Solved

orphan processes in Terminal Server 2008

Posted on 2014-09-15
1
514 Views
Last Modified: 2014-10-10
I have a problem with a new Terminal Server 2008 I installed.  I have a domain running on a 2003 machine which hosts a TS and a TS License server.  For this Terminal Server 2003, I was able to specify on the domain user's profile a setting that would tell the Terminal server to kill its child processes if the session got disconnected.  This mechanism prevented me from having orphan sessions, as my users like to click on the X of the remote desktop window, rather than close their programs and log out.

Now, this new Terminal Server 2008 (and license server) are installed in a server which is not part of the domain.  Therefore, the user ids used to log into this TS are local to the machine.  As such, I don't have a way to tell the Terminal Server to kill its children when my users disconnect (instead of logging out) so I end up with lots of orphan sessions.  On top of all, they use the host to run software that uses floating licenses per user, so all those licenses remain in use while the orphan child of the TS is still alive, and I end up running out of licenses pretty quickly.

How can I configure the Terminal Server 2008 to kill all its children processes when the user disconnects?  I haven't found how to do this and I'm losing my brain!  Please, someone guide me on this one.
0
Comment
Question by:samjomoore
1 Comment
 
LVL 1

Accepted Solution

by:
Konstantinos Tampourakis earned 500 total points
Comment Utility
Try this,
go to Start->Administrative Tools->Terminal Services(Folder)->Terminal Services Configuration

Under "Connections" you'll find RDP-Tcp (Microsoft RDP 6.1), right click on it and select Properties, go to tab Sessions and check the box "Override user settings"->End a disconnected session and choose an appropiate time for Terminal server to end the sessions.

Regards,
Konstantinos
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Suggested Solutions

A procedure for exporting installed hotfix details of remote computers using powershell
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

5 Experts available now in Live!

Get 1:1 Help Now