RunningWithBulls.com - The curse of Sanfermin

We have a load of WIndows 2000/Windows 2003 servers in work here.

I manage all of them from my MMC snap-ins - except for one really really important service-Terminal Services.

I can’t believe that MS have not created a TS snap-in, and hear it from the horses mouth:
“Terminal Services Manager doesn’t exist as a snap-in to connect to a remote machine and because the TermService service is a core system service, you can’t even stop it on the local machine, let alone a remote one.”
[Well from an ASP/MSoftie]

But thankfully he shows a nice work around:

==================
Fortunately there is an easy solution. Windows 2000+ (includes Windows XP and 2003) have two command-line tools called qwinsta and rwinsta that can query and reset a remote session.

As long as the logged in user has administrative rights on the non-accessible machine I would run this:

qwinsta /server:12.12.12.12

Where 12.12.12.12 is the IP address or name of the non-accessible machine.
This will display something like this:

> qwinsta /server:12.12.12.12
SESSIONNAME USERNAME ID STATE TYPE DEVICE
console 0 Conn wdcon
rdp-tcp 65536 Listen rdpwd
rdp-tcp#470 Bob 1 Active rdpwd
rdp-tcp#471 Jane 3 Active rdpwd

To disconnect Jane’s session I would type this:
rwinsta /server:12.12.12.12 3
==================

Full text of the post is here.

Very helpful.

Up until now I have had to get to the machine and use this commandline command:
LOGOFF [ sessionname ¦ sessionid ] [ /SERVER:servername ] [ /V ]

Anyway, maybe M$ will look into creating an MMC snapin.