Comments on: Windows Terminal Server and User Auto Log-Off for RDP http://blogs.digitss.com/microsoft/windows-terminal-server-and-user-auto-log-off-for-rdp/ DiGiTSS Team's Programming experience with PHP, MySQL, Ajax, Javascript, jQuery, C# and Microsoft technologies Wed, 21 Jul 2010 16:48:42 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Dharmavirsinh Jhala http://blogs.digitss.com/microsoft/windows-terminal-server-and-user-auto-log-off-for-rdp/comment-page-1/#comment-11089 Dharmavirsinh Jhala Sun, 26 Jul 2009 08:04:51 +0000 http://blogs.digitss.com/?p=274#comment-11089 Thanks Michal. Thanks Michal.

]]> By: Michal http://blogs.digitss.com/microsoft/windows-terminal-server-and-user-auto-log-off-for-rdp/comment-page-1/#comment-11083 Michal Fri, 24 Jul 2009 07:56:53 +0000 http://blogs.digitss.com/?p=274#comment-11083 Actualy there is yet one option how to shoot down the forgotten inactive sessions on the terminal server, even when you are not able to connect to the server that is affected, and you don't even have to restart the server. The trick is to log on to any machine in the domain with domain administrator privileged account, and to run these commands: query session /server:servername this will list all the sessions on the mentioned server, including their state, so you can choose which ID of the session is the correct one to kill in next step. reset session [ID] /server:servername this will kill the session marked by the ID obtained in the previous step. Once this command is finished, you should be good to go to log on the terminal server again. Hope this will help someone, and prevent in such occassion to restart the server, when it is not needed. Actualy there is yet one option how to shoot down the forgotten inactive sessions on the terminal server, even when you are not able to connect to the server that is affected, and you don’t even have to restart the server.

The trick is to log on to any machine in the domain with domain administrator privileged account, and to run these commands:

query session /server:servername

this will list all the sessions on the mentioned server, including their state, so you can choose which ID of the session is the correct one to kill in next step.

reset session [ID] /server:servername

this will kill the session marked by the ID obtained in the previous step. Once this command is finished, you should be good to go to log on the terminal server again.

Hope this will help someone, and prevent in such occassion to restart the server, when it is not needed.

]]>