Readme for MetaFrame Presentation Server Client for 32-bit Windows, Version 9.100

Readme for MetaFrame Presentation Server Client for 32-bit Windows, Version 9.100 (64-bit compatible)

Description

The MetaFrame Presentation Server Client for 32-bit Windows (64-bit compatible) supports the following platforms:

Windows XP
Windows 2003
Windows 2000
Windows 98
Windows 95
Windows Me
Windows NT 4.0

64-bit Windows Support:

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 9.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.

• Adding Program Neighborhood Agent to the Client Update Database fails. Therefore, you cannot use the database to upgrade to Version 9.1 of Program Neighborhood Agent. [125379]

• Enhanced SpeedScreen Multimedia Acceleration:

o This feature enhancement requires DirectX 9.0c or later to be installed on all pertinent servers and clients. For the latest DirectX updates, see the Microsoft Web site at http://www.microsoft.com/. Search on keyword DirectX.

o The presence on client devices of VNC (Virtual Network Computing) software may interfere with this feature enhancement.

o Compatibility issues may exist with certain codecs or combinations of codecs installed on the server or on the client. If you experience issues, explore alternate codecs for the same type of media.

o Switching between clips frequently may cause the client to become unresponsive or exit ungracefully.

o Using the media player slider frequently or stopping and starting a video frequently may cause the video to freeze.

o When playing a playlist, the audio portion of the videos may degrade after the first video.

o Playing videos in Full Mode (Windows Media Player) or with a skin other than the default skin (RealOne Player) when the application is running in seamless mode causes the video to be rendered on top of everything else on the screen. As a workaround, play videos in Skin Mode (Windows Media Player) or with the default skin (RealOne Player).

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.

1. Client task bar:
Occasionally, seamless published applications covered the client task bar in whole or in part after the workstation was locked. The issue was caused by a code error.

[111313]

2. Clipboard mapping:
Occasionally, copying content from the client device and pasting it in a published application failed. The issue was caused by a third party application that prevented the client from receiving notification when new content had been copied to the local clipboard.

This fix introduces support for a mechanism to check at periodic intervals the client's ability to receive clipboard change notifications. If the mechanism finds the client to be unable to receive such notifications, the client will attempt to register itself to receive future notifications. To enable this functionality, you must modify users' appsrv.ini files as follows:

1. Open the appsrv.ini file located in the user profile directory using a text editor.

2. In the WFClient section, locate or add the entry:

CbChainInterval=<value>, where value is the interval, in milliseconds, at which checks are to be performed. Supported values range from 0 to 2,000, inclusive.

Note: The detection takes at least twice the amount of time specified in this setting.

3. Save your changes and close the file.

[112636]

3. Dragon NaturallySpeaking dictation software:
French users of Dragon NaturallySpeaking dictation software were unable to display diacritic characters (é, è, à, ...) in published instances of Microsoft Word.

[80227]

4. Focus related issues:
Launching published applications by clicking desktop shortcut icons may have caused the session window to lose focus when as it was being created.

[103215]

5. Focus related issues:
When closing modal dialog boxes pertaining to seamless applications, focus went to a local client window rather than to a window pertaining to the seamless application. The issue occurred with a small number of legacy applications that did not support the design that gave users the Minimize All functionality in client sessions.

[107258]

6. Focus-related issues:
On clients where a local instance of an Input Method Editor (IME) was running and minimized in the taskbar, transferring focus to a different window could take up to four seconds after closing a published application that was using the server IME. The issue was related to the implementation of the Microsoft Text Services Framework in IME2002 and later.

[118043]

7. Focus-related issues:
Version 9.0 of Program Neighborhood introduced a feature enhancement that prevented newly created seamless published application windows from taking focus from other windows that had focus at logon time. As a result, seamless applications did not take focus if users changed focus to a local window while the seamless connection was being initiated. In some situations, this new behavior is undesirable. This fix introduces support for a setting that allows you to revert to the client behavior common prior to the release of Version 9.0. To revert to the previous client behavior, you must modify users' appsrv.ini files as follows:

1. Open the appsrv.ini file located in the user profile directory using a text editor.

2. In the WFClient section, add the entry:

TWISeamlessFlag=1

3. Save your changes and close the file.

[118414]

8. Focus-related issues:
When an application spawned a new window and then automatically closed the original window, the new window did not take focus. Instead, other existing windows of the application took focus.

[106451]

9. IME 2003/Alternative User Input Text Input Processor (TIP) support:
When logging off from a session, a user's IME dictionary update was saved to an incorrect folder if Microsoft's Ctfmon.exe was installed on the client and if the client was configured to use pass-through authentication with local credentials.

[114406]

