SCCM 2007 and Wakeup on LAN
Hi I have some packages that need to be delivered over night, this is all working but I have a problem with WOL on the clients.. All clients are running WIndows XP pro.. My problem ONLY happens if Windows has "Shutdown" the machine.. If I use windows to send the mahines to Sleep, it works fine.. SCCM WOL wakes machine up etc If I hard power off the machine again SCCM WOL wakes the machine up etc Seems Like on Shutdown Windows is leaving the NIC in a state that WOL does not work in, I have tried changing the settings in windows but this simply breaks the bits that do work. I know its not the BIOS as I can wake the machines from 2 states.. Help please :) Keith
March 29th, 2012 6:30am

Hi Keith Just check again your bios settings in order to confirm that the deep shutdown is not enable in the power management settings.Gaston Gardonio - http://blogs.technet.com/plataformas/archive/tags/System+Center/default.aspx
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2012 11:23am

ConfigMgr simply sends the magic packet. What the NIC does with the magic packet is up to the NIC. I have seen similar issues before due to the NIC driver and the NIC firmware versions. Make sure you have the latest for both. Another possibility is the ARP cache on the final layer 3 device or the equivalent cache on the final layer 2 deivce (I don't remember the name of this cache). These cache's are only important though if you are using unicast WoL. Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
March 29th, 2012 3:13pm

as have said, WOL does woke as long as the machine has not been booted into windows, therfore it cannot be an issue with the switch, router or any nework issue WOL is turned on in BIOS as it works from a powered off machine, just not one windows has shut down
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2012 2:03am

Hi I have now resolved the initial problem.. I can now WAKE the machines from "WOL magic Packet Sender" from either another test machine or the SCCM server, BUT SCCM will not wake the same machines? Any ideas? Keith
April 4th, 2012 9:12am

Curious if you read my original post? All ConfigMgr can do is send out the magic packet -- its delivery to the client is completely dependant on your network and what the client does with the magic packet is up to the NIC bios; i.e., multiple things outside of ConfigMgr's control or influence. Are you using unicast or directed subnet? Have you reviewed Wolmgr.log and WolCmgr.log? Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2012 10:13am

Hi I have tried both unicast and directed broadcast, SCCM does not wake the machine.. bvut run WOL Magic Package Sender from SCCM server and machine wakes up fine.. this is my last try Wolcmgr.log [only today entries] WOLCManager component polling interval expired. $$<SMS_WAKEONLAN_COMMUNICATION_MANAGER><Thu Apr 05 08:36:59.151 2012 GMT Daylight Time><thread=3304 (0xCE8)> WOLCManager reading settings from the site control file. $$<SMS_WAKEONLAN_COMMUNICATION_MANAGER><Thu Apr 05 08:36:59.151 2012 GMT Daylight Time><thread=3304 (0xCE8)> No changes to the site control file detected, no settings were read. $$<SMS_WAKEONLAN_COMMUNICATION_MANAGER><Thu Apr 05 08:36:59.151 2012 GMT Daylight Time><thread=3304 (0xCE8)> WOLCManager waiting 3600 seconds for work. $$<SMS_WAKEONLAN_COMMUNICATION_MANAGER><Thu Apr 05 08:36:59.152 2012 GMT Daylight Time><thread=3304 (0xCE8)> and Wolmgr.log for same period WOLManager waking up to process new jobs. $$<SMS_WAKEONLAN_MANAGER><Thu Apr 05 08:27:57.119 2012 GMT Daylight Time><thread=3316 (0xCF4)> STATMSG: ID=6510 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WAKEONLAN_MANAGER" SYS=SB3MSSCM1 SITE=SE1 PID=2472 TID=3316 GMTDATE=Thu Apr 05 07:27:57.165 2012 ISTR0="SE120223" ISTR1="1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=421 AVAL0="1" AID1=415 AVAL1="SE120223" $$<SMS_WAKEONLAN_MANAGER><Thu Apr 05 08:27:57.165 2012 GMT Daylight Time><thread=3316 (0xCF4)> WOLManager waiting 3600 seconds for work. $$<SMS_WAKEONLAN_MANAGER><Thu Apr 05 08:27:57.167 2012 GMT Daylight Time><thread=3316 (0xCF4)> WOLManager waking up to process new jobs. $$<SMS_WAKEONLAN_MANAGER><Thu Apr 05 08:27:57.167 2012 GMT Daylight Time><thread=3316 (0xCF4)> WOLManager waiting 3600 seconds for work. $$<SMS_WAKEONLAN_MANAGER><Thu Apr 05 08:27:57.172 2012 GMT Daylight Time><thread=3316 (0xCF4)> WOLManager waking up to process new jobs. $$<SMS_WAKEONLAN_MANAGER><Thu Apr 05 08:28:17.459 2012 GMT Daylight Time><thread=3316 (0xCF4)> STATMSG: ID=6510 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WAKEONLAN_MANAGER" SYS=SB3MSSCM1 SITE=SE1 PID=2472 TID=3316 GMTDATE=Thu Apr 05 07:28:17.711 2012 ISTR0="SE120223" ISTR1="1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=421 AVAL0="1" AID1=415 AVAL1="SE120223" $$<SMS_WAKEONLAN_MANAGER><Thu Apr 05 08:28:17.711 2012 GMT Daylight Time><thread=3316 (0xCF4)> WOLManager waiting 3600 seconds for work. $$<SMS_WAKEONLAN_MANAGER><Thu Apr 05 08:28:17.714 2012 GMT Daylight Time><thread=3316 (0xCF4)> WOLManager waking up to process new jobs. $$<SMS_WAKEONLAN_MANAGER><Thu Apr 05 08:28:17.714 2012 GMT Daylight Time><thread=3316 (0xCF4)> WOLManager waiting 3600 seconds for work. $$<SMS_WAKEONLAN_MANAGER><Thu Apr 05 08:28:17.718 2012 GMT Daylight Time><thread=3316 (0xCF4)>
April 5th, 2012 4:03am

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

Other recent topics Other recent topics