Remote Desktop Connections not disconnecting all the way...

I am having a similar problem as WolfManBN25 in case ID#: 22761624.
I have several people who terminal serve onto a server.  They do this several times a day - and not necessarily from the same computer.  Sometimes it can be a thin client and other times it is a desktop PC.  I was receiving Event ID 1517 all over the place.  Also, sometimes when the person tries to log back in all they receive is a blue screen - no login.  I would have to go into the Terminal Services Manager and reset their account.
So, anyway, I have installed UPHClean.  It got rid of the 1517 errors and now I recieve the UPHClean Info 1401 that look like this:  
The following handles in user profile hive DOMAIN\username (S-1-5-21-153723871-2679035580-3975090593-1611) have been remapped because they Rtvscan.exe (2384)
HKCU\Software\Symantec\Symantec Endpoint Protection\AV\Custom Tasks (0xb8c)

Problem is - I still have users getting locked up w/ the blank screen and no login, so I still have to reset the account.  

Any ideas how to get this to stop?  
Thanks!
tacomaroseAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ChiefITCommented:
You can manage TS through group policy to include a timeout of the connection:

http://www.windowsnetworking.com/articles_tutorials/Terminal-Services-Group-Policy.html

I think these are the two policys you might want to look at on that page:

The following is a direct quote from above article:
_________________________________________________________________________________
Remove disconnect option from Shut Down dialog - This policy is found under Computer Configuration\Administrative Templates\Windows Components\Terminal Services and setting it to Enabled can help enhance the performance of your Terminal server. Reason is, it prevents users from using the Shut Down dialog and disconnecting their Terminal Services session instead of terminating their session. If a Terminal Services session is disconnected, the session continues to run on the Terminal server and uses up server resources (processor, memory, disk). If a session is terminated instead, the resources used by the session are released for use for other sessions. So if your Terminal server is working near capacity to support your users, it's important that users not be allowed to disconnect their sessions and leave them running on the server and hogging resources that could be used by other users. The downside of this policy is that it only removes the disconnect option from the Shut Down dialog and doesn't prevent users from disconnecting their session in other ways, for example by disabling their network connection. As a result, you should also configure the next policy as well.
Sets time limit for disconnected sessions - This policy is found under both Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Sessions and User Configuration\Administrative Templates\Windows Components\Terminal Services\Sessions and it can be used in conjunction of the previous policy above to help enhance your Terminal server's performance. By configuring disconnected sessions to time out after a short period of time, you can ensure that resources are released for your server when a Terminal Services user no longer requires them. Note that this setting has no effect on console or Remote Desktop sessions.
_______________________________________________________________________________
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tacomaroseAuthor Commented:
I have implemented these changes, and since then I have had no phone calls of lockouts.  I realize that it has been only 4 hours, but it is looking very promising.  
Thanks!
0
tacomaroseAuthor Commented:
Hi -
Sorry to bother you again.  
Is there a way where I can setup Terminal Services so the users do not use their roaming profile?  And, even maybe, use a default profile?
Currently, when they use RD to login it automatically runs an app.  I'm wondering if there is a way to set it up where all they get when they login is an icon to run the app rather than it automatically starting.  Is that possible?
Thanks!
0
ChiefITCommented:
You are not bothering me:

Let me look this up and get back with you. I think you should always have a separate profile for TS instead of using the domain profile.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.