Template scan scheduling and maintenance windows

Template scans, service status, and maintenance windows work together to control when devices are evaluated and when actions are allowed to run. Understanding this behavior is important when templates trigger actions such as firmware updates or reboots.

When scheduled template scans run

Scheduled scans (Daily, Weekly, Monthly) run during off-peak hours to minimize disruption:

• Typically between 11:00 PM and 6:00 AM U.S. Central Time.

• Occur outside U.S. business hours.

• Are staggered, so devices are processed at different times.

As a result, devices in the same group may be scanned and remediated at slightly different times.

Device service status

Each device reports a service status that determines whether actions can be performed:

• In Service

  • The device is actively in use.

  • Updates, configuration changes, or reboots are not allowed.

• In Maintenance Window

  • The device is not actively in use.

  • Updates, configuration changes, and reboots are allowed.

By default, devices are typically in a maintenance-ready state unless maintenance windows are explicitly configured.

Using maintenance windows to control timing

To prevent automated actions from occurring during critical business hours, you can use maintenance windows.

You can use templates to configure maintenance windows across your devices. After the template remediates these settings, future scans will only run when devices are within their maintenance windows.

There is currently no way to define a specific time for scheduled scans. As a workaround, you can manually trigger scans if your maintenance windows overlap with the standard scan window.

How maintenance windows affect scans

• If a scan occurs while a device is outside its maintenance window, it is skipped

• The scan runs automatically when the device enters its maintenance window

• Remediation only occurs within the maintenance window

This ensures that changes happen only during approved timeframes.

Best practices

• Align maintenance windows with low-impact periods.

• Use maintenance windows for disruptive actions (reboots, firmware updates).

• Expect staggered execution across devices.

• Use manual scans when tighter timing control is needed.

In simple terms

Scheduled scans determine when devices are checked, and maintenance windows determine when changes can happen. Using both together ensures compliance while controlling when impactful actions occur.