Posted by aidas | Posted in Command line, Windows 2003 | Posted on 03-07-2009
0
Have you ever encountered this annoying window when trying to access Windows server 2003 via Remote Desktop connection?
It draws me mad every time i see it !
So i`ll show you how can we get rid of it in a few seconds.
Lets say that session limit was reached on server named “Testserver”.
Login to another Windows server 2003 in your domain, open command line and type:
query session /server:Testserver
Press “Enter”
In output you will get information about taken sessions: what user is using it, session ID and status.
If you want to reset specific session note session ID you are going to reset. Lets say ID number is 2.
Open command line and the type following:
reset session 2 /server:Testserver
Press “Enter”
Thats all ! The road is clear for now…
This post will show you how to find Windows server 2008 with Terminal server role installed in your domain.
To perform search in domain named “Testdomain.com” domain open command line and type:
query termserver /domain:Testdomain.com
Press “Enter” and you are done !
This post will show you how to manage terminal server session limits.
If you have many disconnected sessions on your Windows server 2003 and other users are complaining about this mess it is time to make some terminal server configurations.
Login to Windows server 2003 and navigate to Administrative Tools > Terminal Services Configuration.
There click on “RDP-Tcp” and select Sessions tab.
Terminal services sessions tab
Ok, here we can change session time outs and override user terminal session settings that are configured (or not) to each user manually in active directory.
In most cases i use following settings on my Windows servers:
End a disconnected session: 1 hour
Active session limit: Never
Idle session limit: 2 hours
When session limit is reached or connection is broken: Disconnect from session
Sometimes you can encounter situation when you try to connect to Terminal server using RDP with Printer redirection enabled but printer doesn`t show in Terminal session. This problem occurs with printer port names that do not begin with COM, USB or LPT. How to deal with that? In that case you must add registry setting to redirect all printer ports. To do that open registry on your Windows XP machine and navigate to:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR
On the Edit menu select New and then DWORD value. Type FilterQueueType and press Enter. On new value right click and select modify. Type FFFFFFFF and click OK. This will enable all ports to be redirected.
That all!
