SCCM WOL Schedule problem
I am having a problem with the WOL feature in SCCM 2007, specifically when I create a package and then an advertisement to deploy that package I can select the Enable Wake-on-LAN option. I can set the advertisement start time well into the future, I can set the mandatory assignment to be even farther into the future but the moment I save that advertisement it wakes up all the systems and does nothing should the system be shut down when the scheduled time arrives. How do I fix this?
March 25th, 2009 11:08pm

What's in WOLmgr.log and WOLCmgr.log? Is that a typo: "should the system be shut down when the scheduled time arrives"? Shut down? Or wake up?
Free Windows Admin Tool Kit Click here and download it now
March 26th, 2009 11:06am

No typos, I am only saying that when a system is woke up immediately after I have saved the advertisement then a user shuts down or turns off that same system after it was started uponce then that system is never woke up again when it is scheduled. I have been looking at the logs you mentioned and they have no errors it just shows that the WOL command was sent as soon as I created the advertisement and once again when it was scheduled but apparently not to the systems that had been successfully startedalready.
March 26th, 2009 4:42pm

I'm sure all of you realize this by now but there is a hotfix to help solve some of these WOL issues.
Free Windows Admin Tool Kit Click here and download it now
October 15th, 2009 10:03pm

That KB is for a Daylight savings time fix. It doesnt sounds like it fixes the issue.
November 12th, 2009 10:52pm

We, too, are having the same problem.Note:We are using WindowsServer 2008 Standard SP1 (x64)with Configuration Manager 2007 SP1 R2 as our Primary Site Server.I've had some success getting the Wake-On-LAN schedule to work correctly by changing the WOL site properties to "Usewake-up packets only" and changing the transmission offset time from 3 minutes to 5 minutes. After doing this, WOL packets are sent at the right time (5 minutes before the mandatory assignment)and the PC(s) wake up as expected.Something odd that I found is that thewake-upreports show that WOL packetsare beingsent out as soon as the advertisementis saved.Computersaren'twaking up during this period (like they were prior to me changing the WOL site settings) but I don't understand why the report shows that these packets are being sent.5 minutes prior to the mandatory assignment,thewake-up reports show that WOL packets are being sent (like they are supposed to)and the computers actually wake up at this point.Has anyone else been able to reproduce this? Does anyone have a better, more reliable way to fix this issue?Thanks!Danny DDeddy,We see almost the exact same issue you describe.We have a DEV environment anda PROD environment.DEV: recurring wake-up advert runs every half hour. The package is a shutdown command. This is used for testing. We see the 6504 messages for the SMS_WAKEONLAN_COMMUNICATION_MANAGER component being sent once every interval.PROD: We have weekly wake-on-lan advertisements with a simple vbscript payload to mark an event in the event log. We see these advertisements (which have anywhere from 1 to 1700+ clients targeted) sending wake-on-lan packets (6504 status message) multiple times for each day and then on days where we don't expect.We, too, are tempted to set the WOL settings for our site to "Usewake-up packets only" as well, but have not yet.Documentation on the SCCM scheduling of WOL is lacking. Any updates to your issue?Here's a different technet post I started a few weeks ago which has not gained much traction:
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2009 12:36am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics