Solved

Remote Desktop Connections not disconnecting all the way...

Posted on 2008-10-03
4
1,034 Views
Last Modified: 2013-11-21
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!
0
Comment
Question by:tacomarose
  • 2
  • 2
4 Comments
 
LVL 38

Accepted Solution

by:
ChiefIT earned 500 total points
ID: 22640129
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
 

Author Closing Comment

by:tacomarose
ID: 31502955
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
 

Author Comment

by:tacomarose
ID: 22654920
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
 
LVL 38

Expert Comment

by:ChiefIT
ID: 22656173
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

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found listed in my profile here: http:…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

707 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

12 Experts available now in Live!

Get 1:1 Help Now