Based Citrix Technical Support experience and customer feedback, the following Citrix and Microsoft hotfixes have been found to resolve the most common issues with XenApp 6 and Windows Server 2008 R2. These hotfixes focus on basic functionality and stability. For a complete list of Citrix hotfixes for XenApp 6, please click here.
Note: Please refer to individual readme files for each of the following hotfixes to review complete details of issues addressed. Details listed below only mention the most common issues known to be resolved with each hotfix. Also, check out CTX126711 for our support statement on and a list of known issues with Windows 2008 R2 - SP1.
Citrix
XA600W2K8R2X64002 · 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.
· 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. · 1.This fix addresses a security vulnerability. For more information, see Knowledge Center article CTX123359. NEW · 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 while shutting down. The issue occurs when when the picadm.sys driver encounters certain error conditions that prevent it from shutting down gracefully. 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 CDM file, the resulting deadlock condition can prevent servers from accepting new session requests.
· Certain applications fail to launch when Admin Approval Mode is enabled in User Account Control
· This fix addresses a security vulnerability. For more information, see Knowledge Center article 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 fail
· 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 during logon and the logon process fails to complete.
· Servers might experience a fatal exception, displaying a blue screen, with bugcheck code 0xf4 on IMAAdvanceSrv.exe.
· 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
· This hotfix contains an updated version of the XenApp Server Configuration Tool, which you use 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. NEW
· 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. NEW · A Windows Server 2008 R2-based Remote Desktop server denies some connection requests randomly under heavy logon or logoff conditions
· Delay when you shut down, restart, or log off on a Windows Server 2008 R2
· Stop error in Windows 7 and in Windows Server 2008 R2 if a heavy load situation exists or if connectivity issues exist: "STOP: 0x000000B8"
· A computer that is running Windows Server 2008 R2 stops responding randomly. Note: It has been reported that this hotfix must be applied prior to installing SP1.
· An application or service that uses Winsock API or Winsock Kernel API may randomly stop responding in Windows Server 2008 R2
· Installs 32-Bit help System 2008R2 may be required if hosting 32-bit applicaitons
· Remote desktop sessions do not completely exit, and you cannot establish new remote desktop sessions to a computer that is running Windows Server 2008 R2
· Startup takes a long time on a Windows 7 or Windows Server 2008 R2-based computer that has an Intel Nehalem-EX CPU installed
· A computer that is running Windows 7 or Windows Server 2008 R2 intermittently cannot use a shared network printer to print NEW
