Thu, Feb 14 2008 12:29
bradley
Give yourself a back door
Two for Two - The Official Blog of the SBS "Diva":
http://msmvps.com/blogs/bradley/archive/2008/02/13/two-for-two.aspx
A note on this. The reboot issue is seen both before and after patching at times. It's sporatic and your best proactive stance to be prepared for it is to have alternative means to reboot the box. That means you install Ilo's and Drac cards in Servers. Or you leave a backdoor in another server or workstation so that you can get on the network and do a remote shutdown script to reboot the box.
A little command line comes in handy - The Official Blog of the SBS "Diva":
http://msmvps.com/blogs/bradley/archive/2006/08/16/107913.aspx
You click start-shutdown-reboot.
You enter the reason for the reboot.
You click okay to start the reboot process.
It begins the shutdown.
You lose the remote desktop/TS session.
The system doesn't complete the reboot process and is sitting there with 3389 not responding and the system not completed the reboot session.
The way to recover is to get onto some other system (RWW to a desktop) and run a remote shutdown script.
shutdown -r -m \\nameofcomputer
add -f to force a shutdown/reboot
Alternatively I've seen where TS/3389 doesn't respond on the way back up if something else grabs 3389 on the way up (There's a KB -- You receive a "The server may be too busy" error message when you try to connect to Terminal Services on a Small Business Server 2000 computer: http://support.microsoft.com/kb/329155 for the 2000 era.. haven't seen it as much in the 2k3 era.
Bottom line when remotely patching, be aware that we are seeing a bit more of an uptick of this issue and plan your processes accordingly. Give yourself a backdoor this month, just in case.
Filed under: Patching issues
![[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.]](http://www.sbslinks.com/images/headertop.png "There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not!")