Quantcast
Channel: Configuration Manager 2012 - Application Management forum
Viewing all articles
Browse latest Browse all 4762

Scheduled WOL never wakes

$
0
0

I'm having a strange issue with WOL functionality.

We have WOL working, the network is set up correctly, using the 'Right-Click-Tools' WOL functionality works.

Working:

  1. Turn PC off
  2. Create a deployment
  3. Enable WOL
  4. Deploy immediately

Computer wakes immediately and deployment begins as you would expect.

Not working:

  1. Turn PC off
  2. Create Deployment
  3. Enable WOL
  4. Schedule availability and deadline for 10-15 minutes into the future
  5. Wait timeframe

Nothing happens on the client side.

I can see the WOL trigger in the 'wolmgr.log' - well what I assume is it triggering, it actually shows a few events a minute apart as I would expect, however the computer doesn't wake.

I hope that's clear,  not sure if there is something else going on here?

Here is the last few triggers in the WOL log:

STATMSG: ID=6504 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WAKEONLAN_COMMUNICATION_MANAGER" SYS=Nobelium.camden.nsw.gov.au SITE=CMD PID=2808 TID=5664 GMTDATE=Thu Jul 31 06:32:21.834 2014 ISTR0="{87B37DCC-3843-48ED-B7E1-4A0B8FEE0B18}" ISTR1="2" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=422 AVAL0="33b8d190" AID1=421 AVAL1="2" AID2=415 AVAL2="{87B37DCC-3843-48ED-B7E1-4A0B8FEE0B18}"	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:21 PM	5664 (0x1620)
WOLCManager retry for job id='33b8d190' - 1 retries of 3 maximum completed).	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:21 PM	5688 (0x1638)
WOLCManager waiting 5 seconds for work.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:21 PM	5664 (0x1620)
WOLCManager waking up to process new jobs.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:21 PM	5664 (0x1620)
WOLCManager executing job id='33b8d190' in state 'STATE_PROCESSDATA'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:21 PM	5664 (0x1620)
WOLCManager processing data for job id='33b8d190'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:21 PM	5664 (0x1620)
WOLCManager waiting 5 seconds for work.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:21 PM	5664 (0x1620)
Persisting job data for job id='33b8d190'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:21 PM	5688 (0x1638)
WOLCManager one or more existing jobs is ready.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:26 PM	5664 (0x1620)
WOLCManager executing job id='33b8d190' in state 'STATE_PROCESSDATA'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:26 PM	5664 (0x1620)
WOLCManager processing data for job id='33b8d190'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:26 PM	5664 (0x1620)
WOLCManager job id='33b8d190' will execute next in at least 55 seconds.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:26 PM	5664 (0x1620)
WOLCManager waiting 55 seconds for work.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:32:26 PM	5664 (0x1620)
WOLCManager one or more existing jobs is ready.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:21 PM	5664 (0x1620)
WOLCManager executing job id='33b8d190' in state 'STATE_PROCESSDATA'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:21 PM	5664 (0x1620)
WOLCManager processing data for job id='33b8d190'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:21 PM	5664 (0x1620)
WOLCManager retry for job id='33b8d190' - 2 retries of 3 maximum completed).	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:21 PM	5688 (0x1638)
Persisting job data for job id='33b8d190'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:21 PM	5688 (0x1638)
WOLCManager waiting 5 seconds for work.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:21 PM	5664 (0x1620)
WOLCManager one or more existing jobs is ready.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:26 PM	5664 (0x1620)
WOLCManager executing job id='33b8d190' in state 'STATE_PROCESSDATA'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:26 PM	5664 (0x1620)
WOLCManager processing data for job id='33b8d190'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:26 PM	5664 (0x1620)
WOLCManager job id='33b8d190' will execute next in at least 55 seconds.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:26 PM	5664 (0x1620)
WOLCManager waiting 55 seconds for work.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:33:26 PM	5664 (0x1620)
WOLCManager one or more existing jobs is ready.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:34:21 PM	5664 (0x1620)
WOLCManager executing job id='33b8d190' in state 'STATE_PROCESSDATA'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:34:21 PM	5664 (0x1620)
WOLCManager processing data for job id='33b8d190'.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:34:21 PM	5664 (0x1620)
WOLCManager waiting 5 seconds for work.	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:34:21 PM	5664 (0x1620)
WOLCManager retry for job id='33b8d190' has completed (3 retries).	SMS_WAKEONLAN_COMMUNICATION_MANAGER	31/07/2014 4:34:21 PM	5688 (0x1638)

Hope I'm being clear enough, help!



Viewing all articles
Browse latest Browse all 4762

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>