Thursday, January 15, 2009

Windows, Remote Desktop, Connecting to Console

If you are a Sys Admin for windows hosts, by now most likely at some point the following has happened:

1) Receive the following email "Dear Johnny, I tried logging in to server xyz and was told all the Remote Desktop sessions are in use, can you clear some?"

2) You may try connecting and get the same error. So then you may try logging in via a Dell Remote Access Card or an HP Ilo card to make the change.

Microsoft Remote Desktop services are limited to two connections when used in Remote Administration mode. So once those 2 connections are used, no one else can connect. This becomes troublesome if you do not have a policy to log off disconnected sessions.
Microsoft gives you the ability to connect to a 3rd session, the console session by using remote desktop with a certain switch.

In Windows XP SP2, you run from the command line: mstsc /console
In Windows XP SP3, and Vista you run: mstsc /admin

These commands will bring up a normal Remote Desktop client, but instead of connection to the two typical remote desktop sessions, it will connect to the console. This allows you to clear disconnected sessions. In turn you can also allow others to have this information, so that when they cannot connect, instead of emailing you, they logon to the console session and clear connections themselves.

The nice thing is, if you try to logon the console session, and someone else is already connected, you can force them off :)

-Dravor

1 comment:

Anonymous said...

You could try RHUB http://www.rhubcom.com solution for your remote desktop needs. It is compatible with both PC and Mac. The System provides instant remote control, remote control speed that is 3 times faster than Microsoft remote desktop, and supports multiple concurrent users. It comes with a host of other advanced features that enable complete control of the Remote PC.