10. LED display serial devices:
Updates to LED display serial devices attached to COM ports did not happen reliably and consistently. This occurred, in part, because the write timeout was set to 10ms, regardless of the amount of data that was being sent.

This fix extends the default write timeout to two minutes, with an additional 100ms per byte of data being sent.

[100638]

11. Multi-monitor environments:
In multi-monitor configurations where the primary monitor is not the left-hand monitor, the local text echo balloon may have been located off the display surface. The issue occurred because the position of the balloon was calculated incorrectly.

[114798]

12. Multi-monitor environments:
Version 9.0 of the client exited unexpectedly when launching sessions in multi-monitor environments. The issue occurred only in conjunction with certain third party video drivers that caused the client to enumerate the list of monitors incorrectly.

[120985]

13. Multi-monitor environments:
The client stopped working in environments with more than four monitors. The issue occurred because the client did not allocate sufficient buffer space to accommodate large graphics data from multiple monitors.

[122977]

14. Multimedia playback:

When switching from normal to full screen mode in a seamless instance of Windows Media Player, the multimedia file stopped playing. The issue occurred because the switch to full screen did not reconnect the video window to the DirectX interface.

[122667]

15. Pass-through client:
Occasionally, a pass-through client running on 64-bit systems stopped running unexpectedly. The issue was caused by an older graphics library.

[118060]

16. Pass-through client:
In RDP sessions to servers running Presentation Server, users may not have been able to use the pass-through client if encryption levels were enforced. The issue occurred because the client did not correctly interpret encryption levels reported by RDP winstations.

[118499]

17. Pass-through client:
Presentation Servers did not prevent administrates from installing or upgrading the pass-through client using the self-extracting executable (.exe) version of the client, even though installing or upgrading using the .exe file is not supported. The issue was caused by an omission in the verification check mechanism.

[119342]

18. Print Screen key:
In client configurations where windows key combinations should be applied to the remote desktop, keeping the Print Screen key pressed was causing a continuous sequence of separate print screen event notifications to be sent to the application. The issue occurred because by default, the print screen event is sent when the Print Screen key is released (up), not when pressed (down).

This fix modifies the client behavior so that the print screen event notification is sent to the application when the Print Screen key is released (up).

[120447]

19. Printing:
Published instances of Adobe Reader 7.0 and Acrobat 7.0 did not print properly. The issue occurred because fonts unknown to the operating system that were temporarily added to the system from the spool file were disposed before the printing process had ended.

[114675]

20. Program Neighborhood Agent:
In Presentation Server 3.0 and later users of Program Neighborhood Agent had to manually reconnect to a disconnected session before launching an application if they wanted to session share the newly launched application with a disconnected session. The issue was caused by the implementation of the workspace control feature, introduced in Version 3.0, which required users to reconnect to a disconnected published application before launching a second published application so to be able to share two sessions.

This feature enhancement allows users of Program Neighborhood Agent to automatically reconnect to a disconnected session while launching a second published application.

To gain this feature enhancement, you must edit the config.xml file, located on the Web Interface server, as follows:

. Open the file config.xml using a text editor.

. Locate the section <ReconnectOptions>

. Add the following entry to the section:

<ReconnectWithLaunch>true</ReconnectWithLaunch>

. Save your changes.

. Restart the Web Interface server.

[106927]

21. Program Neighborhood Agent:
The client failed to launch published applications if the application name, server name, or client name contained multiple ampersand (&) symbols. The issue was caused by a buffer overrun resulting from the presence in those names of multiple ampersands.

[114713]

22. Program Neighborhood Agent:
When authenticating with incorrect credentials, the following dialog box appeared: "The credentials supplied were invalid. Please try again." The dialog box was out of focus. As a result, pressing the Enter key with the intention to respond to the dialog activated a different window - whichever window actually had focus at that time. The issue was caused by a code error.

[116656]

23. Program Neighborhood Agent:
When workspace control was enabled, the client did not automatically reconnect to active sessions if the user logged off from Windows and then logged back on. The issue occurred because the client did not make the necessary notifications to disconnect any sessions when Windows was shutting down on the client device.

[118418]

24. Program Neighborhood Agent:
Existing connections to published applications were disconnected when you attempted to launch another published application from a server that was unavailable. The issue was caused by a code error.

[119796]

25. Proxy configuration:
When setting proxy configuration through the Web browser - using an autoconfiguration URL file generated by the IEAK profile manager - a server connection could not be established if the server's address was in the proxy exception list and had to be accessed in direct mode.

Also, when the exception list of names exceeded 512 bytes and the server name was located outside that limit, the server name was not taken into account for the exception list logic.

