Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'd like to have something akin to a unix "who" and an option to kick out RDP sessions that are not supposed to be there (i.e. using up the limited number of connections). This is for a win2003 server Standard.

Additional info: this is a devel environment, people all use RDP as Administrator (I know, I know), so kicking out should be by session number or at least by remote IP/machine name, not per user.


share|improve this question
up vote 8 down vote accepted

Refer this post on kicking the users.

The summary of the commands is as follows:

To get a list of the Remote Sessions in the command window (Get the session Id of user to kick out):

qwinsta /server:SERVERIP

To disconnect the remote session:

rwinsta /server:SERVERIP SESSIONID

Also you may want to change the default timeout for idle RDP or here.

share|improve this answer
yup, I just found this post listing also quser and rwinsta:!AFCCA5892B178862!804.entry Thanks! – Ira Oct 29 '09 at 14:11

You should also be able to do this by pulling up Task Manager and going to Users and selecting users to Logoff or Disconnect. Disconnect will close their RDP session, but they can log back in to it. Logoff will... well, log off their current session.

share|improve this answer
That would mean you were on the machine in question. What if you want to connect to a machine that is full already :) – Kip Oct 29 '09 at 16:03

mstsc /console or mstsc /admin should let you always log on, but it will kick off anyone else who's logged in using the same technique.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.