Topic last updated—November 2007

In a production environment, implementing Wake On LAN in Configuration Manager 2007 involves various processes that might require interaction and collaboration with a number of different groups across the enterprise. For example, these groups might include the following:

Consult the network card vendor for details about how to enable Wake On LAN for each network card and driver because the configuration for this will vary for each vendor and possibly for each network card and driver.

Because a Wake On LAN solution can involve a number of different roles and processes, a successful implementation will depend on identifying who is responsible for the various roles and ensuring collaboration between groups when necessary. A successful ongoing implementation will depend on identifying and adhering to processes that coordinate the various functions between the roles.

Some of the consequences of not having and following defined processes when Wake On LAN in Configuration Manager is implemented in a production environment are as follows:

Use a methodology such as ITIL or Microsoft Operations Framework ( to help you implement Wake On LAN within a framework of defined processes. Make sure you document your design, testing procedures, the areas of responsibility, and the processes to follow for configuring, monitoring, and troubleshooting, and then disseminate this information, making sure that it is centrally available and updated.

Review existing company security policies, and if necessary, modify them to include the implementation of Wake On LAN.

See Also