Scan Interval Best Practices

This article will help you understand the purpose and impact of scan interval settings when configuring your groups. You can also find best practice use cases for different settings.

Configuring Scan Intervals

Scan intervals are configured in the Group settings. To view or modify these intervals, go to the Automox console dashboard (console.automox.com).

• Click Manage > Groups.
• Open a group to view the Scan Interval section.
  
  
  

By default, the scan interval setting is set to 24 Hours. You can set your scan intervals to execute between 4 hours and 24 hours. Faster scan intervals mean faster updates, but they also increase system resource usage.

Scans begin after a device is added to a group for the first time. They are also initiated after a policy execution completes and after a device reboots.

Example Use Cases

As a reminder, the scan interval setting for groups is set to 24 hours by default. If your devices do not have strict resource usage limits, then setting the scan interval to faster settings can provide more up-to-date statuses. Other settings may be more applicable depending on the specific use cases. See the examples here:

1. Provisioning Group: This is a group designated for provisioning, onboarding, or first-time setup. Devices added to this group are meant for desired state configuration, such as installing required software, applying OS and software configuration changes (via Worklets), or aggressive patching schedules (to catch up on a backlog or reach environmental parity).
   • Configure the scan interval to be between 8 hours and 12 hours. This empowers frequent updates on device statuses in conjunction with frequent policy executions. Note: This increases resource usage.
   • Devices that have achieved the desired state configuration could then be moved to another group for ongoing lifecycle patching with relaxed scan interval settings.
   • Examples for these devices are newly purchased laptops or desktops that must be prepared for assignment to an employee.
2. Server Maintenance Group: This is a group designated for servers with strict maintenance windows for patching and reboots.
   • Configure the scan interval to be between 8 hours and 12 hours. This empowers frequent updates on device statuses in conjunction with frequent policy executions. Note: This increases resource usage.
   • Even if your servers have maintenance windows once a month, having faster scan intervals allows for monitoring of zero-day patches and intermittent security updates that become available outside normal patch release schedules.
3. Lifecycle Group: This is a group designated for ongoing lifecycle patching. Devices added to this group have completed their provisioning or desired state configuration stage and no longer require aggressive policy executions.
   • Configure the scan interval to be between 12 hours and 24 hours. This allows for daily monitoring of zero-day patches and intermittent security updates that become available outside normal patch release schedules. This reduces resource usage compared to a testing or provisioning group.
   • You can leverage device tags and device targeting to scope policies to include devices within this group without moving them if they need extra attention for one-off situations.
   • Example devices for this group are laptops and desktops for employees or servers that do not have strict maintenance windows.
4. Testing Group: This is a group designated for testing new patches, Worklets, or other policies before they can be applied to other groups.
   • Configure the scan interval to be between 4 hours and 8 hours. This allows for monitoring changes and results during typical business hours so administrators can make adjustments and preparations. Note: This increases resource usage.
   • Example devices are laptops, desktops, or servers depending on the testing needs.

Related Topics

• What Happens During a Scan from Automox?
• Managing Groups
• Onboarding Jumpstart Guide - Manage Your Environment