Filename: XA_XD_750_Controller_X64_HFs_001.zip
For: XenApp 7.5 and XenDesktop 7.5 Delivery Controller (64-bit). For operating system requirements, see Citrix eDocs, the Citrix Product Documentation Library.
Replaces: None
Date: March, 2015
Languages supported: English (US), Japanese (JA), Simplified Chinese (SC)
Readme version: 1.00

Readme Revision History

Important Note(s)

• Caution: By design, the Broker Service and the Monitor Service hotfixes (BrokerSrvc750WX64001.msi, MonitorSrvc750WX64001.msi) included in this update modify the DbSchema of both your Broker data store and your Monitor data store, respectively (the "data store"). These modifications are permanent and irreversible. Should you decide, for any reason, to uninstall either the Broker Service or the Monitor Service hotfix at a later time, these modifications will not automatically be reverted. As a matter of precaution, Citrix recommends strongly that you back up your data store before installing the Broker Service and the Monitor Service hotfixes. Doing so allows you to manually restore your data store to the backed up version. Even so, any changes you make to the data store between backing up and restoring it will be lost. For information about backing up and restoring your data store, see Knowledge Center article CTX135207.
• Important: All hotfixes included in this release must be installed; otherwise, your Controller might be left in an unstable state. If you are upgrading from the base (RTM) version of the 7.5 Controller, install all hotfixes included in this package. If you are upgrading from an earlier release of Controller Hotfixes, install only the hotfixes that are new in this package compared to the earlier release you already installed. There is no need to install the individual hotfixes in a specific order.
• For known issues with Citrix XenApp 7.5 and XenDesktop 7.5, see Citrix eDocs.

Where to Find Documentation

• This document describes the issue(s) resolved by this release and includes installation instructions. For additional product information, including supported operating systems and system requirements, see Citrix eDocs, the Citrix Product Documentation Library.
• For information about XenApp and XenDesktop upgrade best practices, see Citrix eDocs.

Known Issues

1. If the hotfix package ConfMgrWOL750WX64001 is installed first, the error message "HCLPlugins\Managed Machine Folder not found" appears. To prevent the error, install the following packages first: Broker Services [BrokerSrvc750WX64001], Machine Creation Services [MCSrvc750WX64001] or Host Services [HostSrvc750WX64001]. Citrix strongly recommends that ConfMgrWOL750WX64001 is installed last.

   If you need to remove the hotfixes, uninstall ConfMgrWOL750WX64001 first and then uninstall the rest of the packages.

