Filename: ME180018.EXE For: MetaFrame Version 1.8 Replaces: ME180004, ME180007, ME180012, ME180017 Language supported: English (US) Description ----------- This hotfix addresses the following issues: 1. The Windows Terminal Server TCP keep-alive settings had no affect for broken ICA sessions. This hotfix adds a new "ICA keep-alive" feature so the MetaFrame server can recognize broken sessions and take appropriate action. When the ICA keep-alive expires, the server either disconnects or resets the broken session based on the setting "On broken or timed-out connection...", which is configurable for the user or ICA connection. Two registry values control the ICA keep-alive feature. Both values can be manually added to the registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix The ICA keep-alive values are: IcaEnableKeepAlive: REG_DWORD: 0 or 1 When this value is 0, ICA keep-alives are disabled. When this value is set to 1, ICA keep-alives are enabled. The IcaEnableKeepAlive is set to 1 by this hotfix installation. IcaKeepAliveInterval: REG_DWORD: If the IcaEnableKeepAlive value is 1, this value controls the frequency at which ICA keep-alives are sent to the client. This IcaKeepAliveInterval is set to 60 seconds by this hotfix installation. Sixty seconds is also the default interval if this value is not defined but IcaEnableKeepAlive is set to 1. The time that elapses between an ICA broken client connection and the MetaFrame server disconnect (or reset) event may be longer than the IcaKeepAliveInterval. For instance, suppose the IcaKeepAliveInterval is set to 15 seconds. A client's ICA WAN connection is dropped at 12:00:00. The server may not put the session into a disconnected (or reset) state until sometime after 12:00:15, although the session will usually disconnect (or reset) within approximately IcaKeepAliveInterval +2 minutes. This is due to the fact that the TSE TCP/IP stack will retransmit the ICA keep alive packet a number of times at increasing intervals before timing out. Once the TCP/IP stack finishes its retransmissions, the session is disconnected (or reset). The TCP/IP retransmissions is controlled by the Windows Terminal Server TcpMaxDataRetransmissions registry value. See Microsoft Knowledgebase Articles Q120642 and Q170359 for more information. [From Hotfix ME180004] 2. The %SystemRoot%\Jet*.tmp files were not deleted when the system shut down because the Terminal Server Licensing service did not receive notification of a system shutdown. The Service Control Manager sends the SERVICE_CONTROL_SHUTDOWN event synchronously to all services one at a time when a system shutdown begins. A service receives the event only when all services that received the event ahead of it have finished processing the event. If the previous service does not process the event, the following services never receive the event. The system can shut down before a service receives the event, which means a service cannot execute code in its SERVICE_CONTROL_SHUTDOWN event handler. With this hotfix, the ICA Browser service and the Client Network service have been changed to use the CTRL_SHUTDOWN_EVENT event (which is an asynchronous handler) instead of the SERVICE_CONTROL_SHUTDOWN event. This allows other services to execute their SERVICE_CONTROL_SHUTDOWN event handler. This change does not guarantee that the %SystemRoot%\Jet*.tmp files will be deleted during reboot. Even on a base Windows NT Terminal Server installation, it is possible that this problem could still occur even if MetaFrame is not installed because other installed services could have the same issue that the MetaFrame services had prior to this hotfix. In order to delete the old Jet*.tmp files, follow this procedure: 1. Install the hotfix according to the installation instructions below, which includes rebooting the server. 2. At a command prompt, type DEL %SYSTEMROOT%\JET*.TMP Some files will display the message "The process cannot access the file because it is being used by another process." This message can be ignored; these files are currently in use and will be deleted when the system is rebooted. [From Hotfix ME180007] 3. Fixed multiple client printer issues: A. When a user has more than one client printer defined on his/her desktop and launches an anonymous application session, the defined client printers are created on the server side. If the same user changes his/her client default printer on his/her desktop without terminating the first anonymous application session and launches a second anonymous application session from the same desktop, the default printer was incorrect. B. If a user had two separate, concurrent anonymous sessions open on a given server and logged off one session, it was possible that a different user from another client could access the first user's auto-created client printers. This occurred only when the second user happened to use the same anonymous logon name that was previously used for the first user. For instance, suppose the first user was concurrently logged in as "Anon000" and "Anon001". Both user accounts would have access to the client's auto-created printers. If the "Anon001" session was logged off, the security on the client autocreated printers was not updated to reflect the fact that "Anon001" no longer had access to the printers. When a second user happened to log on with the "Anon001" account, the second user had access to the the first client's autocreated printers. C. If a user launched more than one anonymous application session from the same client, the client default printer(s) were not created for the second session. [From Hotfix ME180012] 4. If the system administrator selected the "Prompt for Password" checkbox in the Advanced Connection Settings from the Citrix Connection Configuration utility, any anonymous published application prompted for password. [From Hotfix ME180012] 5. When a new user who requires a password change on initial logon connected to a server farm, she or he was connected to a desktop instead of receiving the password change prompt. [From Hotfix ME180017] 6. If a user changed his NetWare password and password synchronization was turned on, the user was unable to log on with the new password. This hotfix fixes the synchronization. [From Hotfix ME180018] 7. The Win32 Client crashed with Hotfix ME180004 installed. It may also have caused a Dr. Watson in Termsrv.exe. [From Hotfix ME180018] Installation Instructions for Hotfix ME180018 --------------------------------------------- 1. Copy ME180018.EXE to an empty directory on your hard disk and execute the command: ME180018 2. Execute the following command to install the hotfix on your system: HOTFIX /I 3. Shut down and restart your computer. Files Updated ------------- cdmsvc exe 35,088 05/21/99 09:21a chgcdm exe 58,128 05/12/99 10:59a ctxlogof exe 27,920 05/12/99 10:59a ctxlogon exe 43,280 06/09/99 07:01p hotfix exe 83,216 03/15/99 11:56a ibrowser exe 98,064 05/21/99 09:22a pnlchcb dll 9,488 06/09/99 07:01p pnsvc exe 113,424 06/20/99 05:11p wdica sys 89,112 06/18/99 12:44p wsxica dll 39,184 06/18/99 06:57p