See http://blog.configmgrftw.com/?p=88 and http://blog.configmgrftw.com/?p=89
J From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Wednesday, September 25, 2013 5:17 PM To: [email protected] Subject: RE: [mssms] Random unplanned reboots after update deployment Check the Windows Application or System event logs. If the Windows Update Agent was the cause of the reboot, it will be noted in there. Cheers, Trevor Sullivan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Wednesday, September 25, 2013 5:02 PM To: '[email protected]'; '[email protected]' Subject: RE: [mssms] Random unplanned reboots after update deployment This is a known issue. we saw it to. I think it's automatic updates settings but I'll check tomorrow to be sure, unless someone else replies sooner. -Daniel Ratliff -----Original Message----- From: Reavis, Mike [[email protected]<mailto:[email protected]>] Sent: Wednesday, September 25, 2013 05:57 PM Eastern Standard Time To: [email protected]<mailto:[email protected]> Subject: [mssms] Random unplanned reboots after update deployment We are running an SCCM 2012 SP1 environment, and after many meetings and discussions we convinced management to change over from the WSUS servers to letting SCCM deliver updates. The GPOs that had configured WSUS have all been set to not configured, a GPUpdate run on all systems, the client policy set to enable the update agent and a policy reset on all clients 2 days later as well to ensure they have the current SCCM policies. When we deployed to the pilot systems we included a reboot to ensure the updates were applied for valid testing, completed with a 6 hour countdown time. This worked great for the most part, only issue was that the countdown was based on when the client saw and installed the updates sometimes caused the reboots to happen with minimal warning. We believe this we have resolved this by adjusting our deadlines. Now we setup our primary deployments for update deployment to sections of our whole organization and suppressed the reboots, but had to put them on hold due to reports from some of our offices of systems rebooting with no warning. From what I saw on the reboot coordinator log it appeared that the system rebooted around 3am, but the user had no warning. In the past I ran updates in both 2003 and 2007 shops and when I suppressed the reboots, the system did not reboot. We need to find out now what caused the reboots before we can continue deploy the updates. I ran the whole process on a VM client last night and it appear to be working normal, with a nag from SCCM to reboot that I had an option to cancel. No countdown timers, I thought all was good. I came in this morning and the system had rebooted. I reset the lab with 2 VMs this morning, they patched, and have the nag in the system tray. 3 hours later they are still idling with reboot. My best guess is that some left over Windows Update function may be seeing the reboot pending state and causing the reboots, but no proof at this point. Where should I look to see what is actually causing the reboots? As the timer never shows up in the sys tray I am thinking it has to be outside of SCCM but after 2 days of log trolling too befuddled to see it. Thanks Mike Reavis ________________________________ This e-mail message is for the sole use of the intended recipient(s)and may contain confidential and privileged information of Transaction Network Services. Any unauthorised review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
