No announcement yet.

Terminal Server 2000

  • Filter
  • Time
  • Show
Clear All
new posts

  • Terminal Server 2000


    I Have Terminal Server 2000 and since last week thr log-off proccess taks too long (A few minutes!!!)
    What can ve the reason ?

  • #2
    Re: Terminal Server 2000

    Typical problems with logoff is the users profile does not unload properly which can cause issues. Take a look at the User Profile Hive Cleanup Service:


    The User Profile Hive Cleanup service helps to ensure user sessions are completely terminated when a user logs off. System processes and applications occasionally maintain connections to registry keys in the user profile after a user logs off. In those cases the user session is prevented from completely ending. This can result in problems when using Roaming User Profiles in a server environment or when using locked profiles as implemented through the Shared Computer Toolkit for Windows XP.

    On Windows 2000 you can benefit from this service if the application event log shows event id 1000 where the message text indicates that the profile is not unloading and that the error is "Access is denied". On Windows XP and Windows Server 2003 either event ids 1517 and 1524 indicate the same profile unload problem.

    To accomplish this the service monitors for logged off users that still have registry hives loaded. When that happens the service determines which application have handles opened to the hives and releases them. It logs the application name and what registry keys were left open. After this the system finishes unloading the profile.
    Hope this helps

    Michael Armstrong
    MCITP: EA, MCTS, MCSE 2003, MCSA 2003: Messaging, CCA, VCP 3.5, 4, 5, VCAP5-DCD, VCAP5-DCA, ITIL, MCP, PGP Certified Technician

    ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **


    • #3
      Re: Terminal Server 2000

      Usually this problem ocuur due application computability issue.

      1. Please download and run on the server:

      Map each application/process.

      2. Disable/uninstall the antivirus and check if this issue return.

      3. If so, copy from Windows XP/2003 msconfig and use it to disable

      any auto load software (none Microsoft) and check this issue again.

      4. If step 3 resolved this issue, add each time a auto start application and

      check if the issue occur again.

      * Note: Please upgrade all the application on the TS to the latest version/hotfix +
      consider to move to Windows 2003/2008 TS.
      Best Regards,

      Yuval Sinay

      LinkedIn:, Blog: