We were previously running LDMS 8.8 on Windows Server 2003, and decided to start using WOL. We started off trying to go the route of using an MDR to send out WOL, but couldn't get a success rate high enough to satisfy our management. One issue is that we have several small "remote" sites that only have a few PCs (some with only one or two PCs), and if all the PCs are powered off there's nothing that can be used as an MDR for the location. After many talks with LANDesk and our network guys, we decided to go the route of allowing direct broadcast on our network. To minimize security risks, our network guys set it up to allow the direct broadcast traffic to be sent only from our Core server and only one-way (out from our Core). This worked great, and we could power on PCs all across the network with a standard WOL "magic packet" with no issues in scheduled tasks and via right-click if we just wanted to power up an individual machine. It worked great and very reliably for quite a while.
Fast forward to now. We've upgraded our Core to all new everything...new server hardware, LDMS 9.0 SP2, and Windows Server 2008 R2...and WOL has quit functioning. No changes have been made to our network. I worked with our network guys to test, and after capturing and analyzing the traffic our network guys are saying that the WOL "magic packet" is now being sent as a broadcast to "the entire world" rather than as a direct broadcast only to the subnet of the location of the PC (or PCs). Our firewall will not allow a broadcast out to everything, so it's blocking this. We initially thought this was an issue with LANDesk and possibly some change in 9.0 SP2, but when I contacted support they insisted that nothing had been changed from 8.8 to 9.0 as far as WOL goes.
I then started plunking around on Google and have found some things, but nothing that has helped our situation. It was all WOL related, but none of it specifically involved/mentioned LANDesk as the WOL tool.
The first thing I found mentioned the Windows Firewall that's included with Windows Server 2008 R2. The person that was having WOL issues mentioned that he had turned the firewall off, but after experimenting found that it was still blocking things even though it was "off". He turned it back on and then changed the settings to allow all incoming and outgoing traffic, and then WOL "magic packets" started working for him. I had turned off the Windows Firewall on our Core, so I turned it back on and set it to allow all traffic as this person said he had done. This had no effect on getting our WOL working again.
Next I found a few mentions of WOL "magic packets" not working properly on Windows Server 2008 R2, and speculation that it has something to do with 2008 R2 being a 64-bit OS because these same people had no issues with it working from machines with a 32-bit OS (Windows XP, Server 2003, etc). One thing I found on this subject mentioned finally getting WOL to work on 2008 R2 via a Command Line utility, but all the other things I found that suspected 2008 R2 being a 64-bit OS as the culprit had not found a way to get WOL working. I don't really see using a separate Command Line utility as a great option for us (if it works...I haven't tried it).
I'm curious if anyone else on here is using Windows Server 2008 R2 and having any luck using LANDesk (or any other WOL tool) to send out the WOL "magic packet" rather than using an MDR. I've tried using a WOL "magic packet" tool from SolarWinds, and it isn't working either. This same SolarWinds tool did work on our old LDMS 8.8/Server 2003 server.