Issues Fixed in Citrix XenApp 6.5 for Windows Server 2008 R2

Citrix XenApp 6.5 for Windows Server 2008 R2

Issues Fixed in this Release

Product: Citrix XenApp
Current Product Version: 6.5
Previous Product Version: 6
Language: English (EN)
Fixed Issues List: 1.00

Revision History

Version	Date	Change Description
1.00	August, 2011	Initial release

Issues Fixed in this Release

The following issues have been fixed since the previous release of this product. For information about new features and system requirements, seeCitrix eDocs, the Citrix Product Documentation Library.

Data Store

1. Restarting the IMA Service while the data store is unavailable results in the temporary deletion of certain farm policy settings from the server. This occurs because reading the settings from the local host cache - intended as a backup mechanism for retrieving farm policy settings in case the data store is down - does not work properly. Even without this fix, the issue is temporary: restarting the IMA Service as soon as the data store is available again repopulates the farm policy settings. This fix addresses the issue that prevents the proper reading of the farm policy settings from the local host cache in the first place.
   [#234694]

EdgeSight

1. EdgeSight does not properly collect data for published desktop launches and does not properly display such data in its reports.
   [#240414]

HDX Plug-n-Play for USB Storage Devices

1. This fix is required to make the HDX Plug-n-Play for USB Storage Devices feature available to XenApp 6 Fundamentals Edition.
   [#247088]

IMA Service

1. The IMA Service fails to start when using multiple NIC teams and the ICA listener is assigned to only one NIC team.
   [#235068]
2. A memory leak in SessionSS.dll can cause the memory utilization of the IMA Service to increase unexpectedly.
   [#236150]
3. Launching Microsoft PowerPoint 2010 in a client session can cause the IMA Service to exit unexpectedly.
   [#240193]

Installing, Uninstalling, Upgrading

1. Installing hotfixes or performing a repair on the base product for Citrix XenApp 6 for Windows Server 2008 R2 can inadvertently remove the Citrix Licensing component, if present, from the system. This fix prevents the Citrix Licensing component from being removed when installing subsequent hotfixes.
   [#245185]
2. After installing XenApp 6, right-clicking My Computer and selecting Manage fails to bring up the Computer Management console.
   [#245755]
3. Servers can experience high CPU utilization after installing Hotfix XA600W2K8R2X64010.
   [#253033]

Licensing

1. The Remote Desktop Licensing Manager displays the client name as "Unknown" for the Terminal Services Client Access Licenses (TSCALs) issued.
   [#251083]

Load Balancing

1. Load balancing, when configured based on servers and applications, might not work correctly at times. This results in new connections going to the same server rather than to the least loaded server.
   [#232105]

Logon/Authentication

1. Connections from WinCE clients can get randomly dropped before the server logon screen appears.
   [#230540]
2. Attempts to log on to a server with a user name that exceeds 19 characters in length fail and can cause the Winlogon.exe process on the server to exit unexpectedly. This fix adds support for user names up to 255 characters long.
   [#233858]
3. When the Windows logon takes a long time due to, for example, Active Directory authentication, a full-screen published desktop does not display a status indicator to provide status feedback. This can be confusing to users. This fix modifies the behavior of the status indicator so that the indicator remains visible until the authentication completes.
   Note: To correct this issue in its entirety, you must install both a server hotfix and a plug-in hotfix that contains Fix #235374.
   [#235374]
4. Attempts to log on to a XenApp 6 server using Version 7 or earlier of the clients can cause svchost.exe to exit unexpectedly. As a result, further connection attempts to the server fail until it is restarted.
   [#237503]

Printing

1. With SmoothRoaming enabled, users must relaunch sessions to reenumerate and update session printers after roaming to a different location. This feature enhancement introduces dynamic printer discovery to automatically reenumerate and update session printers after roaming to a different location so that relaunching of sessions is no longer necessary. To enable this enhancement, you must also deploy a client hotfix that includes Fix #226929.
   [#226929]
2. Parts of the names and descriptions of client mapped printers might appear in an unexpected language; for example, "Microsoft XPS Document Writer (von <computer_name>) in Sitzung: 2." The issue occurs if, while installing Windows Server 2008 R2 (English), underLanguage to install, you select a language other than English (for example, German), then install XenApp 6, and then change the server's current system locale (Regional and Language Options > Administrative > Change system locale... > Regional and Language Settings) to a different locale; for example, English. The localized parts of the names and descriptions of session printers do not, as expected, appear in English but in the language selected under Language to install when installing Windows Server 2008 R2.
   [#248436]

SDK

1. Calling System.IO.Directory.Exists() against \\Client\ returns true, even if there is no media in that drive.
   [#251117]
2. When using the WFSQuerySessionInformationA() API to retrieve session information, the letters in published application names can appear separated by blank spaces.
   [#258019]

Seamless Windows

1. Child windows of some applications position to where their lower boundaries dip below the Windows Taskbar. This is the server-side component of the fix. To resolve the issue in its entirety, you must also install a client-side hotfix that contains Fix #206851.
   [#206851]
2. Dock bars of published applications might overlap and obscure the local Windows Taskbar. This is the server-side component of the fix. To resolve the issue in its entirety, you must also install a client-side hotfix that contains Fix #206851.
   [#210857]

Secure Gateway 3.3

1. Secure Gateway diagnostics might report the following error when requesting information from STA over SSL Relay: "An unclassified SSL/TLS error occurred. (error code: 0x80100308 - The token supplied to the function is invalid)."
   [#174283]
2. The Web Interface is unable to connect to SSL Relay due to SSL Relay selecting incorrect certificates.
   [#190473]
3. The WMI class Win32_PerfRawData_CtxSecGwyPerf_CitrixSecureGateway is not available when Secure Gateway is installed on Windows Server 2003. This happens because Windows Server 2003 registers WMI classes in a way different from Windows 2000 Server and Windows Server 2008.
   [#193394]
4. Under certain circumstances, the Citrix XTE Service does not properly disconnect a Terminal Services session. Specifically, the issue occurs when the network connection between the XTE Service and the client is interrupted and servers stop sending ICA KeepAlives to check the network connection status.
   [#205371]
5. Single sign-on from the Web Interface over SSL can fail for users who are members of a large number of Active Directory domain local groups.
   [#206220]
6. Under heavy load conditions, the non-paged memory pool can increase steadily. As a result, servers can become unresponsive at random.
   [#207150]
7. With Session Reliability enabled, Event IDs 184 and 185 (ICA connection open and close) fail to be logged in the Event Viewer of the Secure Gateway server.
   [#211426]
8. The Citrix XTE Service can exit unexpectedly at random, disconnecting all users.
   [#211650]
9. After upgrading to Version 3.1.1. of the Secure Gateway, the Secure Gateway process can consume extensive memory, eventually using up all available memory.
   [#212358]
10. Secure Gateway fails to delete expired logs configured for automatic cleanup using Rotatelogs (as described in Knowledge Center articleCTX107583).
    [#213336]
11. With several instances of the Secure Gateway Management Console open at the same time, only the first instance of the console that was opened displays data; all instances of the console that are opened later do not display any data. While this behavior is as designed and the console displays an error message indicating the issue, the error message is easily overlooked. This fix introduces an obvious error message pop-up explaining the behavior.
    [#220575]
12. Upgrading to Hotfix SGE3.1.1 or SGJ3.1.3 causes existing application logs to be cleared.
    [#239910]
13. Secure Gateway fails to start when a certain number of Access Control Lists is exceeded.
    [#244212]
14. ICA connections through the Secure Gateway fail from a custom Web Interface site when using the Firefox Web browser.
    [#246862]
15. This fix addresses a security vulnerability related to Citrix Secure Gateway. For more information, see Knowledge Center article CTX128168.
    [#252520]

Security Issues

1. The Citrix SSL Relay Configuration tool can fail to correctly create the outbound connection policies defined in its Connection tab. After applying this fix on affected deployments, the policies are modified to disallow all outgoing connections. As a result, SSL connections can stop working. In order to recreate the correct policies and allow SSL connections to work again, you must rerun the Citrix SSL Relay Configuration tool, verify the policies in its Connection tab and click Apply. The next time the server restarts, the correct policies are in place.
   [#228352]
2. This fix addresses a security vulnerability. For more information, see Knowledge Center article CTX123359.
   [#236530]

Server/Farm Administration

1. Configuration logging fails for administrators whose SQL Server password starts with a capital letter S.
   [#207951]
2. The DSMAINT / RECOVER does not restore a database backed up using the DSMAINT / BACKUP command.
   [#242816]
3. If you install XenApp 6 for Windows Server 2008 R2 without configuring it, the IMA Service fails to update CtxSta.config upon reboot if the XML port is set for "Sharing" with IIS.
   [#244230]
4. The DSCHECK utility can exit unexpectedly when running the DSCHECK /full servers /clean command.
   [#244806]
5. In the Delivery Services Console, under XenApp > Contents or Farm Name > Information session counts include ICA listeners, RDP listeners, and console sessions of all servers. This behavior is different from earlier versions of the product. This fix restores the behavior familiar from earlier versions of the product.
   [#245761]

Session/Connection

1. Certain applications fail to launch when Admin Approval Mode is enabled in User Account Control.
   [#214441]
2. The CPU consumption of Microsoft Office 2007 applications published using Microsoft App-V on servers running XenApp can increase to 100%.
   [#225459]
3. The previous implementation of Excelhook, which is used to create separate taskbar icons for each Microsoft Excel workbook, does not work for Excel 2010. This fix enables Excelhook for Excel 2010 if the following registry key is set:
   • On 32-bit Windows:
     HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ExcelHook
     Name: Enabled
     Type: REG_DWORD
     Data: 1
   • On 64-bit Windows:
     HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ExcelHook
     Name: Enabled
     Type: REG_DWORD
     Data: 1
   [#229062]
4. wfica32.exe might get initialized within a desktop session during disconnect or logoff of a pass-through session. This can cause the session to reconnect to itself and in the process lock out the user. This fix requires you to install both a server and a client-side hotfix that contains Fix #231831. If, after applying both hotfixes, you continue to observe the issue, create the following server-side registry key to resolve the issue:
   HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client
   Name: CheckWfShellForPassThru
   Type: REG_DWORD
   Data: 1
   [#231831]
5. A WSXICA 9 error can occur, causing users to no longer be able to connect to any applications. The following error message appears:
   "The description for Event ID 9 from source wsxica cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."
   [#240438]
6. With Session Reliability enabled, ICA connection attempts fail if the ICA Listener is bound to a single NIC in a multihomed environment.
   [#246316]
7. Attempts to connect to a server can fail. The issue occurs when attempting to connect to a server with multiple network adapters if an adapter that does not route clients is set to the lowest priority.
   [#250909]
8. Selecting Options in any Microsoft Office 2010 published application causes the Options dialog box to remain the topmost window, covering parts of other local or session windows and applications.
   [#254951]

Shadowing

1. Terminating a shadowed session from the Delivery Services Console using a key combination can cause users to loose keyboard and mouse control of their session.
   [#248234]
2. The Shadow Taskbar can become unresponsive when expanding tree items.
   [#249887]

Smart Cards

1. Attempts to connect to a XenApp 6 server from a Wyse terminal configured for smart card single sign-on fail.
   [#242752]

System Exceptions

1. When using the Client for Solaris, copying files from mapped client drives into a session running on XenApp 6 for Windows Server 2008 R2 can cause the server to experience a fatal exception, displaying a blue screen.
   [#230823]
2. Servers running XenApp 6 can become unresponsive while shutting down. The issue occurs when the picadm.sys driver encounters certain error conditions that prevent it from shutting down gracefully.
   [#235234]
3. Winlogon.exe can exit unexpectedly when launching a published application. The issue occurs when the commandline, including parameters, exceeds 200 characters. This fix addresses the issue for commandline parameters that do not exceed 255 characters in length. For instructions on passing longer parameters, see eDocs topic LongCommandLine2.
   [#236631]
4. Servers can experience a svchost.exe exception on termserv.exe and as a result become unresponsive.
   [#238866]
5. An unhandled exception in picaprovider.dll can make processes, among them winlogon.exe, exit unexpectedly.
   [#241468]
6. Restarting Branch Repeater while there are active server sessions can cause the XenApp server to experience a fatal exception, displaying a blue screen.
   [#244759]
7. Server might experience a fatal exception, displaying a blue screen, with bugcheck code 0x3b on vdtw30.dll.
   [#245748]
8. An issue related to CtxAudioSvc.dll can cause servers to experience a fatal exception, displaying a blue screen, with bugcheck code 80 (NMI_HARDWARE_FAILURE).
   [#249548]
9. Servers might experience a fatal exception, displaying a blue screen on picadm.sys with bugcheck code 0x22 (FILE_SYSTEM).
   [#250230]
10. Servers might experience a fatal exception, displaying a blue screen, on picadm.sys. The issue occurs when the user removes a thumb drive from a client device while connected to a session.
    [#251035]
11. Servers might experience a fatal exception, displaying a blue screen on picadm.sys.
    [#253078]
12. Servers can experience a fatal exception, displaying a blue screen, on picadm.sys. Dumps indicate that picadm.sys is referencing invalid, possibly disconnected volumes.
    [#254084]
13. With folder redirection enabled, servers can experience a fatal exception, displaying a blue screen, on picadm.sys. The issue can be observed when attempting to save a file that was introduced into the session on a USB device attached to and then removed from a thin client device.
    [#258343]
14. Servers might experience a fatal exception, displaying a blue screen, while shadowing is started.
    [#258948]

Miscellaneous

1. Attempts to launch Windows Internet Explorer from an http, https, or mms hyperlink embedded in a streamed application fail. The issue occurs because XenApp 6 does not create the HKEY_CLASSES_ROOT\htmlfile\shell\opennew\command_backup registry key as part of server file type association.
   [#250332]
2. The ICA Listener can utilize up to 100 percent of the CPU, causing servers to refuse connections.
   [#254787]
3. The performance monitor I/O Other Bytes counter reports values of 200-500MB for the csrss.exe process when a user moves the mouse and clicks inside a published desktop.
   [#255854]