Setting a wake schedule
You can set a wake schedule for a policy group to automatically wake devices from supported power states (for example, sleep or hibernation) at designated times. Scheduled device wake-ups help you establish regular maintenance windows to ensure that critical device actions, remediation, and data collection execute promptly without waiting for end users to manually wake their devices.
Wake schedules are supported on Windows and Mac devices in a policy group.
To view configured wake schedules for policy groups, your user role needs to be granted the View permission for Policies.
To set or disable wake schedules, your user role needs to be granted the Manage permission for Policies.
-
Each policy group can have one active wake schedule configured at a time.
-
When a wake schedule is enabled or modified, the configuration is sent to all active, supported devices in the policy group during their next agent connection. When a device applies or updates the schedule, a Wake schedule set on device or Wake schedule updated on device event is logged to Event History. If the schedule cannot be applied to a supported device, a Wake schedule set failed on device event is logged.
-
When a device wakes up at the scheduled time (based on its local device time A date and time expressed in a device's local time zone, as opposed to server time.), it remains awake for up to 5 minutes while the Secure Endpoint Agent initiates a check-in with the Absolute Monitoring Center to download and execute any queued commands. Each time a device wakes up at the scheduled time, a Device awoke event is logged to Event History. If the device is already awake at the scheduled time, the agent performs an immediate check-in.
-
If a device moves to a policy group with a different wake schedule, the agent removes the device's previous schedule and applies the new one. If a device moves to a policy group without a wake schedule, or if the schedule is disabled, the agent removes the existing schedule from the device.
-
If a device's license expires, the agent removes the wake schedule.
The following table lists the power states from which a device can be automatically woken using a wake schedule, along with the power source required for a successful wake-up.
On Windows devices, the following limitations apply:
- The operating system must allow wake timers to run. The Secure Endpoint Agent attempts to enable this setting automatically, but any enterprise Group Policy or MDM policy that explicitly disables wake timers will override it and prevent devices from waking as scheduled. Therefore, ensure your organization's power management policies allow wake timers.
- A user must be logged in for a wake schedule to wake the device.
- A device cannot be woken while it is frozen by a Freeze action.
|
Platform |
Supported power states |
Power requirement |
|---|---|---|
| Windows | Sleep | Supported on battery or AC power |
| Hibernate | Requires AC power | |
| Mac |
Sleep |
Supported on battery or AC power |
| Hibernate |
To set a wake schedule:
- On the navigation bar, click
Policies > Policy Groups. - On the Policy Groups sidebar, click the policy group you want to set a wake schedule for. The policy group opens in the work area.
-
Under the policy group name, click Wake schedule. If a wake schedule is already set for the policy group, its description is shown (for example, Wake schedule: 2 AM every 2 days).
-
In the Wake schedule dialog, select the Automatically wake the device checkbox. This checkbox is already selected if an existing wake schedule is set for the policy group.
-
Under the checkbox, set your desired schedule:
-
To set the wake time: click the first field, then select the hour, the minute, and AM or PM, and click OK. If you don't select a time, the wake time defaults to 12:00 am.
The wake time set here represents local device time A date and time expressed in a device's local time zone, as opposed to server time.. -
To set the wake frequency: click the second field and enter a number, then click the third field and select Day(s), Week(s), or Month(s).
-
If you selected Week(s), click the field after On and select the day or days of the week the device should wake up.
-
If you selected Month(s), click the field after On and select the day of the month the device should wake up.
-
-
-
Click Save.
The wake schedule is set and sent to all active, supported devices in the policy group during their next agent connection. Whenever a wake schedule is enabled for the first time or modified, the corresponding Wake schedule policy enabled or Wake schedule policy updated event is logged to Event History.
To disable a wake schedule:
- On the navigation bar, click
Policies > Policy Groups. - On the Policy Groups sidebar, click the policy group whose wake schedule you want to disable. The policy group opens in the work area.
-
Under the policy group name, click Wake schedule. The wake schedule's description is shown (for example, Wake schedule: 2 AM every 2 days).
-
In the Wake schedule dialog, clear the Automatically wake the device checkbox.
-
Click Save.
The wake schedule is disabled on all active, supported devices in the policy group during their next agent connection. Whenever a wake schedule is disabled, the Wake schedule policy disabled event is logged to Event History.
You can check whether a wake schedule has been successfully applied to an individual device by viewing its policy settings in Device Details.
To view a device's wake schedule status:
- On any page that shows linked device identifiers in the first column of the results grid, such as the All Devices page in the Devices area, click the link for the device that you want to view. Summarized information about the device shows in the page header.
- Click the Policies tab.
-
Under the Data collection section, locate Wake schedule to view its current status on the device. Possible values are:
-
Active — the device has successfully received and applied the wake schedule
-
Inactive — the wake schedule is disabled or deactivated on the device
-
Not supported — the device is running an operating system or platform that does not support wake schedules, or the WKS (Wake Schedule) component of the Secure Endpoint Agent has not yet been installed on the device
-
No data — the activation status is unknown at this time
-
Error — an internal error occurred
-




