Hotfix package name: XA600R02W2K8R2X64062.MSP
For: Computers running Windows Server 2008 R2 with Citrix XenApp 6, Hotfix Rollup Pack XA600W2K8R2X64R02 installed
Replaces: XA600R02W2K8R2X64010, XA600R02W2K8R2X64027, XA600R02W2K8R2X64056, XA600R02W2K8R2X64057
Date: June, 2014
Languages supported: English (US), German (DE), Spanish (ES), French (FR), Japanese (JA), Simplified Chinese (SC)
Readme version: 1.00

Readme Revision History

Important Notes about This Release

• Note: As a best practice, Citrix recommends that you install this and other hotfixes only if you are affected by the specific issues they resolve. Otherwise, Citrix recommends that you wait for the next hotfix rollup pack for your product release. Hotfix rollup packs consolidate most previously released hotfixes and allow you to update systems in a convenient, single installation.
• Important: Installing this hotfix over an ICA session is not supported but you can install it through a remote desktop session using an administrator account.
• Caution! This release may 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.

Important Disclaimer - Limited Release Hotfix

If the Download link is not available on this page and you wish to obtain this limited distribution release, visit our support site at http://www.citrix.com/support and open a support case using your Citrix account credentials, or contact your reseller at http://www.citrix.com/partners/locator.

Testing of this release was targeted only at the affected functionality, and regression and stress testing were minimal. Introduce this release to a test environment for evaluation before deploying it to a production environment.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CITRIX AND ITS SUPPLIERS MAKE AND YOU RECEIVE NO WARRANTIES OR CONDITIONS, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, AND CITRIX AND ITS SUPPLIERS SPECIFICALLY DISCLAIM WITH RESPECT TO THE HOTFIX ANY CONDITIONS OF QUALITY, AVAILABILITY, RELIABILITY, SECURITY, LACK OF VIRUSES, BUGS OR ERRORS, OR SUPPORT AND ANY IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT PERMITTED BY APPLICABLE LAW, NEITHER CITRIX, NOR ITS SUPPLIERS SHALL BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL, MULTIPLE, PUNITIVE OR OTHER DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF DATA, LOSS OF INCOME, LOSS OF OPPORTUNITY, LOST PROFITS, COSTS OF RECOVERY OR ANY OTHER DAMAGES), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, AND WHETHER OR NOT FOR BREACH OF CONTRACT, NEGLIGENCE OR OTHERWISE, AND WHETHER OR NOT CITRIX, ITS SUPPLIERS, OR LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Where to Find Documentation

This document describes the issue(s) resolved by this release and includes installation instructions. For additional product information, see Citrix eDocs, the Citrix Product Documentation Library.

New Fixes in This Release

1. Servers might report a load of twenty thousand (20,000) after a scheduled reboot and refuse connection attempts.

   To enable the fix, you must create the following registry key:

   HKEY_LOCAL_MACHINE\Software\Wow6432Node\Citrix\Licensing
   Name: CheckRA_SS
   Type: REG_DWORD
   Value: 1

   [From XA600R02W2K8R2X64062][#LA5005]

Fixes from Replaced Hotfixes

1. Terminal Services can exit unexpectedly on RPM.dll.

   [From XA600R02W2K8R2X64010][#LA3411]

2. This fix addresses a regression introduced by Fix #LA0798.

   Description of Fix #LA0798: The Group Policy engine (CitrixCseEngine.exe) can cause the server CPU to spike unexpectedly while performing Group Policy checks upon session reconnection. This fix introduces support for the following registry key that, when set, allows you to suppress Group Policy checking when reconnecting to existing sessions:

   HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Logon
   Name: NoGPCheckForExistingSession
   Type: REG_DWORD
   Data: 1 (do not check); all other values, including 0 (do check)

   With Fix #LA3521, the check is made for a value of 0 and not made for any other values (1 and higher).

   [From XA600R02W2K8R2X64010][#LA3521]

3. A Citrix policy set to filter on connection evidences using Access Gateway connection information fails to apply to sessions authenticated using a smart card.

   [From XA600R02W2K8R2X64056][#LA4245]

4. In certain scenarios, the reconnection process fails to update the connection information (for example – client IP, client name, and Access Gateway information). Instead, the connection information of the connection that originated the session might be preserved.

   [From XA600R02W2K8R2X64057][#LA2349]

5. On Windows Server 2003, you can specify whether a user can reconnect to a session from any client device or only from the originating client. The From originating client only option is not present in the Remote Desktop Services settings of the Windows Server 2008 R2 edition.

   This feature enhancement allows you to implement the same functionality on Windows Server 2008 R2 through XenApp. To enable the feature, you must set the following registry key:

   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Citrix
   Name: ReconnectSame
   Type: REG_DWORD
   Data: 1

   If Workspace Control is enabled in Web Interface, enabling the " Automatically reconnect to sessions when users log on" option can result in side effects and users might have to launch the session twice to open a session from the non-originating client device.

   [From XA600R02W2K8R2X64057][#LA5860]

6. In certain scenarios, the Citrix Group Policies' Access Control filters might fail to work while reconnecting to a disconnected session. This condition can impact the final policy settings that rely on these filters.

   [From XA600R02W2K8R2X64057][#LC0002]

Installing and Uninstalling This Release

Notes:

• This hotfix is packaged with Microsoft Windows Installer 3.0 as a .msp file. For more information about deploying .msp files, see Microsoft article 884016 or visit the Microsoft Web site and search on keyword msiexec.
• This installer program complies with Microsoft User Account Control (UAC). If UAC is enabled, you must run the installer program in elevated mode; that is, with administrative privileges enabled. For more information about UAC, see Microsoft TechNet or visit the Microsoft Web site and search on keyword UAC.
• To install this hotfix successfully, servers must not have registry modification restrictions in place.
• Slipstreaming - installations of the XenApp Server base product packaged with one or more individual hotfixes - is not supported and might leave servers in an unstable state.
• You must restart the server after the installation of this hotfix completes. However, if you are installing multiple hotfixes at the same time, there is no need to restart the server after the installation of each hotfix. It is sufficient to restart the server after the installation of the final hotfix completes.
• If the need arises to restore the original settings and functionality provided by this hotfix, you must uninstall the hotfix before reinstalling it according to the installation instructions below.

To install this hotfix:

1. Copy the hotfix package to an empty folder on the hard drive of the server you want to update.
2. Close all applications.
3. Run the executable.
4. Restart the server. This ensures that the installation completes and that the hotfix is added to the hotfix inventory list of the Delivery Service Console.

To uninstall this hotfix:

1. From the Start menu, select Control Panel > Programs and Features.
2. Highlight the hotfix you want to uninstall and click Uninstall.
3. Follow the directions on-screen.

Files Updated (All Dates/Times UTC)