SCCM 2012: How to troubleshoot Wake on Lan functionality

01 Oct

Wake on Lan (WoL) functionality is one the poorest documented features SCCM 2012 offers. Enabling WoL requires one checkbox (to enable it) and two radio buttons (to select the packet type and the protocol). Getting it to work though is rather challenging. Many people have written blogs to set up requirements (such as BIOS and OS settings and of course the network infrastructure) so these can be found at a lot of places on the internet. The biggest challenge is to determine which UDP port is used. The default value is 9 but very often this port is not used at all.

To facilitate and test WoL functionality, it is recommended to install the SCCM Right Click Tools which includes wol.exe. wol.exe can be used to wake up machines by sending wake up packets to destination computers. These packets should arrive when the destination computer is on.

If UDP port 9 is not used, then it becomes a guess to determine which UDP port is used instead. One great way of determining the right UDP port is using a packet sniffer tool such Microsoft Network Monitor or Wireshark. Filtering options can be used to discard all irrelevant traffic for display purposes.

At my current project, the administrators did a great job by setting up Wireshark which allowed them to detect that wol.exe was using UDP port 12287 instead of 9.

After challenging the WoL port in SCCM 2012 from 9 to 12287, they were able to successfully wake up machines to let them execute the required task. In this case a new operating system is deployed started from PXE. Wol.exe is no longer needed to wake up the machines at any time.


2 responses to “SCCM 2012: How to troubleshoot Wake on Lan functionality

  1. Greg

    04/09/2014 at 17:31

    I know this was a long time ago now…..but in case any one else googles there way across this. I think one of us is confused, and it could very well be me, but here goes: SCCM right click tools are powershell scripts that launch from the console. The WOL tool uses wolcmd.exe from the machine running the console, it is totally divorced from any settings in SCCM. You could have WOL disabled in SCCM, and the right click tool would still work. wolcmd.exe uses port 7 by default, but if you look at the powershell code for that right click took, it is set to use 12287. There is no reason the port SCCM uses itself to wake machines has to match the one you use from the console, its just a setting that describes what port the magic packets go to on the destination machine, it doesnt do anything to enable WOL on those machines. Machines can recieve WOL magic packets on any port, it doesn’t matter which one you use. What it does matter for is your routers and firewalls, they have to be passing thru the correct port. It sounds like your network was setup to pass directed broadcasts on 12287 (which is wahlt allowed the right click tool to work), which is why SCCMs attempts to wake machines for tasks using port 9 didnt work.

  2. Drake Deadmarsh

    28/05/2015 at 13:51

    Also if you open up the wol.ps1 in Right-click tools port 12287 is indicated within it.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Steve Thompson [MVP]

The automation specialist

Boudewijn Plomp

Cloud and related stuff...

Anything about IT

by Alex Verboon

Deployment Made Simple

Modern Workplace

Azure, Hybrid Identity & Enterprise Mobility + Security

Daan Weda

This site is all about System Center and PowerShell

IT And Management by Abheek

Microsoft certified Trainer -Abheek

Heading To The Clouds

by Marthijn van Rheenen

%d bloggers like this: