I saw a thread about Wake On LAN on the myITforum SMS e-mail list last week that got me working on some Configuration Manager Wake On LAN (WOL) research for you. I am not actually writing the WOL documentation for Configuration Manager, and presently may not be able to help you any further than telling you what I know about it as of right now—which I’ve done below here:
The current planning for WOL support in Configuration Manager 2007 will support both subnet directed and unicast methods for sending the “magic packets”. Unicast is actually the preferred method for doing this as subnet directed broadcasts will not be supported in an IPv6 environment. To use unicast mode, systems must be in hibernatation mode and not completely turned off.
Subnet directed broadcasts can wake up systems that have power going only to the motherboard, but you must configure routers to pass their magic packets, and the computers must have their BIOS configured to support WOL. You can also configure a specific port and ACL on a router for a specific IP address to send the subnet directed broadcast. When using peer-peer WOL solutions you need to have at least one system awake on every subnet to act as a proxy. So, if you attempt to wake up computers on a subnet without at least one system turned on, your WOL solution will fail. When using Configuration Manager's planned WOL feature not every machine on the subnet will be woken up when you send the broadcast. Configuration Manager will require a system to be noncompliant for whatever software update or advertisement that you have targeted at a collection before it sends out a wake up packet. These packets are sent based on client DDR IP address information, but are targeted at the system's actual MAC address. Here’s what I mean; when the initial packet is sent out to wake up a system, it will use the IP address to route to the subnet and router and then send a unicast broadcast to everything on that subnet—looking for the MAC address of the system identified as noncompliant and wakes the matching system—and only that system—up to perform the necessary action. This solution is much more integrated with Software Updates, Operating System Deployment (OSD), and Software Distribution via Configuration Manager than other WOL solution. MAC address targeting also helps protect against systems or networks with aggressive DHCP lease requirements where the IP address may have changed recently on systems. The Configuration Manager 2007 WOL solution will not turn off machines after they have been woken up. This allows other processes that may have been triggered after the machine started up to complete whatever it is they need to do without the system shutting down on them. The Configuration Manager 2007 WOL process will register as a busy service when it wakes up a system and then unregister itself once the process is completed allowing existing power management processes and templates to shut the machine down. Group policy can be leveraged to configure power management options for your systems in accordance with your own WOL needs.
Of course, since Configuration Manager hasn't been released yet this information is subject to change and as always:
This posting is provided "AS IS" with no warranties and confers no rights.