Filename: ica32.exe, ica32.msi, ica32a.exe, ica32a.msi, ica32t.exe, wfica.cab, wficat.cab For: Citrix ICA Win32 Client (ICA 32-bit Windows Client) Replaces: All versions prior to January 2002 Note: This readme includes information contained in the September 2001 client readme. Date: January 2002 Language: English (US) Description ----------- The ICA 32-bit Windows Client supports the following platforms: Windows XP Windows 2000 Windows 98 Windows 95 Windows Me Windows NT 4.0 Windows NT 3.51 Where to Find Documentation --------------------------- This document contains last-minute information about the ICA Win32 Client. For more information about the ICA Win32 Client, see the Citrix ICA Client Administrator’s Guide for the ICA Win32 Clients, available in an Adobe Portable Document Format (PDF) file (ICA_Win32_Guide.PDF). The file is in the \DOC directory on the Citrix ICA Client CD. Use the Adobe Acrobat Reader or Exchange program to view PDF files. You can download Acrobat Reader for free from the Adobe Web site at http://www.adobe.com. You can also find documentation on the Citrix Web at * http://www.citrix.com/download. On the Downloads page, click ICA Clients * http://www.citrix.com/support. On the Services Portfolio page, click Product Documentation and choose ICA Clients Overview of the ICA Win32 Clients ---------------------------------- To choose which ICA Win32 Client(s) to deploy in your enterprise, decide how your users will access published applications. If you are using MetaFrame XP in conjunction with Citrix NFuse, you can deliver application sets to users in two ways. You can use the ICA Win32 Web Client with NFuse to publish links to applications to a Web page on your corporate Intranet or the Internet. Users run a standard Web browser to access the Web page that contains the links to their applications. The Web Client includes the engine needed to launch published applications. You can also use the ICA Win 32 Program Neighborhood Agent with NFuse to "push" links to applications directly to users’ Windows desktops. Because users do not run a Web browser to view a Web page, accessing remote applications is just like accessing local applications. All client configuration is done at the server level in an XML file. Users connect to the XML file using HTTP or HTTPS to retrieve configuration, enumeration, and launch information. Because the Program Neighborhood Agent uses HTTP to pass the XML data, it is easy to use it with a firewall. If you do not want to deliver applications using NFuse, publish the applications for direct access. To directly access applications published on MetaFrame XP servers, users launch the ICA Win32 Program Neighborhood Client to browse for application sets or create custom ICA connections to Citrix servers or published applications. Features Included in the September 2001 Release ----------------------------------------------- The following new features are supported in Version 6.20 of the ICA Win32 Clients. For information about enabling and configuring the following features on MetaFrame XP servers, see the MetaFrame XP Administrator’s Guide delivered with Feature Release 1 of MetaFrame XP Version 1.0. In addition to support for new features, Version 6.20 of the ICA Win32 Clients includes performance enhancements in the following areas: ICA display Client printer management Features that are marked with an asterisk (*) indicate that the MetaFrame XP server must be licensed for Feature Release 1. Features that are not marked need to have Service Pack 1 for MetaFrame XP installed. 1. Citrix Program Neighborhood Agent With Citrix Program Neighborhood Agent, you can "push" links to remote applications directly to your users’ Windows desktops. Users do not have to open additional software, such as a Web browser, to launch applications published on MetaFrame XP servers. With the Program Neighborhood Agent, you place links to NFuse-enabled published applications in the user’s Start menu, on the Windows desktop, or in the Windows System Tray. You can integrate remote applications into the Windows desktop so that they appear as locally accessed applications to the user. You configure Program Neighborhood Agent settings on the NFuse server, allowing you to control connections and application sets from a central location. XML data is passed between the Program Neighborhood Agent and the NFuse server using HTTP or HTTPS and can pass through firewalls using port 80. The Program Neighborhood Agent supports the following: Automatically refreshing application icons Pass-through authentication Secure Sockets Layer For information about working with the configuration file on the NFuse server, see Chapter 6 of the NFuse 1.6 Administrator’s Guide. 2. Secure Sockets Layer Support for ICA Citrix SSL Relay provides the ability to secure data communications using the Secure Sockets Layer (SSL) protocol. SSL is the security standard for communication across the Internet. SSL provides server authentication, encryption of the data stream, and message integrity checks. You can use Citrix SSL Relay to secure communications between an SSL-enabled ICA Win32 Client and a MetaFrame server. Citrix SSL Relay uses Version 3.0 of SSL. 3. Universal Print Driver Support * The Citrix Universal Print Driver is a standard Windows 2000 or Windows NT print driver that encapsulates print jobs in PCL4 format. A client-based interpreter renders the print job using the client Device's local print driver and printing services. The Universal Print Driver renders print jobs in monochrome at up to 300 dots per inch on a standard set of forms. Using the Universal Print Driver results in smaller print jobs, which can have a significant impact on printing over WAN or dial-up connections. If the MetaFrame server is configured to automatically create both native driver and Universal Print Driver printers on the client device, the user must explicitly select a printer to process print jobs. If the print job requires color or advanced printing options such as duplex printing, the user must select the standard printer, which uses the printer’s native driver. 4. Auto Client Reconnect * ICA sessions can be dropped because of unreliable networks, highly variable network latency, or range limitations of wireless devices. The auto client reconnect feature is triggered when the ICA Client detects a disconnected session. When this feature is enabled on a MetaFrame XP server, users do not have to reconnect manually or reenter logon credentials to continue working. Automatic reconnection does not occur if users exit applications without logging off. 5. Windows Installer Packages for ICA Win32 Clients The ICA Win32 full Program Neighborhood Client and the Program Neighborhood Agent are available in Microsoft Windows installer packages (.msi files), so you can use Windows Installer technology to deploy and install them. You can distribute the ICA Win32 Client installer package files using Microsoft’s Systems Management Server or Active Directory. 6. Published Content Support * Citrix administrators can "push" content files, including documents, Web pages, video presentations, and sound files, to users. You publish content files on the MetaFrame XP server in the same manner as applications. Users view or play the published content files with a content viewer or player stored locally on the client device. 7. Novell Directory Services Support * When users launch ICA Win32 Client software, they can log on and be authenticated using their NDS credentials. Supported NDS credentials are user name (or distinguished name), password, directory tree, and context. NDS support is integrated into the following: Program Neighborhood and Program Neighborhood Agent. If NDS is enabled in the MetaFrame XP farm, NDS users enter their credentials on an NDS tab on the ICA Client logon screen. If users have the Novell Client (Version 4.8) installed, they can browse the NDS tree to choose their context. See Chapter 6 of the NFuse 1.6 Administrator’s Guide for information about configuring the Program Neighborhood Agent for NDS. Pass-Through Authentication. If users have the Novell Client (Version 4.8) installed, their credentials can be passed to the MetaFrame XP server, eliminating the need for multiple system and application authentications. To enable pass-through authentication, set the "Use NetWare Credentials" value in Novell Zenworks for Desktops dynamic local user policy package to On. Custom ICA Connections. When users run the Add New ICA Connection wizard, they must enter a distinguished name in the user name field and a password in the password field. Users must leave the domain field blank. NFuse Version 1.6. NDS users enter their credentials on an NFuse NDS logon screen. See Chapter 3 of the NFuse 1.6 Administrator’s Guide for information about how to configure NFuse for NDS. To use NDS logon information with earlier versions of ICA Win32 Clients, enter the NDS tree name in the Domain field and a distinguished name in the User field on the ICA Win32 Client logon screen. 8. DNS Name Resolution * You can configure ICA Win32 Clients that use the XML Service to connect to the MetaFrame farm to request a Domain Name System (DNS) name instead of a server’s IP address. 9. Extended Parameter Passing With extended parameter passing you can associate a file type on a client device with an application published on a Citrix server. When a user double-clicks a locally-saved file, the file is opened in the application associated with it on the MetaFrame XP server. Installation Instructions for the ICA Win32 Client --------------------------------------------------- See the ICA Win32 Clients Administrator's Guide for step-by-step instructions for installing the ICA Win32 Client. Limitations and Known Issues ---------------------------- 1. When running an ICA session on a computer with multiple monitors running at different color depths, moving the ICA session window between monitors will corrupt the display. If you want to move ICA sessions between monitors, you must set all monitors to the same color depth. 2. If you install a Web browser after installing the ICA Win32 Web Client, you must reinstall the ICA Win32 Web Client if you are using the Netscape Plug-In. The Netscape Plug-In needs to be registered with the browser so that when you select an ICA file in an HTML file, the browser knows what to run to invoke the ICA file. 3. If you set an encryption level higher than Basic, you must add the following line to the Appsrv.ini file to use the single sign-on feature: AutoLogonAllowed=on 4. If the color depth of your local desktop is set to High or True Color, running a 256-color ICA Client session causes a bold border around modified cells in Microsoft Excel 97 and Excel 2000. To fix this issue, adjust the color depth of your local desktop to match that of the ICA Client. 5. ICA Win32 Client regression: You cannot connect to a Citrix server using the IPX, SPX, or NetBIOS protocols after installing Version 6.20 of the ICA Win32 Client (the version shipped with MetaFrame XP, Feature Release 1) in the following circumstances: * If you install Version 6.20 of the ICA Win32 Client on a client device and then install an earlier version of the ICA Win32 Client. Attempting to connect using the earlier version of the ICA Win32 Client will fail. * If you install and then uninstall Version 6.20 of the ICA Win32 Client and then install an earlier version of the ICA Win32 Client. 6. To use Version 6.20 of the ICA Win32 Client with MetaFrame for Windows Version 1.8 on Windows 2000 servers, the server must be running Service Pack 2 for MetaFrame 1.8. If you use Version 6.20 of the ICA Win32 Client to connect to a MetaFrame 1.8 server that is at Service Pack level 1, the connection will be dropped the next time you attempt to connect. 7. Scaling limitations A Win32 Client session window can be reduced to a minimum of 64 pixels in width. However, the Windows operating system may enforce a different limit (greater than 64 pixels) based on the prevailing desktop scheme, which overrides the ICA Win32 Client scaling limit. 8. If you are using SSL encryption with the Program Neighborhood Agent, you must edit the Config.xml file on the NFuse 1.6 server to replace the machine name with the fully qualified domain name of the server hosting the SSL certificate. For more information about working with the Program Neighborhood Agent configuration file on the NFuse 1.6 server, see Chapter 6 of the NFuse 1.6 Administrator's Guide. 9. On ICA Win32 client devices running Windows 9x or Windows Me, Off Screen Surface (OSS) functionality is disabled by default. OSS functionality directs the ICA Client to draw screen updates to an in-memory bitmap instead of to the screen. Because this functionality improves bandwidth efficiency, you may want to enable it if users connect to Citrix servers across a WAN. To enable OSS functionality before you deploy the ICA Win32 Client software to users: A. Extract the ICA Win32 Client files from the ICA Win32 Client executable (see the list of executables at the top of this document). B. Open Module.ini in any text editor. C. Change the line EnableOssOnWin9xMe= in the [Thinwire3.0] section to EnableOssOnWin9xMe=on. D. Save and close Module.ini. E. Repackage the ICA Win32 Client files for distribution to your users. 10. On low-end client devices or systems running multiple simultaneous ICA connections, CPU utilization may run higher than expected when there is no activity between the client and the server. If this happens, change the poll time-out value on the client device. The default poll time-out value is 1 millisecond. To enter a higher poll time-out value: A. Open the Appsrv.ini file in a text editor. The default location for this file on the client device is in the "user profile directory" \Application Data\Icaclient. B. Enter the following line in the [wfclient] section of the Appsrv.ini file: IdlePollDelay=n where n is the desired polling interval (in milliseconds). C. Save and close the Appsrv.ini file. 11. If the ICA Win32 Client is uninstalled shortly after using Netscape to connect to a published application using NFuse, the Npican.dll file is not removed from the Netscape Plug-in folder. When this happens, the NFuse Login page does not display the ICA Client download links. To remedy the situation, either manually remove the Npican.dll file or reinstall the ICA Win32 Client using a method other than the NFuse Login page. 12. Do not install the ICA Win32 Program Neighborhood Agent and the ICA Win32 Program Neighborhood Client on the same client device. If you install and then uninstall the Program Neighborhood Agent on a client device that already has the Program Neighborhood Client installed, file type association for .ica-type files is lost and the client will not able to connect to Citrix servers. To restore file type association for .ica-type files, type the following command at a command prompt: wfica32.exe /setup 13. If you want to use Citrix Extranet with the Program Neighborhood Agent on a Windows 95, Windows 98, or Windows Me system, you must use Version 2.5 of both the Extranet client and the Extranet server. Earlier versions of Citrix Extranet installed on a client device running Windows 9x can cause the Program Neighborhood Agent to hang, even if you are not using Extranet when you are running the Program Neighborhood Agent. 14. When you double-click a file whose filename contains spaces, the extended parameter passing feature may open the associated published application, but not the file itself. When this happens, open the file by browsing to it from within the application's File > Open... dialog. Issues Resolved in the ICA Win32 Clients, Version 6.20.986 ---------------------------------------------------------- 1. If a session was disconnected with the Num Lock, Caps Lock, and/or Scroll Lock LEDs on and the session later reconnected, the LEDs and the functions sometimes turned off unexpectedly. 2. The right-click menu did not appear correctly when a seamless application was minimized on the taskbar. The menu popped up momentarily and immediately disappeared. 3. Caps Lock failed when the client connection option "Queue mouse movements and keystrokes" was enabled. 4. Auto update of the 6.20.985 client continuously asked users to reboot their Windows 95 workstation if pass-through options were selected before the update began. 5. Session sharing did not work in seamless sessions when in a workgroup. 6. If a user on a client device is running a minimized seamless application and moved an icon on the desktop, the server did not recognize that the icon had moved. Synchronization between the server and the client device was lost. 7. Client drive mapping on the pass-through client was restricted to the drives on the client device. The client could not map local or network drives configured on the MetaFrame server in a pass-through session. Local or network drives configured on the MetaFrame server can now be mapped by the pass-through client. Open the Module.ini file in a text editor and add the following line to the [ClientDrive] section of the file: NativeDriveMapping=TRUE When this flag is set, the client drives on the client device are not mapped and are not available. The drives configured on the MetaFrame server are mapped and are available to the pass-through client. 8. Synchronization of handheld devices failed sometimes on the Version 6.00.910 client. This caused 100% CPU utilization. To enable the timer-based COM port polling, under the "Client COM Mapping Virtual Driver" section in the Module.ini, change "CommPollSize = On" to "CommPollSize = Timer." 9. Selecting Alt+PrintScreen while running an application in a seamless session caused the File menu to be highlighted. 10. The Verisign-issued Global Server Certificate could not be used when running ICA over SSL on a Windows XP computer. 11. When using SSL, Windows XP produced error 15: "The SSL security context is invalid or has expired." 12. On Windows 95 computers, ICA files configured with HTTP browsing failed when using IP addresses instead of NetBIOS or DNS names. 13. The user password appeared in clear text when using Process Explorer from Sysinternals. 14. Could not launch a second instance of a seamless application when the TWI flag was set other than On. 15. The autocreated printer option failed when using a pass- through client because the pass-through client routed all users to the same network printer. To enable the pass- through client to use the original client name, add the following registry setting to the computer on which the pass-through client is running. WARNING! Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Use Registry Editor at your own risk. A. Run regedt32. B. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\ PASS THROUGH. C. From the Edit pull-down menu, select Add Value and type PASS THROUGH. Select REG_DWORD in the Data Type field. D. In the DWORD Editor window, type 1 in the Data field to use the original client name for the autocreated printer. 16. When a single sign-on user had the Novell client installed and authenticated, only the Novell credentials were sent to the server. Users could not choose to use Windows credentials. To override this behavior, make the following change to the Appsrv.ini or *ICA files. Appsrv.ini - Under the [WFCLIENT] section, add or modify the SSOnCredentialType entry to "SSOnCredentialType=NT." *ICA - Under the application name section, add or modify the SSOnCredentialType entry to "SSOnCredentialType=NT." 17. When users attempted to connect, they sometimes received the following error messages: "Error adding to custom ICA connection." "Error creating application set." These messages were received under the following conditions: A. The user was a member of an Organization Unit (OU). B. The OU defined "user's profile path" on a network share point using a Universal Naming Convention (UNC) style name. C. The Everyone group was restricted from accessing that network share point. The application data folder can now be created (if necessary) and it can be accessed the first time a user attempts to connect. 18. ICA error log messages did not contain month, day, year, or hour in the time-stamp fields. 19. When logging off, could not close an application running in seamless mode using a pass-through client. 20. Pressing Alt+Tab to change focus did not work in certain scenarios for applications running in seamless mode. 21. ICA session scroll bars hid the application scroll bars. 22. When switching focus among seamless and non-seamless windows, the up or down state of the Alt, Shift, and Ctrl keys sometimes did not synchronize between the server and the client device. To the client device, the keys appeared to be locked in the up position while to the server, the keys appeared to be in the down position. 23. The universal printer driver did not change paper size as required. The paper always remained as 8-1/2 x 11 letter size. 24. The client produced a Dr. Watson error when SpeedScreen Latency Reduction was enabled. 25. The appearance of the startup logo was corrupted on the Windows 95/98 client. 26. .Ica files were subject to incursion by a malicious user. This potentially represented a security risk. 27. A newly launched application sometimes lost focus. 28. Mouse button configuration did not work correctly within an ICA session when using left-handed mouse settings on the MetaFrame server and the client device. 29. The Ctrl and Alt keys sometimes became locked in the down position for a seamless application if the following occurred: A. Multiple seamless applications were sharing a session. B. All of the seamless applications were minimized. C. The Alt+Ctrl+Del hotkey sequence was pressed. D. When returning to the desktop, one of the minimized application's windows was brought into focus. E. When the window was brought into focus, the Alt and Ctrl keys became locked in the down position and no characters could be typed. 30. (This fix pertains only to the English and German versions of the Win32 Client.) A "Transport Driver Error" message incorrectly appeared when no licenses were available. This message has been changed to read: "Unable to connect to published application. No licenses are available." 31. In Windows 95 OSR2, there was a brush handle leak every time a new window was created. 32. A client error appeared when running an ICA session embedded in a Web page. This occurred with Internet Explorer Version 5.0. 33. Minimized windows of Delphi-based applications disappeared when the parent was minimized and then restored. 34. When an application called for the Empty Clipboard function on the server, the function did not synchronize with the clipboard channel on the ICA client device.