• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 792
  • Last Modified:

Terminal server window won't close when client logs off

When users log off of their terminal server session, they get the loggin off dialog box and then they have the blue desktop on their screen for a very long time.  They end up closing the sessino by clicking the windows close box.  This is something that has started all of a sudden and it seems to be affecting everyone.  The event log has several Application Hung event (mostly IE) but is is not very many and not from every day.

Any help??
0
beyondt
Asked:
beyondt
  • 8
  • 4
  • 2
1 Solution
 
Cláudio RodriguesFounder and CEOCommented:
The first thing I would try is to have UPHClean installed on the TS.
Secondly I would use TSADMIN to monitor one of the sessions to determine which process is left running (there is something running for sure if the session is not closing completely).


Cláudio Rodrigues

Microsoft MVP
Windows Server - Terminal Services
0
 
beyondtAuthor Commented:
Do I run TSADMIN from a workstation?  How do you start it?
0
 
Cláudio RodriguesFounder and CEOCommented:
You run TSADMIN on the terminal server. Logon to it as administrator.

Cláudio Rodrigues

Microsoft MVP
Windows Server - Terminal Services
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
beyondtAuthor Commented:
I installed UPHClean and that had no affect.  I have opened Term Manager and can't see anything that looks out of the ordinary.
It turns out that the logout does not actually hang but is very delayed (it also seems to be logging in slowly) - about 1-2 minutes.

Any ideas?

Thanks
0
 
Cláudio RodriguesFounder and CEOCommented:
What is the profile size for the users? Are these roaming profiles?

Cláudio Rodrigues

Microsoft MVP
Windows Server - Terminal Services
0
 
beyondtAuthor Commented:
They do not use roaming profiles.  But, in each of the profiles, the Locoal Settings\Temporary Internet Files\Content.IE5 folder is huge.  It ranges form several hundred MB to over a GB.
I assume that this is the problem...Is it safe to delete all of theose files?  Should I delete the Content IE5 folder?

Thanks!
0
 
beyondtAuthor Commented:
There are a huge amount of folders in the Content.IE5 folder( OVWR2ZW, 4FIF5MP, etc...)  Do these indicate a problem i.e. virus?
0
 
Cláudio RodriguesFounder and CEOCommented:
Well if you have no roaming profile, the local profile size should not matter but of course it is always good to keep these small.
You can delete these folders for sure. It is just the temporary internet files.


Cláudio Rodrigues

Microsoft MVP
Windows Server - Terminal Services
0
 
beyondtAuthor Commented:
I deleted the files but it did not make a differentc.
Any other thoughts as to why it is happening?

Thanks
0
 
beyondtAuthor Commented:
It turned out that Symantec Endpoint Protection was the problem.  The client agent was installed as a managed agent and not a stand-alone.  This was the problem.
0
 
MiffanweeCommented:
"It turned out that Symantec Endpoint Protection was the problem.  The client agent was installed as a managed agent and not a stand-alone.  This was the problem. "

WOOOOO Please can you tell me more about this?
I have this problem and my TS clients have Endpoint installed.

Please explain?
Thanks
Miff
0
 
beyondtAuthor Commented:
I contacted Microsoft on this issue and they looked at the registry and everything looked fine.  The suggested uninstalling Symantec EndPoint.  When I uninstalled it from the client, the logoff delay from the terminal server woked fine.  I reinstalled EndPoint and the logoff was delayed.
My solution was to unistall EndPoint clients and then reinstall it locally as an Unmanaged client.  After that all was fine.

My ulitamate solution was to replace Symantec EndPoint with Trend Micro Worry-Free Business Security.  I have replaced all of my clients' Symantec with Trend Micro.  I find it effective and a very user-friendly interface.  Good tech support also.

I hope this helps.
0
 
MiffanweeCommented:
Just to clarify....

Are you saying install the ENdpoint to the TERMINAL SERVER 2003 as an unmanaged client (effectively making all log clients to the TS unmanaged??)

Wonder why this has worked fine for approx 1 year and now slow logoffs?
Thanks
Miff
0
 
beyondtAuthor Commented:
Sorry for the confusion (this took place a year ago and my notes aren't as clear as the should be).  Yes, I installed the Endpoint on the server as an unmanages client.  The Endpoint management council was actually installed on an XP box and was managing the Antivirus from there.

That was what drove me crazy...why did it all of a sudden start acting up (it may have started happening sooner without users letting me know).  MS could not aswer that and I try not to call Symantec unless I have several hours available to wait for someone to answer the phone.  It may be because the users were utilizing more and more on the terminal server.  They run and Access DB from the server and also MS office, so possible, when someone logged of, the server had more to scan before closing the session.  That is just a guess through.
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 8
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now