Wake On Lan Task Sequence Extension Beta Download

Another Wake on Lan tool for Configuration Manager? Aren't there enough already? Aren't Wake on Lan Capabilities already in Configuration Manager?

System Center Tools created the SCT WOL extension tool due to multiple customers who want to use WOL capabilities with Configuration Manager, but don't want to spend extra money for a 3rd party product. Our belief is that the out of the box WOL capabilities combined with the extension tool will meet the needs of most customers.

How it Works:

The WOL Extension tool is a single executable that should be added to a ConfigMgr package. This executable should then be added to the beginning of a task sequence as a 'Run Command Line' Task Sequence item. When the task sequence item is launched on a client, the WOL Extension tool will query ConfigMgr to identify other systems on the same subnet as the client that are also targeted by the advertisement. The WOL tool will then send wake-up packets to these systems and report to ConfigMgr which systems the wake-up packets were sent to. If WOL is enabled on the offline systems they will wake-up and run the task sequence as well.

Here's a high-level comparison of SCT's WOL Extension tool to existing solutions.

Solution

Additional Cost

Network Impact

Limitations

SCT WOL Extension Beta

$0.00

This solution is an agentless add-on for your ConfigMgr task sequences. Wake-up packets are sent from ConfigMgr clients on the same subnet therefore network/router/switch re-configuration is not required. This solution can work well in combination with ConfigMgr WOL Unicast.

The solution only works from ConfigMgr task sequences. It is also a recent addition to the available solutions and therefore hasn't been tested to the same extent of the other solutions. This solution requires MS .Net Framework v2.0 on the ConfigMgr Clients.

ConfigMgr WOL Unicast

$0.00

This solution requires minimal network changes to function. For the most part switches must be configured to forward UDP packets. http://technet.microsoft.com/en-us/library/bb632911.aspx

The biggest challenge here is the reliance on the router arp cache to function. The default TTL for the arp cache on Cisco routers is 4 hours. The end result is that systems that have been off for more than 4 hours won't wakeup. So much for your weekend deployment plan.

ConfigMgr WOL Subnet-directed

$0.00

This solution requires fairly extensive network changes to function. Routers would need to be configured to allow IP-directed broadcasts from the ConfigMgr Primary Site Servers. It is unpopular for this reason. http://technet.microsoft.com/en-us/library/bb632911.aspx

The key limitation is the required network changes. Once the network/routers are re-configured this solution works well.

1E Wakeup

Yes

This solution is generally considered to be a top notch solution. While I'm not an expert at the solution, an agent is deployed and wake up packets are sent from the agent to other systems on the same subnet. Wake-up packets are delivered on the same subnet therefore network/router/switch re-configuration is not required.

The chief limitation is that this solution has extra cost. If you planned for WOL to work out of the box with ConfigMgr then perhaps you did not budget for 3rd party tools. Some may not wish to deploy an additional agent.

 

Intrigued? Want to Try it out? Here are basic setup instructions:

1. Use the link above to download the extension tool.

2. E-mail SCTWOL@Systemcentertools.com with your organization name, number of computers, how long you have been using ConfigMgr/SMS. A registration key will be automatically e-mailed back to you along with a EULA. The EULA is "By using this software you agree that System Center Tools LLC is in no way liable for any impact the software may have on your computers, network or organization. You also grant System Center Tools a right to reference your organization and information provided by you to other System Center Tools customers or potential customers."

3. Create a folder that will contain the downloaded .exe, and then create a ConfigMgr package that refers to this folder.

4. Create a new or add to an existing task sequence (one possibly that deploys an application or suite of applications).

5. Create a group of task sequence items in the following order:

6. Adjust the SMS SQL Server view privileges so that either the SQL Logon account has read privileges or domain computers have read privileges.

7. Send your feedback to sbobosky@systemcentertools.com ! Thanks!