LIMITED RELEASE - Hotfix XA600R02W2K8R2X64094 - For Citrix XenApp 6.0 for Windows Server 2008 R2 - English

LIMITED RELEASE - Hotfix XA600R02W2K8R2X64094 - For Citrix XenApp 6.0 for Windows Server 2008 R2 - English

book

Article ID: CTX209281

calendar_today

Updated On:

Description

Hotfix package name: XA600R02W2K8R2X64094.MSP
For: Computers running Windows Server 2008 R2 with Citrix XenApp 6, Hotfix Rollup Pack XA600W2K8R2X64R02 installed
Replaces: XA600R02W2K8R2X64002, XA600R02W2K8R2X64012, XA600R02W2K8R2X64015, XA600R02W2K8R2X64023, XA600R02W2K8R2X64041, XA600R02W2K8R2X64051, XA600R02W2K8R2X64058, XA600R02W2K8R2X64064, XA600R02W2K8R2X64073, XA600R02W2K8R2X64078, XA600R02W2K8R2X64088, XA600R02W2K8R2X64093
Date: May, 2016
Languages supported: English (US), German (DE), Spanish (ES), French (FR), Japanese (JA), Simplified Chinese (SC)
Readme version: 1.00

Readme Revision History

VersionDateChange Description
1.00May, 2016Initial release

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, including system requirements, see XenApp 6 on the Citrix Product Documentation site.

