I’m sure everyone reading this has a perfect WOL setup. You just click the button to turn on WOL magic packet on the ConfigMgr server and it starts working, like magic! But, just in case one or two of you don’t have a 100% success rate, I decided to write a guide on things I do to increase your success rate with magic packet.
The first thing you’ll want to do is enable WOL on the ConfigMgr server. Go to the Administration tab, Site Configuration, Sites, right click on the site and go to properties:
Go to the Wake On LAN tab and check “Enable Wake On LAN for this site”
Now, if you don’t have a server with the out of band service point installed in your site, you are going to be greeted by an informational message.
This message has nothing to do with WOL magic packet, it only applies to the AMT power on commands. Magic packets will still be sent out as long as you select option one or option three.
You will have to decide if you want to do subnet directed broadcasts or unicast. Subnet directed broadcasts send the packet to all computers on the last subnet ConfigMgr saw the computer on. Unicast broadcasts send the packet only to that computer. Unicast tends to be not as reliable as subnet directed broadcasts because it depends on the router’s ARP cache. If the cache is cleared, it won’t know where to send the packet. I recommend subnet directed broadcasts. It can be a security problem if you don’t restrict who can send the packets though. So if your network team gives you push back, have them restrict subnet directed broadcasts to your ConfigMgr server.
Click on Advanced and look through these settings. The defaults are usually fine, but if you have a special need in your environment, you can usually find the setting to change here. For instance, if you know you have a packet loss problem, you might want to change the number of retries to something more than 3.
Now, go to the ports tab and check to make sure the WOL port is the one you want. By default it is 9, but you can change it to whatever you want.