CTX105790 - Hotfix XE104W2K3001 - For MetaFrame XP 1.0 for Windows 2003 Server This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX105790 Document ID: CTX105790, Created on: Feb 18, 2005, Updated: Feb 25, 2005 Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2003 Hotfix readme name: XE104W2K3001.HTM Hotfix package name: XE104W2K3001.MSP For: MetaFrame XP 1.0 with Feature Release 3/Service Pack 4 for Windows 2003 Replaces: None Date: January, 2005 Language supported: English (US) Readme version: 1.0 Note: This hotfix can be applied only to a Windows 2003 Server with MetaFrame XP Version 1.0 with Feature Release 3 and Service Pack 4 installed. Where to Find Documentation This document describes the issue(s) solved by this hotfix and includes installation instructions. You can find more information about MetaFrame for Windows in the Administrator's Guide. The Administrator's Guide is in the \DOCS directory on the Citrix MetaFrame Server CD. All product documentation is also available from the Citrix Web site at http://www.citrix.com/support. The Administrator's Guide is in an Adobe Portable Document (PDF) format file. To view, search, and print the documentation, you need Adobe Reader 4 or above. You can download the Reader for free from the Adobe Web site at http://www.adobe.com. Issue(s) Resolved in this Hotfix Caution! Several items in this hotfix may require you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. 1. Due to an access violation, a custom MFCOM application was experiencing a fatal error while attempting to obtain Citrix virtual channel policy information. This occurred because the reference count of the wrong MFCOM object was incremented, which resulted in the original MFCOM object being freed while it was still in use. This hotfix corrects the issue. [From Hotfix XE104W2K3001][#90079] 2. In large farms, when replicating an updated version of a printer driver to a server that was using a previous version of the same driver, the update failed on the destination server even though the event viewer on the source server reported the update as successful. This occurred because the two versions of the specific driver had inconsistent printer monitor configuration information in the registry. This hotfix corrects the issue by forcing the installation of the print monitor on the destination server. If the monitor is not already installed, installation is performed; otherwise, the driver installation process simply skips this step and continues as expected. [From Hotfix XE104W2K3001][#92899] 3. The feature that allows you to limit application launches to one concurrent instance per user did not work when a user connected using a UPN name. This occurred because the Independent Management Architecture (IMA) service, when comparing the user names associated with sessions that were already already open, did not check against UPN names. This hotfix corrects the issue. [From Hotfix XE104W2K3001][#94371] 4. In farms with more than one server, smart card users could not reconnect to disconnected sessions. This occurred because sessions of smart card users were not associated with actual user or computer names, and therefore the server hosting the disconnected session could not be identified. This hotfix corrects the issue. [From Hotfix XE104W2K3001][#101409] 5. If a server had more than one network interface card (NIC), but not all cards were bound to ICA-TCP listeners, incoming ICA connections were attempted on all NICs, including those not bound to ICA-TCP listeners. This occurred because MetaFrame operated under the assumption that all NICs were bound to ICA-TCP listeners. This hotfix corrects the issue. [From Hotfix XE104W2K3001][#104098] Installation Instructions Note: This hotfix is packaged with Microsoft Windows Installer. You can deploy the hotfix package to a group of servers using Microsoft Active Directory Group Policy Object or using Citrix Installation Manager. For more information, see the Citrix server Administrator?s Guide or the Citrix Installation Manager Administrator?s Guide. 1. Download the hotfix package from the Hotfixes and Service Packs page of the Citrix Web site at http://www.citrix.com. 2. Copy the hotfix package to an empty directory on the hard drive of the MetaFrame server. 3. Close all applications. 4. Run the executable. 5. Shut down and restart the server. Note: To install this hotfix silently, use the /q option after the executable. For example: msiexec /P XE104W2K3001.MSP /q Using the /q option without additional options automatically restarts the server. For additional information about msiexec, see the Microsoft Web site at http://www.microsoft.com. Search on keyword msiexec. Uninstallation Instructions 1. From the Start menu, select Setting > Control Panel. 2. In Control Panel, double-click Add/Remove Programs. 3. Highlight the hotfix you want to uninstall and click Remove. 4. Follow the directions on-screen. Files Updated CPatch.exe 25,600 02/16/2005 07:09p mfappsal.dll 135,304 01/24/2005 03:09p mfappss.dll 450,696 01/24/2005 03:09p mfbrowsersal.dll 17,544 01/24/2005 03:09p mfbrowserss.dll 131,208 01/24/2005 03:09p mfcom.exe 221,184 01/24/2005 03:08p mfcomsrv.dll 454,656 01/20/2005 07:02p mfcontentsal.dll 25,736 01/24/2005 03:09p mfcontentss.dll 86,152 01/24/2005 03:09p mferror.dll 15,872 01/24/2005 03:08p mfevent.dll 12,288 01/24/2005 03:08p mfpnsal.dll 37,000 01/24/2005 03:09p mfpnss.dll 143,496 01/24/2005 03:09p mfprintsal.dll 69,768 01/24/2005 03:09p mfprintss.dll 397,448 01/24/2005 03:09p mfrpcss.dll 204,936 01/24/2005 03:09p mfrules.dll 48,128 01/24/2005 03:08p mfsrvsal.dll 172,168 01/24/2005 03:09p mfsrvss.dll 442,504 01/24/2005 03:09p mfstatus.dll 13,824 01/24/2005 03:08p