New Fixes in This Release

  1. If another process holds the same lock as picadm.sys, users cannot log off from the session and the session remains in a disconnected state.

    [From XA600R02W2K8R2X64094][#LC4415]

Fixes from Replaced Hotfixes

  1. This enhancement provides significant improvements in the performance of file transfers. To enable this fix, you must install both a server hotfix (XA650W2K8R2X64R02 or its replacement) and a version of Receiver for Windows (Citrix Receiver for Windows 3.4 Cumulative Update 2 or its replacement) that contains Fix #LA1263.

    Note: After installing this fix, users might experience unexpected session drops when the File Redirection Bandwidth Limit and Overall Session Bandwidth Limit policies are set to 100kbps and 120kbps, respectively. If this happens, modify the value of HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ClientDrive\HighThroughputWindowSize or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ClientDrive\HighThroughputWindowSize(REG_SZ) to 65535 or less on the client device.

    [From XA600R02W2K8R2X64002][#LA1263]

  2. 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]

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

    [From XA600R02W2K8R2X64002][#LA2086]

  4. 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]

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

    [From XA600R02W2K8R2X64012][#LA3276]

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

    [From XA600R02W2K8R2X64015][#LA2010]

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

    [From XA600R02W2K8R2X64023][#LA3640]

  8. 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]

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

    [From XA600R02W2K8R2X64041][#LA4309]

  10. 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]

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

    [From XA600R02W2K8R2X64051][#LA4195]

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

    [From XA600R02W2K8R2X64051][#LA4223]

  13. 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]

  14. 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]

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

    [From XA600R02W2K8R2X64051][#LA5649]

  16. Servers can become unresponsive at random while sessions are logging off. On rare occasions and if left unattended, the servers can experience a fatal exception, displaying a blue screen.

    [From XA600R02W2K8R2X64058][#LA3857]

  17. Servers might experience a fatal exception, displaying a blue screen, on picadm.sys with stop code 0x50.

    [From XA600R02W2K8R2X64058][#LA4939]

  18. Servers might experience a fatal exception, displaying a blue screen, on picadm.sys.

    [From XA600R02W2K8R2X64064][#LA1389]

  19. On systems with Fix #LA4309 (Hotfix XA600R02W2K8R2X64041 or its replacement hotfix) installed, the operating system experiences an error on picadm.sys with bugcheck code 0x00000022 and a blue screen appears.

    [From XA600R02W2K8R2X64064][#LC0088]

  20. The operating system experiences an error on picadm.sys and a blue screen appears with the stop code 0x0000003B.

    [From XA600R02W2K8R2X64073][#LC0896]

  21. If another process holds the same lock as picadm.sys, users cannot log off from the session and the session remains in a disconnected state.

    [From XA600R02W2K8R2X64078][#LC1243]

  22. User sessions might stall in a disconnected state during log off. As a result, the sessions cannot be closed and you cannot restart the server.

    [From XA600R02W2K8R2X64088][#LC0399]

  23. The server can experience a deadlock on picadm.sys that prevents the server from accepting new user connections.

    [From XA600R02W2K8R2X64088][#LC1685]

  24. Sophos Anti-Virus for Windows might fail to scan files under mapped client drives. To enable this fix, you must set the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\picadm\Parameters
    Name: EnableSophosAVSupport
    Type: REG_DWORD
    Data: 1

    [From XA600R02W2K8R2X64093][#LA1855]

  25. A deadlock on picadm.sys can cause published applications to become unresponsive.

    [From XA600R02W2K8R2X64093][#LC3872]

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)

File Name

 

Date

 

Time

 

Size

 

complus_ca.dll

05/05/2016

14:59

841,128

CPatch.exe

05/05/2016

14:59

444,328

Cpatchbackup_Files.vbs

05/05/2016

14:59

3,082

CpatchRestore_Files.vbs

05/05/2016

14:59

3,537

CtxHfLoader.dll

05/05/2016

14:59

288,728

ctxsfoinst_ca.dll

05/05/2016

14:59

194,488

IcaperfCustomActions.dll

05/05/2016

14:59

103,864

ima_msi_ca.dll

05/05/2016

14:59

1,218,480

mf_mm_ca.dll

05/05/2016

14:59

2,954,656

msi50ca.dll

05/05/2016

14:59

432,080

Parra_RunTime_Xml.xml

05/05/2016

14:59

1,354

picadm.sys

05/05/2016

14:58

713,144

picadm.cat (driverfiles)

05/05/2016

14:58

8,080

picadm.inf (driverfiles)

05/05/2016

14:58

2,476

Error.idt (en)

05/05/2016

14:59

35,850

CPatchUI.dll (x32\de)

05/05/2016

14:59

13,232

CPatchUI.dll (x32\en)

05/05/2016

14:59

12,720

CPatchUI.dll (x32\es)

05/05/2016

14:59

13,744

CPatchUI.dll (x32\fr)

05/05/2016

14:59

13,744

CPatchUI.dll (x32\ja)

05/05/2016

14:59

11,696

CPatchUI.dll (x32\zh-cn)

05/05/2016

14:59

11,184

 

File Name

 

MD5 Checksum

 

XA600R02W2K8R2X64094.msp

1EB3AF9145B1648CF178FE5BC6A15928

complus_ca.dll

828AC9897B8D6BE445372742FCBC76CA

CPatch.exe

E0130509E4A61B8E225AB4DCE121BA8F

Cpatchbackup_Files.vbs

0EB9234E7FF2ED9E72337FF26F46AE0E

CpatchRestore_Files.vbs

F64D03B0DC4D0137C3A101B31084D880

CtxHfLoader.dll

1ECC53C0D7C97BE04EEC0F8F1CE3F353

ctxsfoinst_ca.dll

BAC7527CBD92FD0B4F5B495DDAAA32C8

IcaperfCustomActions.dll

11D4A91E8FB2BB274838C45250AB727E

ima_msi_ca.dll

98F1E1808E1922B85B1AEF3B7174FEE4

mf_mm_ca.dll

A9225A273854EE0D43C0B4DE3F58FABD

msi50ca.dll

5075A9961245798FF95E678DB455C43C

Parra_RunTime_Xml.xml

149B41A05D92BFF44C6A26EFAFA99724

picadm.sys

0D8BDB0032C413A5BC1B6A1C23FF69F2

picadm.cat (driverfiles)

6FF4E7E9D4EB28E7608F7089DCE63259

picadm.inf (driverfiles)

19D209A85003D31F39C7A216B833C020

Error.idt (en)

48633A51D4A647553FFABC72739AAB33

CPatchUI.dll (x32\de)

1E3916C350F8BFF385A1DE5220456555

CPatchUI.dll (x32\en)

7500103A935F0D723C461F49A70FBB60

CPatchUI.dll (x32\es)

417641F83EE48F58FB5BCA333AE9B41D

CPatchUI.dll (x32\fr)

541F401CBCFF1734A81C78FC02BA136E

CPatchUI.dll (x32\ja)

2589B3D17004BF673DE60B164F6F168F

CPatchUI.dll (x32\zh-cn)

351BDC93974F93289CA7F21D653AAD2C