Bug - 2 Hr Delay with Scheduled Patch WOL

Bug - 2 Hr Delay with Scheduled Patch WOL

We have version 92119

The scheduled time in patch policies and deployment policies is irrelevant for shutdown machines, there is no point to it.

Devices get woken up 2 hours after the specified time. There is no point to this and it makes trying to work out actual WOL times a nightmare.

M.E have said that it's always been like this. What is the point?

Is this a bug or a known 'design feature'?


Note: Software configurations using deployment policies to wake up PC's work at the stated time.


We have hundreds of PC's that get replaced all the time. We cannot rely on scheduled WOL tasks to help, because you can associate scheduled WOL tasks to a dynamic group (that's another design floor). Therefore, for us, scheduled WoL tasks are not viable because ironically, it has too big an administrative overhead.


Scenario (our scenario is below, we cannot achieve what we want)


  • PC's shutdown around 5 - 6 pm
  • We want PC's to WoL at 7pm, scan download and then install patches
  • However, if we set the schedule to be 7pm... PC's wake up at 9pm
  • If we set patch schedules to take place before 6pm - User performance will be impacted and PC's may reboot

Effectively - we cannot automate WOL and patch schedules at 7pm



                New to ADSelfService Plus?