The issue occurred because the IEAK profile manager generates the Proxy_Override keyword that contains the list of addresses/domains that should be accessed in direct mode (without going through the proxy). That keyword's format was not parsed properly if the "Do not use proxy for local addresses" check box was selected in IEAK. In this particular case, the IEAK profile manager introduced extra double quotes that were not expected. The parsing logic also had an upper boundary of 512 bytes beyond which it would truncate the Web browser's proxy exception list.

[113167]

26. Proxy configuration:
If a Web browser's settings specified an invalid URL to a proxy configuration file, or if the contents of the file could not be properly parsed, connections to published applications failed even though connections to the servers where the applications were published did succeed in direct mode. The issue occurred because the client's proxy detection process through the browser did not allow the connection to fall back in direct mode or manual mode if the proxy configuration file was unavailable.

[114299]

27. Secure Gateway:
When creating an SSL/TLS connection to a server located behind a network address translation (NAT) device, you could only connect to the server if the Fully Qualified Domain Name (FQDN) of the Secure Gateway was explicitly specified with the FQDN of the external server address. Setting the FQDN in the connection address list failed to establish the connection. The issue was caused by a code error.

[103209 ]

28. Server to client content redirection:
Server to client redirection failed when connecting through a proxy that requires authentication. The issue was caused by a code error.

[108285]

29. Server to client content redirection:
When server to client content redirection was enabled and a user clicked a hyperlink in a published Office application, the client side browser opened behind the published application. The issue was caused by a code error.

[110138]

30. Shadowing:
After shadowing a user in full screen mode, vertical and horizontal scrollbars may have appeared on the shadower's screen if the shadowee's screen resolution was lesser than the shadower's. The issue was caused by a code error.

[120880]

31. Smart card support:

Note: To get the full benefit of this fix, you must also install the latest smart card server fixes available in Hotfix Rollup Pack 3 and Service Pack 2005.4 for Presentation Server 3.0, or upgrade to Presentation Server 4.0.

On occasion, smart card readers did not show up properly or disappeared from the GemPlus 4.2 SmartDiag utility. The issue occurred due to an ICA Client timing situation that was causing the reader state not to be reflected by Presentation Server in a timely manner.

[108062]

32. Smart card support:
In seamless connections with smart card authentication, the smart card pin prompt appeared encapsulated in a non-seamless, 640 x 480 window. This is the client side component of a fix that resolves the issue. To get the full feature enhancement, you must also install the following server hotfixes:

o For server running Windows 2000 Server: MPSE300W2K004 or PSE400W2K001

o For servers running Windows Server 2003: MPSE300W2K3004 or PSE400W2K3001

[121027]

33. SpeedScreen Multimedia Acceleration:
Multimedia playback was rendered inconsistently or corrupted. The issue was caused by a buffer overrun.

[91393]

34. SpeedScreen Multimedia Acceleration:
This feature enhancement extends SpeedScreen Multimedia Acceleration to support the following media types. This is the client component of the feature enhancement. To get the full feature enhancement, you must also install the following server hotfixes:

o For server running Windows 2000 Server: MPSE300R03W2K003

o For servers running Windows Server 2003: MPSE300R03W2K3003

Note: There is a difference between media types and file formats (file extensions). File formats (for example, .avi, .mpg) can encapsulate multiple media types (for example, DIVX Video, MPEG-1 Video). A single .avi file, for example, could contain a DIVX Video stream, and an AC3 Digital Audio Stream, and would require both the DIVX and AC3 DirectShow codecs for proper playback.

* Note about MPEG-2 video decoders and the Windows XP Video Decoder Checkup Utility:

The following limitations are known:

[96644]

35. Web interface:
When connecting to the Web interface with a template.ica file containing the line ProxyUseFQDN=True in the [WFClient] section, the client exited unexpectedly. The issue was caused by a problem with the error diagnostics code.

[120884]

36. Miscellaneous fixed issues:
The .ica file type was not properly associated with wfica32.exe. The issue occurred because the installation version table was not updated properly.

[121119]

37. Miscellaneous fixed issues:
After upgrading from Version 8.1 of the client to version 9.0 using the .msi package, client devices experienced a blue screen and/or reported other errors. The issue occurred because the upgrade installation removed a required system registry key.

[122862]

38. Miscellaneous fixed issues:
On Windows NT 4.0 workstations connecting over the Secure Gateway, clicking OK in the following dialog box caused an access violation:

The network connection to your application was interrupted. Try to access your application later, or contact technical support.

The issue was caused by a code error.

[111009]

Installation Instructions

See the Client for 32-bit Windows Administrator’s Guide, Version 9.x for step-by-step instructions for installing the Clients for 32-bit Windows.

Copyright © 2005 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.