Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

re: Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

Clayton Olley — Wed, 19 Mar 2008 09:47:46 GMT

we get this problem all the time and not just when installing patches... we'll just reboot from the start menu and the same behavior happens... I'm fairly certain the /console switch doesn't help either... we have to either reboot it from the physical console or run a shutdown command from a remote system. This has been plaguing us for years!!!

Hotfix Installs, Remote Desktop and the Reboot that wasn't

News — Wed, 19 Mar 2008 11:03:38 GMT

Every couple of months or so, we'll get a call from an Administrator reporting that his system hung

re: Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

Chris Knight — Wed, 19 Mar 2008 13:20:38 GMT

Great post.

This partly explains why I've been seeing this problem occur since session 0 support got ripped from the RDP client. The other part of the problem is that SBS RWW doesn't know about the session 0 change, so selecting "Log on to the selected computer as administrator" no longer works as expected when the newer client is used on the PC accessing SBS RWW.

re: Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

Chris Knight — Wed, 19 Mar 2008 14:38:37 GMT

Sorry - cut'n'paste error - that should be the "Log on to or resume the console session of the remote computer" option.

re: Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

Hurricane Andrew — Wed, 19 Mar 2008 16:58:05 GMT

We use Process Explorer and use the restart command on it's File\Shutdown menu. Never had any issues.

re: Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

Stephen — Thu, 20 Mar 2008 02:14:27 GMT

@Clayton: we get the same thing a fair bit. we have even tested this - Log in via RDP (with our without console), do a Start/Shutown/Restart, get kicked from the rdp session as you expect, but the server doesn't rebooot

A ping -t to the server never shows a drop packet, but any new rdp sessions will fail.

Connect to the physical console (all our physical boxes are HP so we just iLo, for virtual machines use vmwares admin tool), and when you log in you can reboot.

We have always assumed there is some wierd race condition going on.

re: Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

Boaz Galil — Thu, 20 Mar 2008 10:28:58 GMT

Is it possible to change the location of the patch installation logs ?

Thanks in advance,

Boaz Galil.

re: Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

Christian — Thu, 20 Mar 2008 14:10:32 GMT

@Clayton: Have a look at KB930045 <http://support.microsoft.com/kb/930045> which fixes some but not all race conditions when shutting down a server through a RDP session.

re: Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

Brent — Thu, 25 Sep 2008 02:04:14 GMT

We have seen this behavior for a couple of years now, and although the /console switch to RDP helps, it still occurs often.

What I don't understand, is that for the past year, we have gotten the same thing when we use WSUS server to patch our servers.

I had found some forum discussions that attributed it to the version of WSUS we were using, WSUS 2.0.

Several months ago, I approved patches, (no SP's) for 200 + servers over the weekend.

Of the 200+ patched, 78 did not complete the restart and were left in the state described here.

It was supposed to be fixed in WSUS version 3.0

I have just run a test update from the version 3.01 server, and my test server balked at restarting!

1 additional piece of weirdness: on some of the hanging servers, as soon as a console session is established, whether it's ilo or KVM/IP, the server shuts down and reboots immediately.

Some posters have suggested Anti-Virus is the cause, but this is the 1st thread I have found describing the symptom exactly.

Brent

re: Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

Jose — Sat, 07 Feb 2009 00:32:30 GMT

In doing security patching for a large corporation, we have noticed clearing other ts session is a must. In addition the 'restart now' via wsus or 'start->shutdown' methods appear to cause trouble.

In rare cases we will find another ts session we are unable to kick. Although we have the necessary permissions. This will cause a hang virtually every time.

For best results we use either a remote restart using the shutdown -i command or we run "shutdown /r /t 10 /c "Rebooting for Updates" on the local machine.

re: Hotfix Installs, Remote Desktop and the Reboot that wasn't ...

Brad — Thu, 05 Nov 2009 16:45:42 GMT

I know this is a very old post but we have been getting hit up automatic updates on our servers not rebooting. Many of our servers are set to automatically update and reboot but have been hanging on the "Windows is shutting down" part. I am wondering if what you have stated above applies in that situation. In addition, would setting "No auto-restart for scheduled Automatic Updates installations" to disabled (thus requiring a reboot) in a GPO fix this?

Thanks

Brad