For wake-up when a deadline occurs, the older version of Wake on LAN is used.

Machines only wake when you notify them through the Wake Up client notification.

Limitations for Configuration Manager version 2006 and earlier:

With Configuration Manager version 2006 and earlier, you may see the become very large and possibly a broadcast storm in environments where DHCP leases are set to infinite.

With Configuration Manager version 2010 and later, if the DHCP lease is set to infinite a client won't be woken up or used as a peer to wake other devices.

DHCP lease durations can't be set to infinite.

802.1x network authentication may work with additional configuration depending on the hardware and its configuration.

This feature doesn't support the following network technologies:.

At least one client in the target subnet must be awake.

The new version of Wake on LAN can be enabled at the same time as the older version. Using the client notification channel helps avoid MAC flaps, which could cause the port to be shut down by the router. The site server uses the client notification channel to identify other clients that are awake on the same remote subnet, then uses those clients to send a wake on LAN request (magic packet). If you need to do maintenance or query devices, you're not limited by remote clients that are asleep. You can wake up clients from the Configuration Manager console, even if the client isn't on the same subnet as the site server. Starting in Configuration Manager 1810, there's a new way to wake up sleeping machines. Specify Wake on LAN (WoL) settings for Configuration Manager when you want to bring computers out of a sleep state. Applies to: Configuration Manager (current branch)

Mac wake on lan