Wake On LAN in Configuration Manager 2007 supports the following scenarios:

For example scenarios of how Wake On LAN can be implemented in Configuration Manager 2007 to address these requirements, see Example Scenarios for Implementing Wake On LAN.

Each site must be independently configured for Wake On LAN, using either unicast or subnet-directed broadcast as the transmission method. Wake-up packets are sent from the primary site server to computers assigned to its site.

Wake-up packet transmissions are sent only from primary site servers. You cannot configure secondary site servers or other computers acting as proxies to send wake-up packets.

Computers are woken up before the scheduled activity to ensure that they have completed startup. By default, this occurs 3 minutes before the scheduled activity, but this setting can be configured with the transmission offset option as a Wake On LAN advanced setting. You can also control the amount of network bandwidth that will be used when sending wake-up packets, using the Wake On LAN advanced options. For more information, see How to Configure Wake On LAN Advanced Options.

Wake On LAN in Configuration Manager 2007 supports waking up computers in sleep states S1 through S5. For more information about sleep states, see Sleep States for Wake On LAN.

On wake-up, the Configuration Manager Client registers the system as busy for the specific wake-up task it receives, until the task is complete. This prevents the computer from going back into a sleep state based on its power management settings before the task can complete. Wake On LAN does not return computers to a sleep state but power management schemes can configure computers to shut down or hibernate after a period of inactivity. Windows Vista supports power management schemes through Group Policy.

If you are using Configuration Manager 2007 Internet-based client management, wake-up transmissions are not sent to clients when they are on the Internet. Wake On LAN transmissions are always sent at the scheduled time, ignoring any maintenance windows that might be in effect on a client computer.

In This Section

See Also