Hotfix package name: XAE500R01W2K8X64089.MSP
For: Citrix XenApp 5 for Windows Server 2008 64-bit Edition with Hotfix Rollup Pack XAE500W2K8X64R01
Replaces: XAE500R01W2K8X64001, XAE500R01W2K8X64022, XAE500R01W2K8X64036, XAE500R01W2K8X64041, XAE500R01W2K8X64044, XAE500R01W2K8X64052, XAE500R01W2K8X64068, XAE500R01W2K8X64074, XAE500R01W2K8X64079, XAE500R01W2K8X64083
Date: November, 2013
Language supported: English (US)
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. With the "Restrict Terminal Services users to a single remote session" policy enabled and the application instance limit set to "1," attempts to relaunch an application from a disconnected session can fail with the following error message. The issue occurs when the session is still active on the server.

   "You already have an instance of this application open and are not allowed to run more than one instance."

   [From XAE500R01W2K8X64089][#LA3959]

2. This fix addresses the following issues:

   • Even with Workspace Control/SmoothRoaming enabled, users are sometimes presented with a locked desktop when trying to reconnect to a session. The issue occurs when making several reconnection attempts in rapid succession, specifically when trying to reconnect multiple times within the same 20 seconds. This behavior is as designed as the minimum wait time before a session can be disconnected is hard-coded at 20 seconds. Thus, making an additional reconnection attempt within 20 seconds of the previous attempt causes users to be presented with a locked desktop. This fix introduces support for the following registry key that allows you to configure the minimum wait time before a session can be disconnected:

     HKEY_LOCAL_MACHINE\Software\Wow6432Node\Citrix\WFShell
     Name: SessionReconnectMinTimeInMilliSeconds
     Type: REG_DWORD
     Value: 20000 (default)

     For related information, see Knowledge Center article CTX138189.

   • When attempting to reconnect to a disconnected session that is locked, users might be prompted to reauthenticate. To enable this fix, you must set the following registry key:

     HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\WFShell
     Name: LockOnReconnect
     Type: REG_DWORD
     Data: <0=OFF; any other value=ON (default)>

     For related information, see Knowledge Center article CTX138189.

   [From XAE500R01W2K8X64089][#LA4724]

Fixes from Replaced Hotfixes

1. On servers with Hotfix Rollup Pack 1 installed, local file type associations for Windows Internet Explorer no longer work after a published application is run.

   [From XAE500R01W2K8X64001][#250962]

2. A NULL pointer can cause the svchost.exe process to exit unexpectedly while the operating system is starting.

   [From XAE500R01W2K8X64022][#246851]

3. This is an enhancement aiming to increase the robustness of the Automatic Client Reconnection feature.

   [From XAE500R01W2K8X64022][#247586]

4. Terminal Services can exit unexpectedly, causing sessions to be disconnected at random.

   [From XAE500R01W2K8X64036][#258283]

5. Attempts to launch Windows Internet Explorer from an http, https, or mms hyperlink embedded in a streamed application fail. The issue occurs because XenApp does not create the HKEY_CLASSES_ROOT\htmlfile\shell\opennew\command_backup registry key as part of server file type association.

   [From XAE500R01W2K8X64041][#250332]

6. In certain scenarios, clicking a URL in Microsoft Outlook within a published desktop session fails to launch Internet Explorer while Google Chrome browser is running in the same session.

   [From XAE500R01W2K8X64052][#LA0937]

7. On occasion, attempts to reconnect to a disconnected session can fail and a new session starts in addition to the existing session. The issue occurs when the "Restrict each user to a single session" setting of the Terminal Services property is not enabled.

   [From XAE500R01W2K8X64068][#LA1596]

8. Provisioned XenApp servers refuse to accept connections if they are restarted while the license server is unavailable. The issue occurs because the license server cache file, MPS-WSXICA_MPS-WSXICA.ini, is saved in the %ProgramFiles (x86)%\Citrix\system32\cache folder, which might be unavailable when the server image shuts down.

   This fix allows you to save the license server cache file in a shared network location - a location separate from the XenApp server image - so that the file is available even when the server image shuts down. If you save the file in a location away from the server image, you must set the following registry key to point to the cache file location:

   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Install
   Name: CacheLocation
   Type: REG_SZ
   Data: <network location of license server cache file>

   Note : You must restart the server after this registry edit in order for the license file to be cached.

   For more information, see Knowledge Center article CTX135301.

   [From XAE500R01W2K8X64068][#LA1661]

9. When several Provisioning Servers are restarting simultaneously, XenApp connections might not immediately be available and the following message appears:

   "Please wait for Local Session Manager."

   [From XAE500R01W2K8X64074][#LA3011]

10. This enhancement extends Fix #LA0367 so that the functionality introduced by #LA0367 is also available when reconnecting from a client device other than the one on which the original session was created.

    From Fix #LA0367:

    Attempts to reconnect to a disconnected session can result in a new session when launching a different application after reconnecting.

    To enable this fix, you must set the following registry keys:

    On 32-bit Windows:

    HKEY_LOCAL_MACHINE\Software\Citrix\IMA
    Name: ReconnectWithNewApplication
    Type: REG_DWORD
    Data: 1

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Citrix
    Name: ReconnectWithNewApplication
    Type: REG_DWORD
    Data: 1

    On 64-bit Windows:

    HKEY_LOCAL_MACHINE\Software\Wow6432Node\Citrix\IMA
    Name: ReconnectWithNewApplication
    Type: REG_DWORD
    Data: 1

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Citrix
    Name: ReconnectWithNewApplication
    Type: REG_DWORD
    Data: 1

    [From XAE500R01W2K8X64079][#LA3192]

Installing and Uninstalling This Release

Notes:

• Before installing this hotfix, make sure to verify the digital certificate chain validation of the MSP package. For more information, see Knowledge Center article CTX129998.
• 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.
• This hotfix might or might not prompt you to restart the server when the installation or uninstallation is complete. If you are using the Access Management Console, you must restart the server after installing or uninstalling this hotfix to ensure that the hotfix is added to or removed from the console's hotfix inventory list.
• 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. Open the Properties tab of the package and verify the digital certificate chain validation.
3. Close all applications.
4. Run the executable.
5. Restart the server. This ensures that the installation completes and that the hotfix is added to the hotfix inventory list of the Access Management 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)