Those 1004 events were killing me. Been complaining for over 6 months about it to Citrix!!! The worst part was that this was stopping users logging on but it only seemed to effect NT4 machines like that. Thanks for the read me. Have been trying to find this before deciding which client to use in next desktop build. Malcolm -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Thin Fan Sent: 05 November 2004 19:08 To: thin@xxxxxxxxxxxxx Subject: [THIN] Citrix Address some ICA Client issues with v8.1 Finally I won't be plagued with so many 1004 Licensing Errors in the Event Logs per this readme for v8.1 client: Readme for MetaFrame Presentation Server Client for 32-bit Windows, Version 8.100 Filenames Ica32pkg.msi, Ica32.exe, Ica32a.exe, Ica32t.exe, Wfica.cab, Wficat.cab For MetaFrame Presentation Server Clients for 32-bit Windows Replaces All versions prior to May, 2004 Date September, 2004 Language English (US) Description The MetaFrame Presentation Server Client for 32-bit Windows supports the following platforms: Windows XP Windows 2003 Windows 2000 Windows 98 Windows 95 Windows Me Windows NT 4.0 Windows NT 3.51 Where to Find Documentation This document contains information about the MetaFrame Presentation Server Clients for 32-bit Windows. For more information about the clients, see the Client for 32-bit Windows Administrator's Guide, Version 8.x. Documentation, including the Administrator's Guide, is in the Document Center located in the \Documentation\docs directory on the Components CD. The Document Center provides a single point of access to the documentation and enables you to go directly to the section in the documentation that you need. You can access the Document Center from the product CD or install it on your servers. If you prefer to access the guide without using the Document Center, navigate to the component PDF files using Windows Explorer. The guide is in an Adobe Portable Document (PDF) format file. To view, search, and print the documentation, you need Adobe Reader 5.0.5 or later with Search. You can download Adobe Reader for free from the Adobe Web site at http://www.adobe.com/. All product documentation is also available in PDF format from the Citrix Web site at http://www.citrix.com/support. Notes about this Release Certain fixes in this release require you to install a corresponding server hotfix to gain full functionality. The required server hotfixes are indicated with each applicable line item in this readme. If the readme indicates that a server hotfix is required, but none is listed for your platform and language version, contact customer support for assistance. With clean installations of this release (that is, on computers where you did not previously install Version 8.0 of the client), the default behavior of SSPI, controlled by the SSPIEnabled entry in the wfclient.ini file, is different from the way it was in Version 8.0 of the client: For Version 8.100 of the client, the default value for SSPIEnabled is ON. If you are upgrading from Version 8.0 of the client, the default value for SSPIEnabled is OFF. [#83635] The Gateway Client fails to open MetaFrame Secure Access Manager access centers when Windows XP, Service Pack 2, is installed. This issue is unrelated to MetaFrame Presentation Server Clients. Applying this upgrade does not correct the issue. For more information and to download a Microsoft Update for Windows XP Service Pack 2 that corrects the issue, see Microsoft Knowledge Base article KB884020. Issues Resolved in this Release The following issues with the previous release of this product were addressed and fixed in this current release: ---------------------------------------------------------------------------- ---- CAUTION! Several items in this fix 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. ---------------------------------------------------------------------------- ---- Large file transfers: Transfers of large files over wide-are networks (WANs) tended to be slow relative to the available bandwidth. This was caused, in part, by the earlier design of the drive mapping feature. This fix, along with the requisite server Hotfixes and registry entries, results in significant performance gains for large file transfers over WANs. Note: You must apply both this release and the following server Hotfixes, depending of the server platform: · For Windows 2000 and MetaFrame XP 1.0 with Feature Release 3 - Hotfix XE103W2K081 · For Windows 2000 Server and MetaFrame Presentation Server 3.0 - Hotfix MPSE300W2KR01 · For Windows Server 2003 and MetaFrame Presentation Server 3.0 - Hotfix MPSE300W2K3R01 Enable the following registry entries: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\icawd (REG_DWORD)CongestionMonitoring (REG_DWORD)AsyncDiskWritesToClient (REG_DWORD)DiskReadAheadFromClient All three registry entries are independent and enabled by the value 1. If undefined or set to 0, the corresponding feature is disabled. CongestionMonitoring improves throughput without impeding on interactivity. Recommendation: Always enable. AsyncDiskWritesToClient improves the speed of disk writes and file transfers from server to client. However, when a session is disconnected or the client device runs out of disk space during an asynchronous transfer, you must reinitiate the file transfer after reconnecting to the server. Recommendation: Only enable if client-side files written by server applications are easy to recover in case of disconnected sessions. DiskReadAheadFromClient improves the speed of disk reads and file transfers from client to server, and, unlike AsyncDiskWritesToClient, without any compromising functionality or data integrity. Recommendation: Always enable. [82457] Automatic client reconnection: Note: To get the automatic client reconnection feature for servers running MetaFrame Server 1.2 for UNIX, you must install server Hotfix ME113SB200, ME113HB200, or ME113AB200, depending on your server platform. Manually reconnecting to a disconnected session on a server running MetaFrame for UNIX 1.1 with Feature Release 1 or MetaFrame for UNIX 1.2 prevented the auto client reconnection feature from being invoked if the session was disconnected again. [82345] Automatic client reconnection: As designed, clients would make an indefinite number of attempts to reconnect to disconnected sessions until the connection was reestablished or until you clicked Cancel in the corresponding dialog box. Support has been added for disabling automatic client reconnection and for limiting the number of automatic reconnection attempts. To do this, you must edit each user's Appsrv.ini file. By default, this file is installed in the %USERPROFILE%\Application Data\ICA Client folder. To disable automatic client reconnection: Open the Appsrv.ini file in a text editor. Add or modify the following parameter in the [WFClient] section to read as follows: TransportReconnectEnabled=0 To limit the number of automatic reconnection attempts: Open the Appsrv.ini file in a text editor. Add or modify the following parameter in the [WFClient] section to read as follows: TransportReconnectRetries =<value> where <value> indicates the number of reconnection attempts. In the same section, locate the TransportReconnectEnabled parameter. If it is present, set its value to 1. If it is not present, no additional action is required for Step 3. Also, if an unrecoverable error occurred during a reconnection attempt, the client ignored the error and continued its reconnection attempt(s). With this fix, a dialog box has been added to inform you of the error. [85983] Num Lock state: Clients were sometimes slow or unable to update the server Num Lock state (On/Off).. [76606, 85057] Num Lock state: Users of terminal emulation software, such as WRQ Reflections, were unable to use special function keys, such as PF1, that are mapped to the Num Lock key. As a result, pressing the PF1 key also unexpectedly changed the Num Lock state. [77424] Server-to-client content redirection: If a redirected URL specified a non-standard HTTP port, that is a port other than 80, the client was unable to access the URL. This was caused by the fact that the URL was stripped of the port number when the client Web browser was launched. [80871] Program Neighborhood: Occasionally, the client failed to launch applications in an application set and caused an ID 1004 terminal services event in the event log. This was caused by an error in the client/server capabilities negotiation process. Occasionally, the process represented that the client supported smart card authentication and was then bound by the server to use smart card authentication even when you were not using a smart card for authentication. [85645] Program Neighborhood: You were prompted for credentials for each connection you made to a server. This was caused by a particular flag being cleared for each connection. With this fix, the flag is no longer cleared so that logon information is reused for subsequent connections. [88712] Program Neighborhood Agent: Moving the cursor over Program Neighborhood Agent shortcuts placed on the Quick Launch bar when Program Neighborhood Agent was not running caused the shortcuts to display the Windows default icon. [82108] Program Neighborhood Agent: The application list did not refresh properly under the following circumstances: · When a user closed the client's Properties dialog box · When a user logged off and back on to the client · When the client's configuration and application refresh intervals were the same [86422] Program Neighborhood Agent: Servers failed to recognize user names that contained the ampersand (&) symbol, for example, j.smith@xy&z.com, and rejected users' logon attempts. [85421] Program Neighborhood Agent: Single sign-on failed when connecting to servers running different versions of MetaFrame Presentation Server. This was caused by the fact that the client was attempting to locate the server DLL, ctxrpc.dll, which starting with Presentation Server 3.0 is located in a different directory than in previous versions of the product. [87760] Program Neighborhood Agent: If enabled from the Program Neighborhood Agent Console (or in the config.xml file), single sign-on was available as a logon option from the Program Neighborhood Agent properties dialog box even if you opted not to enable single sign-on at install time. [89478] Program Neighborhood Agent: When using Program Neighborhood Agent as the pass-through client, users running Windows 98 occasionally experienced the following issues: · Published application shortcuts occasionally failed to launch the associated application on clients running Windows 98 · When clicking Program Neighborhood Agent's system tray menu, the application list failed to appear [88610] Web Client: Occasionally, you were unable to launch applications from the ICA Web Client. This was caused by an incorrect parsing of client proxy settings for Internet Explorer. [86426] Web Client: Updates to the Web Client from the Auto Client Update Database failed if you were using a manually extracted addition of the ica32t.exe Web Client package. This was caused by the fact that the installer package failed to create a dedicated resource directory. Therefore, the update database was unable to locate the resource files in the expected location and the update failed. [86946] Web Client: After installing the Web Client using the ica32t.exe file, the client's name would appear as Citrix Web Client in the Add/Remove Programs control panel. With this fix, the client name is displayed as MetaFrame Presentation Server Web Client for Win32. [89098] Program Neighborhood and Secure Gateway: Program Neighborhood Clients installed on Windows 98 and Windows NT devices were unable to locate servers through the Secure Gateway over HTTP/HTTPS. [83732] Zen Agent for Desktops V. 4.0: Single sign-on failed in certain client configurations that included combinations of Program Neighborhood Agent, Zen Agent for Desktops 4.0, and the Windows 98/SE operating system. [82392] Dragon NaturallySpeaking dictation software: French users of Dragon NaturallySpeaking dictation software were unable to display diacritic characters (é, è, à, ...) in published instances of Microsoft Word. [80227] Unresponsive client sessions: When using the scrollbar, certain published applications led the client to become unresponsive in connections to servers where SpeedScreen Browser Acceleration was enabled. [79559] Unresponsive client sessions: When you minimized and then maximized or restored a session set to 100% screen size the window failed to redraw, giving the appearance that the session was becoming unresponsive. [80141] Unresponsive client sessions: Playing video files in client sessions occasionally resulted in an unresponsive session or caused a fatal client error. This was caused by the way the client multimedia driver was implemented. [90600] Unresponsive client sessions: On clients running Windows 95 and Windows 98, dragging or resizing a local application window while in an ICA session occasionally rendered the display unresponsive. [89001] Print Screen key: Pressing the Print Screen key in a non-seamless ICA session would unpredictably capture either the client desktop or the ICA session. [81712] Print Screen key: Pressing the Print Screen key in seamless connections caused unexpected results in some applications. This happened when the AlwaysSendPrintScreen entry in the appsrv.ini file was set to On. [91858] NEC PC-98 keyboards: The Esc key did not work properly. [84961] NEC PC-98 keyboards: An incorrect key message was sent to server applications when you pressed the [vf.2] key on NEC PC-98 keyboards if ICAPrntScrnKey=F12 was set in the [WFCLIENT] section of the Appsrv.ini file. [85579] Client memory: Memory allocated to the ICA ActiveX control was not properly released for use by the client operating system or other applications after the client exited. [86717] Connections through proxy servers: If you were using a Proxy Auto Configuration (PAC) file and the client was unable to download the PAC file, for example, due to the client's location, you were not able to connect to servers. Support for a proxy fallback has been added that allows clients to bypass the proxy to connect to servers. To enable the fallback: Open the Appsrv.ini file in a text editor. Locate the DoNotUseDefaultCSL entry. · If set to True, add the following parameter to the [applicationservername] and/or the [applicationsetname] sections: ProxyFallback=yes · If set to False, add the following parameter to the [WFClient] section: ProxyFallback=yes Save your changes and close the file. [86975] Connections through proxy servers: When using a .ins file to dynamically configure proxy settings, you were not able to connect to servers. [88356] Auto-created printers: If you created printers from the command line, using the following entries: rundll32 printui.dll,PrintUIEntry /ga /n\\printserver\printer (to create a client printer) rundll32 printui.dll,PrintUIEntry /y /n\\printserver\printer (to set a printer as the client default printer) the printer at the top of the printer list was set as the client default printer, regardless of which printer was the actual default printer. This was caused by the way queries compared printer names to default printer names. [85953] SpeedScreen Browser Acceleration: Clients did not properly apply the compression and maximum compression settings configured for servers running MetaFrame XP 1.0, Feature Release 3 and MetaFrame Presentation Server 3.0. [90906] Client display: When changing client display settings before reconnecting to a server, the tray icon of MetaFrame Password Manager occasionally displayed transparent or invisible. [87609] Smart cards: Occasionally, reconnecting to a server failed when using smart card authentication. This was caused by improper handling of smart card status routines. [80574] Special characters in published application names: Published application names that contained special characters, such as Ü and Ä, caused the following issues: · The application failed to launch and generated the error message, "Not able to find ICA connection settings. The connection cannot be launched" · A generic icon was displayed in place of the icon representing the published application · In Program Neighborhood, the name for the published application may have displayed incorrectly [90611] Installing the client: On devices running Windows 95, Windows 98, and Windows Me, the two client installer files, ica32.exe and ica32pkg.msi, showed different default values for the Use machine name as client name option. [90433] Uninstalling the client: You could not properly uninstall clients that were installed with multiple Client Packager, ica32pkg.msi, files. This was caused by the fact that certain registry keys were not removed when uninstalling. [86333] Error messages: During network outages, an error message was displayed in SSL connections, stating, "The Citrix server is unavailable." This was misleading in that the message may have directed administrators' attention to servers running MetaFrame Presentation Server rather than to the network outage. The new error message does not make reference to MetaFrame Presentation Server or Citrix. [90513] Mouse pointer: Occasionally, the mouse pointer was not updated properly when moving over a disabled seamless window. This was caused by the fact that the window procedure does not receive mouse messages for disabled windows, which caused servers to be unaware of mouse movements on disabled seamless session windows. [89708] Connections launched from ICA files: Seamless connections launched from an ICA file, such as those launched from the Web interface, did not honor settings specified in Program Neighborhood. This was caused by the fact that for seamless connections launched from ICA files, only the parameters specified in the ICA file were applied, but not those specified in the appsrv.ini file. [88985] Seamless connections: When running a published application in seamless mode, moving the mouse pointer over associated icons in the system tray inadvertently disconnected the session. This was caused by a buffer processing flaw. [85458] Miscellaneous: When launching an ICA file from the desktop, associated temporary ICA files were created in the same folder as the ICA file. With this release, temporary ICA files are created in Internet Explorer's cache folder. [87648] Miscellaneous: Windows Explorer showed an inaccurate date modified time stamp for Microsoft Excel spreadsheets on local devices running Windows 98. Note: You must apply both this release and the following server Hotfixes (#72187), depending of the server platform: · For Windows 2000 and MetaFrame XP 1.0 with Feature Release 3: XE103W2K129 · For Windows 2003 and MetaFrame XP 1.0 with Feature Release 3: XE103W2K3041 · For Windows 2000 and MetaFrame Presentation Server 3.0: MPSE300W2KR01 · For Windows 2003 and MetaFrame Presentation Server 3.0: MPSE300W2K3R01 [91460] Installation Instructions See the Client for 32-bit Windows Administrator's Guide, Version 8,x. for step-by-step instructions for installing the Clients for 32-bit Windows. Copyright © 2004 Citrix Systems, Inc. All rights reserved. Citrix, MetaFrame, and MetaFrame XP are registered trademarks of Citrix Systems, Inc. in the United States and other countries. All other trademarks and registered trademarks are the property of their respective owners. ******************************************************** This Weeks Sponsor Emergent Online ThinCity Conference Join us at ThinCity 2004: The 1st Annual Emergent OnLine Technology Conference http://www.ThinCity.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm *********************************************************************************** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbs.co.uk/CBFM http://www.rbsmarkets.com ******************************************************************************** ******************************************************** This Weeks Sponsor Emergent Online ThinCity Conference Join us at ThinCity 2004: The 1st Annual Emergent OnLine Technology Conference http://www.ThinCity.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm