Schedules | TrendAI™

Views:

Create schedules to configure Anti-Malware Scheduled Scans in Endpoint Security Policies.

Important

If you are working on a policy, make sure to save your settings before leaving the screen. Leaving the screen without saving discards any changes.

Schedules are a policy resource you can configure to control when the agent runs scans or performs certain tasks. These lists are used by the following policy features:

Anti-Malware to control when the agent runs Scheduled Scans.
Version Control Policies to control when the agent checks for and downloads software updates.

You can add up to 50 schedules.

Support for weekly schedules with multiple days selected has some limitations. Agents older than the supported version only run the schedule on the first selected day of the week. For example, if you create a weekly schedule with Monday, Wednesday, and Friday selected, older agents only run on Monday. See the following table for more details.

Scheduled support

Agent feature	Anti-Malware scan full support	Version Control Policies update check full support
Standard Endpoint Protection	Agent version 202604 and later	Agent version 202603 and later
Server & Workload Protection	Agent version 202603 and later	Agent version 202603 and later
Endpoint Sensor	Agent version 202603 and later	Agent version 202603 and later

Procedure

Go to Endpoint Security → Endpoint Security Configuration → Policy Resources → Schedules.
Create or edit a schedule.
- To create a new list, click Add schedule.
- To edit an existing schedule, click the schedule name and go to General.
- To duplicate an existing schedule, select a schedule and click Duplicate. After creating the duplicate schedule, click the schedule name and go to General.
Specify a name and description for the schedule.
Specify the Start date.

The start date controls the earliest date the schedule can occur. Depending on your settings, the schedule might not run on the start date, but instead runs the first time the frequency conditions are met after the start date.

For example, if the start date is set to February 15, but the frequency is monthly on the 20th, the first run of the schedule is February 20.
Specify the Frequency.
- Daily: Schedule occurs once per calendar day.
- Weekly: Schedule occurs once per calendar week.
- Monthly: Schedule occurs once per calendar month.
1. If you select Weekly, specify On which days to run the schedule. You can select multiple days.
2. If you select Monthly, specify On which day to run.
  - Select Day to specify which numerical date for the schedule to run.
    
    If a month has fewer days than the selected day, the schedule runs on the last day of that month. For example, if you select 31, the schedule runs on April 30.
  - Select the second option to specify which week and weekday for the schedule to run.
    
    For example, you can select The Monday of the first week to run the schedule on the first Monday of the month.

Specify the Start time and duration.

Specify the start time to set what time the schedule runs.

Agents use the timezone settings on the endpoint to determine start time.

For example, if you set the start time to 8 PM, an agent in New York City starts the schedule at 8 PM Eastern Time. An agent in Seattle starts three hours later, at 8 PM Pacific Time.

Select the duration to set when the scheduled event ends.

The duration determines when to timeout or fail a scheduled task.

Scans treat the end of the duration as a timeout and stops the scan process if the agent fails to start the scan or if the scan takes too long.
Agent updates only check for and download updates during the duration. If agents are unable to download the update within the duration, the agents try again at the next valid schedule.

Note

Agents with Standard Endpoint Protection attempt to resume the scan the next day at the same scheduled time. If the scan failed because the task took too long, the agent skips previously scanned files and resumes the scan.

If agents consistency timeout while scanning, try increasing the timeout period.
Agents which start the update installation process within the duration period do not stop or timeout the installation. Installation continues until successfully completed, even if the process takes longer than the specified duration.

Agents queue for update checks based on your connection and bandwidth settings. If you have a large number of agents in your environment, the update process might take several days to complete.

Click Save.