

Keeping a computer awake after an alarm clockīy default, an alarm clock call keeps a computer awake by preventing power schemes from operating for 60 minutes. One advantage of using a power policy to set alarm clocks is that if WakeUp integration is enabled, you can bring a computer out of a power-off state as well, unlike the command-line restriction, where you can only bring a computer out of a sleep state. Nightwatchman -acturnonmonitor=on Setting alarm clocks from the NightWatchman ConsoleĪlarm clocks can also be defined using power policies. For example, to set a weekly alarm clock for the above profile for Windows: To bring clients out of a power-off state you must use the NightWatchman Console together with WakeUp. When using this method to define alarm clocks, you can only bring client computers out of a sleep state and not from a power-off state. On the NightWatchman command-line, you set alarm clocks using alarmclock and acturnonmonitor. Setting alarm clocks from the command-line For example, you may want all machines in a development department to be available from 08:00 Monday to Friday, except Thursday where there is a team meeting and the machines should be available from 10:00. Alarm clocksĪlarm clock definitions consists of a day of the week and a time when it should operate. Client computers are brought out of a low-power state up to 5 minutes before an alarm clock or maintenance window event to ensure that they are available at the pre-determined time. If you are using Configuration Manager and have many site servers, these events should be set using dummy Configuration Manager advertisements for performance reasons.


NightWatchman will not wake a laptop from sleep for alarm clocks or maintenance windows.
