So I'm working alot with a client through a Remote Desktop Connection. This is a scenario where I log into a computer remotely using terminal services via the Window Remote Desktop Connection utility. I'm sure many of you have the same kind of setup with your remote clients.
.
The problem is that the standard terminal services setup allows only 3 connections at a time. That means only three users can be on the remote desktop at one time. So it's important that after working with a remote computer, any user explictly logs out by clicking LogOff. If they don't log off, the terminal services will hold the connection as being used.
.
The bane of my existance these days stems from this limitation. Inevitably, some goofball forgets to log out and I'm essentially left with this lovely message.

.
At this point, I can send out a nasty-gram email saying something like
"Hey, if any of you tools are still logged into the remote desktop, get out. I've got work to do."
.
But I'm a guru. So I typically unlock the remote computer myself using these magic steps:
.
1. Click Start – Run
2. Enter mstsc -v:204.204.204.40 /f–console (replacing the ip address for the server)

3. Log into the remote desktop using your normal credentials
4. Click Start | Control Panel | Administrative Tools | Terminal Services Manager
5. Right click on any disconnected users and click Reset.
6. Log Out of the Remote Computer
.
Now that connections are free, I can log back into the server using the conventional method.
That's right….Douches beware….I will shut you down if you stand in between me and my milestone goals.
Why don't you just open Terminal Service Manager on your local machine, connect to the remote machine and log the tools off?
Mike -
Great stuff. Can you administer an electric shock through the keyboard?
I use http://www.beamyourscreen.com to do stuff like that, but of course that requires a person on the other side of the fence…
Nicely integrates with your website too:
http://www.jkp-ads.com/CustomerArea/remotesupport.asp