[THIN] Re: KB: CTX106049 - Published Application Sessions Take 60 Seconds to Log Off when Windows 2003, Service Pack 1 is Installed

  • From: "Kevin Droz" <drozk@xxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Fri, 8 Apr 2005 10:16:19 -0400

I have this problem on my Windows 2000 SP4 Citrix MetaFrame XPa 1.0 SP4.
Anyone have any fixes for this?
  -----Original Message-----
  From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Jim Kenzig Kenzig.com
  Sent: Thursday, April 07, 2005 10:43 PM
  To: thin@xxxxxxxxxxxxx
  Subject: [THIN] KB: CTX106049 - Published Application Sessions Take 60
Seconds to Log Off when Windows 2003, Service Pack 1 is Installed


  Ya I know..stupid design...
  JK
  CTX106049 - Published Application Sessions Take 60 Seconds to Log Off when
Windows 2003, Service Pack 1 is Installed

  This document was published at:
http://support.citrix.com/kb/entry.jspa?externalID=CTX106049


  Document ID: CTX106049, Created on: Apr 1, 2005, Updated: Apr 6, 2005

  Products: Citrix MetaFrame Presentation Server 3.0 for Microsoft Windows
2003, Citrix MetaFrame XP 1.0 for Microsoft Windows 2003

        Symptoms

        Published application sessions take 60 seconds to log off when
Windows 2003, Service Pack 1 is installed.

        Cause

        This is due to Microsoft code changes.

        In Service Pack 1, two instances of userinit.exe are started at
logon. One instance runs for more than 1 minute performing Certification
Auto Enrollment. If you leave your ICA session connected application open
for longer than 60 seconds and then exit the application, the session logs
off from the server immediately and there is no delay.

        Because it takes userinit more than a minute to run the second
instance on load, once 60 seconds have passed, the session will log off
normally.

        However, if logoff occurs or is attempted before the 60 seconds, the
logoff will wait for the second userinit to run, taking at least 60 seconds
causing the delay.

        Resolution

        This behavior is by Microsoft design.


Other related posts: