Based on Citrix Technical Support experience and customer feedback, the following Citrix and Microsoft hotfixes are found to resolve the most common issues with XenApp 6 running on a Windows Server 2008 R2 server. These hotfixes focus on basic functionality and stability.
Recommended Citrix Hotfixes
- 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 from the system, if present. This fix prevents the Citrix Licensing component from being removed when installing subsequent hotfixes.
- This enhancement is a part of the XenApp Printing Optimization Pack. The Printing Optimization Pack improves the user experience and printing speed by reducing the printer bandwidth required. For more information, including system requirements, required components, and known issues, see XenApp Printing Optimization Pack in eDocs, the Citrix Product Documentation Library.
- This fix addresses security vulnerability. For more information, see CTX123359.
- This fix addresses session reliability issues that can occur when using multiple, disparate, client devices to reconnect to the same session.
- Servers running XenApp 6 can become unresponsive when shutting down. The issue occurs when the picadm.sys driver encounters certain error conditions that prevent it from shutting down in an orderly fashion. Also, servers might experience a fatal exception, displaying a blue screen on picadm.sys with bugcheck code 0x22 (FILE_SYSTEM).
- If a session is disconnected while it is still reading or writing a Client Drive Mapping (CDM) file, the resulting deadlock condition can prevent servers from accepting new session requests.
- This fix addresses a security vulnerability. For more information, see CTX128169
- 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.
- The CPU consumption of the CitrixCseEngine.exe process can spike unexpectedly and cause logon delays.
- Attempts to launch a published application that resides on a mapped network drive rather than on a XenApp server failure
- When connecting to a server running Windows Server 2008 R2 with Service Pack 1, Terminal Services can exit unexpectedly. This causes users to experience a black screen when logging on and the logon process fails to complete.
- Servers might experience a fatal exception, displaying a blue screen, with bugcheck code 0xf4 on IMAAdvanceSrv.exe.
- Servers attempt to launch Windows Internet Explorer from an http, https, or mms hyperlink embedded in a streamed application failure. 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.
- Certain applications fail to launch when Administrator Approval Mode is enabled in User Account Control.
- This fix addresses the following issues for sessions launched as streamed to server or by a script: 1) The application name can be missing from the session information of the Delivery Services Console Session and not appear under the Applications folder of the Delivery Services Console. 2) Application limits might be ingnored. 3) Attempts to reconnect to disconnected sessions can fail.
Other Citrix Hotfixes
- This hotfix contains an updated version of the XenApp Server Configuration Tool, which is used to configure XenApp 6 for Windows Server 2008 R2 server role installations. The XenApp image can be prepared for imaging and provisioning before, during, or after configuring XenApp.
- This enhancement is a part of the XenApp Printing Optimization Pack. The Printing Optimization Pack improves the user experience and printing speed by reducing the printer bandwidth required. For more information, including system requirements and required components, see XenApp Printing Optimization Pack in eDocs, the Citrix Product Documentation Library.
Recommended Microsoft Hotfixes
- A Windows Server 2008 R2-based Remote Desktop server denies some connection requests randomly under heavy logon or logoff conditions.