ESET PROTECT On-Prem

Offline | Go online

ESET PROTECT On-Prem – Table of Contents

# Task trigger types

Copy current article URL Share via email

Triggers are essentially sensors that react to certain events in a pre-defined way. They are used to execute the task they are assigned to. They can be activated by the scheduler (time events) or when a certain system event occurs.

|  | You cannot reuse a trigger. Each task must be triggered with a separate trigger. Each trigger can run only one task.

The trigger does not run newly assigned tasks immediately (except the ASAP trigger)—the task is run as soon as the trigger is fired. Trigger sensitivity to events can be reduced further using throttling.

## Trigger types

•As soon as possible—Available only for Client Tasks. The task will run as soon as you click Finish. The Expiration Date value specifies the date after which the task will no longer be executed. You can define the expiration date up to six months from the current date.

### Scheduled

Scheduled Trigger will run the task based on date and time settings. Tasks can be scheduled to run once, on a recurring basis, or on CRON expression.

•Schedule Once—This trigger is invoked once on the scheduled date and time. It can be delayed by random interval.

•Daily—This trigger is invoked every selected day. You can set the start and end of the interval. For example, you can run a task for ten consecutive weekends.

•Weekly—This trigger is invoked on a selected day of the week. For example, run a task every Monday and Friday between July 1 and August 31.

•Monthly—This trigger is invoked on selected days in the selected week of a month, for the selected period of time. The Repeat on value sets the weekday in the month (for example, the second Monday) on which the task should run.

•Yearly—This trigger is invoked every year (or more years, if so configured) on the specified start date.

|  | Random delay interval setting is available for Scheduled type triggers. It defines the range of maximum delay for task execution. Randomizing can prevent overloading the server.

|  | If John set the task to trigger Weekly on Monday and Start on 2017 Feb 10 8:00:00, with Random delay interval set to 1 hour and end by set to 2017 Apr 6 00:00:00, the task would run with a randomized one-hour delay between 8:00 and 9:00 every Monday until the specified end date.

|  | •Select the check box Invoke ASAP if Event Missed to run the task immediately if it did not run at the defined time. • When configuring a trigger, ESET PROTECT Web Console time zone is used by default. Alternatively, you can select the check box Use Target Local Time to use local time zone of the target device instead of ESET PROTECT Web Console time zone for the trigger.

### Dynamic Group

Dynamic Group triggers are available only for Server Tasks:

•Dynamic Group Members Changed—This trigger is invoked when the contents of a Dynamic Group change. For example, if clients join or leave a specific Dynamic Group.

•Dynamic Group Size Changed According to Threshold—This trigger is invoked when the number of clients in a Dynamic Group becomes higher or lower than the specified threshold. For example, if more than 100 computers are in a given group.

•Dynamic Group Size Changed Over the Time Period—This trigger is invoked when the number of clients in a Dynamic Group changes over a defined time period. For example, if the number of computers in a given group increases by 10% in an hour.

•Dynamic Group Size Changed According to Compared Group—This trigger is invoked when the number of clients in an observed Dynamic Group change according to a compared group (static or dynamic). For example, if more than 10% of all computers are infected (the group All compared to the group Infected).

### Other

•Server Started—Available only for Server Tasks. Is invoked when the server starts. For example, this trigger is used for the Static Group Synchronization task.

•Joined Dynamic Group Trigger—Available only for Client Tasks. This trigger is invoked every time a device joins the dynamic group.

|  | Joined Dynamic Group Trigger is available only if a dynamic group is selected in the Target section. The trigger will run the task only on devices that join the dynamic group after the trigger is created. For all the devices already in the dynamic group, you will have to execute the task manually.

•Event Log Trigger—This trigger is invoked when a certain event occurs in logs. For example, if there is a detection in the Scan log. This type of trigger provides a set of special settings in the Throttling settings.

•CRON Expression—This trigger is invoked at a certain time and date.

˄˅