They told me it needed to be done by 9 AM. I knew it wasn’t true.
*From:* [email protected] [mailto: [email protected]] *On Behalf Of *Susan E Bradley *Sent:* Monday, May 22, 2017 3:26 PM *To:* [email protected] *Subject:* Re: [NTSysADM] Long time for reboot after May patching Your adjustment to the maintenance window made me smile. Yeah it got stuck in shut down/start up. On 5/22/2017 12:10 PM, Charles F Sullivan wrote: So after 7 plus hours the spinning beads began to make me dizzy. I powered off the VM, powered it on and checked. All of the patches installed successfully. There was absolutely no mention of badness in the Event Logs. No unexpected shutdown or dump file. There was a gap in all of the logs from 7:21 to 14:23. The last one in the System Log was, as expected, “The system is shutting down at 7:21”. It’s as if the server wasn’t really running even though it also wasn’t shut down. None of this surprises me much, but it’s a critical server so I didn’t want to take a chance. It runs a parking revenue application, but today is commencement day so they left the arms up on the parking machines. Thus I had all day to get it done. *From:* [email protected] [mailto: [email protected]] *On Behalf Of *Susan E Bradley *Sent:* Monday, May 22, 2017 1:14 PM *To:* [email protected] *Subject:* Re: [NTSysADM] Long time for reboot after May patching There was a servicing stack update that unless you hit control-alt-delete it would sit there. I would ask myself... self? Do I have a good backup? If I answered yes I would hit a hard reset and see what happens. On 5/22/2017 9:45 AM, Charles F Sullivan wrote: I have a Windows 2012 R2 server that rebooted over 4 hours ago to complete patching and it’s still showing the spinning wheel and the Windows logo. I had 3 others made from the same image that had no issues at all. These are all WMware VMs. I’m not sure if this is the shutdown or startup phase, but I’m guessing startup. Hitting ctrl, alt, del (technically ctrl, alt, insert in the WMware Console) did no good. (I don’t think this is quite the state where that problem applies.) Because there is no network connectivity I feel pretty helpless since I can’t check logs, stop services or send a reboot command. Has anyone else seen this? If so, how long did you wait before you powered off? Or did you not have to? I saw at least one post on the Patch Management list where someone else had the same problem after the May patches. His server came back on its own eventually, but I don’t think it took 4 plus hours. The application is not in use today, which is why they chose it as the patching day, so I probably have another 2 hours before I have no choice but to power off. Thanks.
