System Center Configuration Manager TechCenter >
System Center Configuration Manager Forums
>
Configuration Manager Software Distribution
>
Wake On LAN behavior is erratic - Packets being sent at unscheduled times
Wake On LAN behavior is erratic - Packets being sent at unscheduled times
- I have a couple issues with SCCM and WOL and cannot find any detailed documentation as to the inner workings of the site servers regarding WOL.Issue 1:-------------------------I have a wake-up advertisement for software distribution that is targeted to clients at 5:30am on Sundays.Message ID 6510 = The SMS Wake On LAN component successfully processed wakeup information for the object id=<advertisementID> of type=1.When I look at the SMS_WAKEONLAN_MANAGER component status messages (since Saturday), I see the message ID 6510 repeated many times for this one particular advertisement. We expect that the wake-up packets are to be sent about 10 minutes prior to the advertisement mandatory scheduled time (5:20am).I see the 6510 message for this advertisement on Saturday at 3:20am, Sunday at 4:20am, 5:20am, 6:20am, 6:50am, 6:52am, and then on Tuesday at 5:04am.SCCM does not log individual packets sent, so I cannot tell how many packets are being sent at those times. My best assumption (____-u-me) is that the site server is receiving either updated hardware inventory for clients that may not have woken up and is resending the packets to those systems so they run the advertisement...Issue 2:-------------------------We have the identical advertisement scheduled to run on sundays except for the time is 6:00am (same package/program)This advertisement, according to the SMS_WAKEONLAN_MANAGER component status messages, is not being processed. I do not see the objectID that matches the advertisementID for that particular advertisement.There are a few identical advertisements that WOL is not being sent for that day.Additional information-------------------------These advertisements and collections were created via a script using the SDK as reference. They are created the same.It seems that Issue 2 only occurs on Sundays. The 5am Advertisement works, but the other 8 advertisements that run at 6am, 6:30, 7, 7:30, 8, 9, 10, and 11 (all AM) do not have any WOL information in the status messages and clients are not waking up with those advertisements. All 9 advertisements are created the same way with the same script.I've compared all advertisements in the v_advertisements and vadvertisements tables... flags and everything are the same (except schedules, of course).These advertisements are weekly schedules.-------------------------Help?
nick
Answers
- SMS_WAKEONLAN_MANAGER doesn't send WOL packets to clients. SMS_WAKEONLAN_COMMUNICATION_MANAGER does it. If you have troubles and can't find enough information from status message, please take a look at wolmgr.log and wolcmgr.log first. Also you can enable verbose logging when you update registry key HKLM\Software\Microsfot\SMS\Componetns\SMS_WAKEONLAN_MANAGER (SMS_WAKEONLAN_COMMUNICATION_MANAGER)\Verbose Logging.
- Marked As Answer byEric C. MattoonMSFT, ModeratorWednesday, November 11, 2009 12:25 AM
- Unmarked As Answer byEric C. MattoonMSFT, ModeratorWednesday, November 11, 2009 7:03 PM
- Marked As Answer byEric C. MattoonMSFT, ModeratorWednesday, November 11, 2009 9:40 PM
- When to wake up the client machine is based on your server side settings. Following settings will affect the result.
#1) WOL offset settings
#2) Adverstisement schedule (UTC or Local time)
If your advertisment schedule isn't UTC, all clients will be waken up based on clients' time zone. That should be your case.- Proposed As Answer byEric C. MattoonMSFT, ModeratorWednesday, November 11, 2009 9:39 PM
- Marked As Answer byEric C. MattoonMSFT, ModeratorWednesday, November 11, 2009 9:39 PM
All Replies
- SMS_WAKEONLAN_MANAGER doesn't send WOL packets to clients. SMS_WAKEONLAN_COMMUNICATION_MANAGER does it. If you have troubles and can't find enough information from status message, please take a look at wolmgr.log and wolcmgr.log first. Also you can enable verbose logging when you update registry key HKLM\Software\Microsfot\SMS\Componetns\SMS_WAKEONLAN_MANAGER (SMS_WAKEONLAN_COMMUNICATION_MANAGER)\Verbose Logging.
- Marked As Answer byEric C. MattoonMSFT, ModeratorWednesday, November 11, 2009 12:25 AM
- Unmarked As Answer byEric C. MattoonMSFT, ModeratorWednesday, November 11, 2009 7:03 PM
- Marked As Answer byEric C. MattoonMSFT, ModeratorWednesday, November 11, 2009 9:40 PM
- This issue is happening on more than just Sunday. below are the status messages from the ad set with WOL for 6:30 AM Wednesday.
Advert info - Day:Wednesday 24HRTime-06:30 count of machines-3936 advertID-XXX201E5
SeverityType Site code Date / Time System Component Message ID Description Information Milestone xxx 11/11/2009 7:22 XXXXX SMS_WAKEONLAN_COMMUNICATION_MANAGER 6505 The SMS Wake On LAN component component completed sending wakeup packets for the object id=XXX201E5 of type=1. Information Milestone xxx 11/11/2009 7:20 XXXXX SMS_WAKEONLAN_COMMUNICATION_MANAGER 6504 The SMS Wake On LAN component is starting to send wakeup packets for the object id=XXX201E5 of type=1. Information Milestone xxx 11/11/2009 6:22 XXXXX SMS_WAKEONLAN_COMMUNICATION_MANAGER 6505 The SMS Wake On LAN component component completed sending wakeup packets for the object id=XXX201E5 of type=1. Information Milestone xxx 11/11/2009 6:20 XXXXX SMS_WAKEONLAN_COMMUNICATION_MANAGER 6504 The SMS Wake On LAN component is starting to send wakeup packets for the object id=XXX201E5 of type=1. Information Milestone xxx 11/11/2009 5:22 XXXXX SMS_WAKEONLAN_COMMUNICATION_MANAGER 6505 The SMS Wake On LAN component component completed sending wakeup packets for the object id=XXX201E5 of type=1. Information Milestone xxx 11/11/2009 5:20 XXXXX SMS_WAKEONLAN_COMMUNICATION_MANAGER 6504 The SMS Wake On LAN component is starting to send wakeup packets for the object id=XXX201E5 of type=1.
Like Nick mentioned, the WOL packets (for certain advertisements) are being sent out by the primary site server when they should not be... early and late in some cases. our settings are:
Use power on commands if the ocmputer support this technology, otherwise use wake-up packets
Subnet-directed broadcasts.
Advanced -
Transmission retries: Retries=3 Delay(minutes)=1
Transmission maximum: Maximum=10000 Wait(seconds)=10
Transmission threads=3
Transmission offset(minutes)=3
What are the innerworkings of WOL in regards to SCCM's implementation of it? Meaning, how is this scheduled and what triggers it to be sent by the site server configured for this? How do our advanced WOL settings affect this? If we modify the advanced settings would this issue go away? We just can't find enough info on how SCCM handles the WOL process to troubleshoot the issue we are seeing. If anyone knows where we can get very detailed info on how WOL is handled by SCCM it would be very helpful. OR, if someone else has seen this and found a root cause please share!
Matt I ran a report to determine the number of timezone offsets in our environment... We have 3 timezones showing up... most are in eastern time (-300), but a few are in -240 and -360. I am thinking this may be causing part of the issue. BUT, I still need info on how SCCM does WOL to know for certain! This would explain WOL kicking off one hour before and one hour after 6:30, since those time offsets are 4 hours, 5 hours and 6 hours off GMT.
Matt- When to wake up the client machine is based on your server side settings. Following settings will affect the result.
#1) WOL offset settings
#2) Adverstisement schedule (UTC or Local time)
If your advertisment schedule isn't UTC, all clients will be waken up based on clients' time zone. That should be your case.- Proposed As Answer byEric C. MattoonMSFT, ModeratorWednesday, November 11, 2009 9:39 PM
- Marked As Answer byEric C. MattoonMSFT, ModeratorWednesday, November 11, 2009 9:39 PM
Sorry to be the late responder on this one, but I was out all last week with a case of the H1N1 - Not fun and I don't wish it upon my worst enemy.
As for the troubleshooting, Matt was working on this while I was out of the office, so his issue and mine are one in the same.
As Matt states, we do not fully understand the behavior of WOL with regards to SCCM's implementation. We have a collection of clients that are targeted with a weekly 6:30am wake-up on Mondays. There are only two different time-zones (240 and 300) in this collection of clients; however, looking at the SMS_WAKEONLAN_COMMUNICATION_MANAGER, it seems that the component is sending waekup packets at 6:20, 7:20, 8:20, and 11:20 today. If there are only two possible time-zones in the collection that the SMS_WAKEONLAN_COMMUNICATION_MANAGER has to deal with, then why send out packets at four different times?Also, this would still not explain the issue number 2 (the system is just not sending packets at all).
nick
