Managing remote computers (and even local computers only as far away as the office next door) via Remote Desktop Protocol (RDP) tools is both incredibly easy and a big time saver. The biggest limitation of using the Remote Desktop Client (RDC) to manage remote PCs is that it disables the ability to restart a remote PC both via the toolbar and the Windows task manager. Administrators all seem to have their own favorite methods to work around this limitation in the RDC. Common methods include using custom RDP clients instead of the built-in RDC, storing “reboot” executables on the network or internet, and all sorts of scripts that are stored on the ‘net or even typed up by hand.

Working with Microsoft systems I prefer to find the fastest method to work around a problem that doesn’t require ANY custom clients or moving data/files across the network. The first option, custom clients, I avoid because I dislike be slowed down when I’m working from an unfamiliar system or even when my own system(s) crash and are waiting for a rebuild (the client’s systems always come first). The second reason, moving data/files across the network, is best avoided because it’s inevitable that a private or heavily filtered network will restrict access to those files when they’re needed most. So, the best option would seem to be scripts that can be typed in from within the RDC or just finding ways to

I do know one administrator who types so fast that he claims he can manually type a reboot script for Windows XP onto the remote client faster than this method. Personally though, without that typing speed and having a memory that always seems to fail when I try to work too fast, forcing a reboot via the GUI on the remote Windows system is my option of choice. And, here it is, just one command and five clicks to remember long:

• Start > Run… > type “msconfig” and click OK
• Go to the “Startup” tab and uncheck the top box on the list, now check the same box again, so there are no effective changes
• Click OK — you’ll be presented with a “System Configuration” popup with a “Restart” option

• After the restart you’ll also get a popup window promtping you to make the changes permanent or go back into the “msconfig” utility - on a remotely supported system I can’t think of many reasons not to check the “Do not show this again” option

2 Responses to “Remote Desktop Protocol - Easy Remote Reboots Without a Script or Executable”

1. Remote Desktop Protocol - More Remote Reboots Without Script or Executable by Mr. Tweak - Windows Network & Admin Tweaks, on February 17th, 2006 at 4:42 pm, said:
   

   […] As I said in a previous remote desktop reboot article, it’s worth getting to know the default Microsoft tools because they’re always around when everything else is crashed or broken. Here are two additional methods of rebooting a remote PC that has been accessed via Microsoft’s Remote Desktop client (RDC). […]

2. NinoJ, on May 22nd, 2006 at 12:51 am, said:
   

   use command - shutdown -f -r -t 2 to rebbo

Comment on this post below

You can leave a response, or trackback from your own site.