Hotfix package name: XA600R02W2K8R2X64051.MSP
For: Computers running Windows Server 2008 R2 with Citrix XenApp 6, Hotfix Rollup Pack XA600W2K8R2X64R02 installed
Replaces: XA600R02W2K8R2X64002, XA600R02W2K8R2X64012, XA600R02W2K8R2X64015, XA600R02W2K8R2X64023, XA600R02W2K8R2X64041
Date: April, 2014
Languages supported: English (US), German (DE), Spanish (ES), French (FR), Japanese (JA), Simplified Chinese (SC)
Readme version: 1.01

Readme Revision History

Important Notes about This Release

• 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.

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 experience a fatal exception (DRIVER_IRQL_NOT_LESS_OR_EQUAL), displaying a blue screen, on picadm.sys with bugcheck code 0xd1.

   [From XA600R02W2K8R2X64051][#LA2854]

2. Servers might experience a fatal exception, displaying a blue screen, on picadm.sys with bugcheck code 0x22.

   [From XA600R02W2K8R2X64051][#LA4195]

3. A deadlock in picadm.sys can cause servers to become unresponsive.

   [From XA600R02W2K8R2X64051][#LA4223]

4. On systems with Fixes #LA2067 and #LA2645 installed, it might take a long time to copy files from a client drive to a server while using client drive mapping.

   [From XA600R02W2K8R2X64051][#LA5100]

5. On XenApp 6 systems with Fix #LA2830 installed, attempts to upload a client-side file using a published FTP client can fail. In addition, the data size of the file as indicated in the upload progress bar continues to increase. The issue is an unintended regression introduced by Fix #LA2830, which is enabled by default. After you install Fix #LA5194, Fix #LA2830 is now  disabled  by default to prevent the regression issue. If you do need the enhancement provided by Fix #2830, you can enable it manually by creating the following registry keys:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\picadm\Parameters
   Name: EnableCcReadCache
   Type: REG_DWORD
   Data: 0

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\picadm\Parameters
   Name: EnableCcWriteCache
   Type: REG_DWORD
   Data: 0

   From the description of Fix #LA2830:

   When two users are connected to the same instance of an Access database located on a mapped client drive, neither user can see updates made by the other user when refreshing the database. This is caused by the read/write cache, which is enabled by default.

   [From XA600R02W2K8R2X64051][#LA5194]

6. On systems with Fix LA4309 (Hotfix XA600R02W2K8R2X64041 or its replacement hotfix) installed, servers might experience a fatal exception, displaying a blue screen, on picadm.sys with bugcheck code 0x00000022.

   [From XA600R02W2K8R2X64051][#LA5649]

Fixes from Replaced Hotfixes

1. When updating a file located on a drive mapped outside of the session, the modified size of the file is not updated while using the GetFileSize () function in the session.

   [From XA600R02W2K8R2X64002][#LA2067]

2. Servers might experience a fatal exception, displaying a blue screen, on picadm.sys with bugcheck code 0xD5.

   [From XA600R02W2K8R2X64002][#LA2086]

3. When updating a file located on a drive mapped outside of the session, the modified size of the file is not updated when opening the file through Windows Explorer in the session.

   [From XA600R02W2K8R2X64002][#LA2645]

4. A deadlock in picadm.sys can cause servers to become unresponsive and prevent them from accepting new connections.

   [From XA600R02W2K8R2X64012][#LA3276]

5. A deadlock in picadm.sys can cause servers to become unresponsive.

   [From XA600R02W2K8R2X64015][#LA2010]

6. Servers might experience a fatal exception, displaying a blue screen, on picadm.sys with bugcheck code 0x22.

   [From XA600R02W2K8R2X64023][#LA3640]

7. When two users are connected to the same instance of an Access database located on a mapped client drive, neither user can see updates made by the other user when refreshing the database. This is caused by the read/write cache, which is enabled by default.

   This enhancement allows you to disable the read/write cache by setting the following registry keys:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\picadm\Parameters
   Name: EnableCcReadCache
   Type: REG_WORD
   Data: 1 (enable; default); 0 (disable)

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\picadm\Parameters
   Name: EnableCcWriteCache
   Type: REG_WORD
   Data: 1 (enable; default); 0 (disable)

   [From XA600R02W2K8R2X64041][#LA2830]

8. This fix addresses excessive paged pool memory consumption on servers with sessions using client mapped drives.

   [From XA600R02W2K8R2X64041][#LA4309]

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)