2. If a Delegated Administrator account has User Access Control enabled, updates to Delivery Controller are installed to the default location in error. The default location is "systemroot%\Program Files\Citrix" and this might not be the same location where you originally installed Delivery Controller. To resolve this issue, perform one of the following steps:
   
   • Disable User Account Control and then run the msi file.
   • Install the packages as a "local administrator" on the Delivery Controller server when User Account Control is enabled.

   [#LC2252]

3. After applying the Broker Service and/or Monitor Service hotfix included in this update, Desktop Studio prompts for a database upgrade. If you click Start the automatic Site upgrade, the Upgrading Site dialog box appears. In that dialog box, if you click I am ready to upgrade, another dialog box, Studio, appears after the database upgrade completes. The interface of the Studio dialog box is misleading in that it displays a green check mark next to 0 Successful tasks - even though the database upgrade was successful.

Issue(s) Fixed in This Release

1. If PowerShell version 3.0 is installed on Desktop Delivery Controller, after a period of time the Broker Service might fail to send power commands to System Center Virtual Machine Manager (SCVMM) until the Broker Service is restarted.

   [From BrokerSrvc750WX64001, HostSrvc750WX64001, MCSrvc750WX64001] [#LA5090]

2. The memory consumption of the Monitoring Service can grow steadily until the service stops responding to requests from Director, eventually rendering Director unresponsive as well.

   [From MonitorSrvc750WX64001][#LA5615]

3. When the user updates a catalog, the Configuration Logging reports that the "Update Machine Catalog" is successful but one of the tasks in the Task Details view shows the message "Release the provisioning scheme" failed.

   [From MCSrvc750WX64001][#LC0518]

4. This fix addresses a memory consumption issue of the Monitoring Service.

   From MonitorSrvc750WX64001][#LC0537]

5. The following error message might appear on the Citrix Director Dashboard page:

   "Cannot retrieve the data."

   "Data source unresponsive or reported an error. View server event logs for further information."

   [From MonitorSrvc750WX64001][#LC0563]

6. On Japanese versions of the VMware vSphere hypervisor, testing resources on the Studio > Hosting node fails with the error message "'Check the hypervisor storage' is failed."

   [From BrokerSrvc750WX64001, HostSrvc750WX64001, MCSrvc750WX64001][#LC0611]

7. In deployments that use a combination of NetScaler Gateway and StoreFront, starting two VM hosted applications from a single VDA at the same time can cause one of the apps to disconnect and then reconnect while the other VM hosted application fails to start.

   [From BrokerSrvc750WX64001][#LC0634]

8. If the resource name (display name) changes on the Delivery Controller, users who previously subscribed to the applications cannot start the applications.

   [From BrokerSrvc750WX64001][#LC0727]

9. Multiple deadlocks can occur in the Microsoft SQL Server database that hosts XenApp and XenDesktop when load testing with HP LoadRunner and simultaneously accessing multiple published desktops and applications.

   [From BrokerSrvc750WX64001][#LC0877]

10. If you create virtual machines (VM) with Desktop Studio that uses Machine Creation Services and the VMs are hosted on a VMware hypervisor, attempts to update VMs that are part of the machine catalog fail. When this occurs, an error appears in the Machine Creation log that the virtual disk does not exist, but the directory in the datastore does exist.

    [From BrokerSrvc750WX64001, ConfMgrWOL750WX64001, HostSrvc750WX64001, MCSrvc750WX64001][#LC1201]

11. In some Amazon Web Services environments, provisioning desktops with Machine Creation Services (MCS) might fail with the error “No facility for disk upload�, even when the environment is configured correctly.

    [From BrokerSrvc750WX64001][#LC1295]

12. After installing all of the updates in CTX141087 "Hotfixes Update 2 for XD 7.1 Delivery Controller x64," the Logon Duration data does not appear in Director 7.1 or Director 7.6 when accessing Desktop Delivery Controller 7.1.

    [From MonitorSrvc750WX64001][#LC1581]

13. If a Delegated Administrator account has User Access Control enabled, updates to Delivery Controller are installed to the default location in error. The default location is "%systemroot%\Program Files\Citrix" and this might not be the same location where you originally installed Delivery Controller.

    [From BrokerSrvc750WX64001, MCSrvc750WX64001, MonitorSrvc750WX64001][#LC2252]

Component Versions

Installing This Release

Notes:

• This release is packaged as a .zip file containing the replacement .msi files for the various components of XenApp 7.5 and XenDesktop 7.5 Controller. For more information about deploying msi files, see Microsoft article 884016 or visit the Microsoft Web site and search on keyword msiexec.
• By design, the Broker Service and the Monitor Service hotfixes (BrokerSrvc750WX64001.msi, MonitorSrvc750WX64001.msi) included in this update modify the DbSchema of both your Broker data store and your Monitor data store, respectively (the "data store"). These modifications are permanent and irreversible. Should you decide, for any reason, to uninstall either the Broker Service or the Monitor Service hotfix at a later time, these modifications will not automatically be reverted. As a matter of precaution, Citrix recommends strongly that you back up your data store before installing the Broker Service and the Monitor Service hotfixes. Doing so allows you to manually restore your data store to the backed up version. Even so, any changes you make to the data store between backing up and restoring it will be lost. For information about backing up and restoring your data store, see Knowledge Center article CTX135207.
  The DbSchema update succeeds only if at least one site has been created. If you have not yet created a site, carete at least one site before installing this update. Otherwise, the install will fail to update the existing DBSchema and you will need to rebuild your XenDesktop.
• Caution: Downgrades, also known as rollbacks, from individual component hotfixes in this release are not supported and might leave your systems in an unstable state. The component hotfixes in this release do not patch the existing installations of the components - each fully replaces the original component with a new installation. As a result, uninstalling a component hotfix removes the entire component from the Controller. If the need arises to revert to an earlier version of the product, you must uninstall each component hotfix of this release and then reinstall the earlier versions of each component. Reverting to an earlier version of a component might result in the loss of settings you configure while this upgrade is installed.
• Important: All hotfixes included in this release must be installed; otherwise, your Controller might be left in an unstable state. If you are upgrading from the base (RTM) version of the 7.5 Controller, install all hotfixes included in this package. If you are upgrading from an earlier release of Controller Hotfixes, install only the hotfixes that are new in this package compared to the earlier release you already installed. There is no need to install the individual hotfixes in a specific order.
• To install the component hotfixes in the release successfully, servers must not have registry modification restrictions in place.

To install the component hotfixes in this release:

Note: See the Known Issues section for steps you might need to perform before installing this hotfix.

1. Copy the compressed hotfix package to a shared folder on the network.
2. Extract the compressed hotfix package and save the component msi file(s) on the Delivery Controller you want to update.
3. Run the .msi file(s).
4. Restart the Delivery Controller even if not prompted to do so.
5. To upgrade to the latest DbSchema installed by this release, go to the Desktop Studio Dashboard and click Upgrade.

To uninstall this hotfix and revert to an earlier level of the component and the data store:

1. Uninstall the component from ARP/Programs and Features.
2. Restore the data store as described in Knowledge Center article CTX135207.
3. Install the desired level of the component (base or other hotfix).
4. Restart the Controller even if not prompted to do so.