The postings on this site are my own and do not represent my Employer's positions, advice or strategies.

LifeAsBob

  Tuesday, December 18, 2018

 


Home
Blog
bob tech
Calendar
Contact Bob
Pictures
VW Buses
HomeBrew
Cook Book

 

Thomas 3rd Birthday_22.JPG

  bob Links
Yeast Culturing
This beer is good for you. This is draft beer. Stick with the beer. Let's go and beat this guy up and come back and drink some more beer. - Ernest Hemingway, To Have and Have Not
Wider View Insert

Cluster
DOS
IBM - AS400
MOM
Performance Counters
Service Broker
SQL Server
Windows OS
     Standard Terminal Se...
     Managing Terminal Se...
     Recovering Space on ...

Insert Category

Will be added as a sub-category of, Windows OS
Managing Terminal Services Sessions Remotely

Managing Terminal Services Sessions Remotely

I regularly administer Windows 2000 Server and Windows Server 2003 machine using Terminal Services.  In W2K I use Terminal Services in Administration mode and in W2K3 I use Remote Desktop.  Basically this is the same thing but it's packaged a bit differently on the two OSes.  In both situations there are only 2 users allowed for administration so occasionally both are used up and I can't access the server.  This may happen if two people are legitimately using the servers or if someone forgot to log off.  Yes, I do have the settings set to automatically disconnect and/or log off a user after X minutes of inactivity but even with that there are times when I need to be able to manage this remotely.

You would think this would be as easy as connecting to the remote server by adding the Terminal Services Manager snap-in to a MMC console or remotely stopping and starting the service (in a pinch).  Strangely, these obvious solutions aren't available.  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.

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.

For example, let's say that I can't gain access to a server using Terminal Services because both sessions are used up.  I can use another server to check the status of the first one.  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

Now I know that Bob and Jane are the two that are logged in.  Since Jane left the office 20 minutes ago I know that she forgot to log off.  I don't know where Bob is but I only need one session so I'll ignore him for now.

To disconnect Jane's session I would type this:

rwinsta /server:12.12.12.12 3

Notice the 3 which is the session ID I found from using qwinsta above.

Yet another option with W2K3 is a new feature that lets you connect to the desktop directly and gain a 3rd session. 

If you're like me, you probably noticed that rwinsta and qwinsta seems like strange names.  This came from the Citrix Metaframe days which Terminal Services has descended from.  It stands for:

qwinsta = Query WINdows STAtion
rwinsta = Reset WINdows STAtion

One final comment.  Microsoft has replaced these two tools with Query but since qwinsta and rwinsta is fully compatible with W2K WinXP and W2K3 I choose to use it instead.