Filename: XD710_Controller_X64_HFs_3.zip
For: Citrix XenDesktop 7.1 Delivery Controller (64-bit). For operating system requirements, see Citrix Product Documentation.
Replaces: XD710BrokerSvcWX64002, XD710HostSvcWX64002, XD710MCSvcWX64002, XD710MonitorSvcWX64002
Date: April, 2015
Languages supported: English (US), Japanese (JA), Simplified Chinese (SC)
Readme version: 1.00

Readme Revision History

Important Note(s)

• Caution:
  • If upgrading from Update 1 or Base (RTM), by design, the Broker Service and the Monitor Service hotfixes (Broker_Service_x64.msi, Monitor_Service_x64.msi) included in this update modifies the DbSchema of both your Broker data store and your Monitor data store, respectively (the "data store").
  • If upgrading from Update 2, by design, only the Monitor Service hotfix (Monitor_Service_x64.msi) included in this update modifies the DbSchema in your Monitor data store (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.1 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 XenDesktop 7.1, see Citrix Product Documentation.

Known Issues in This Release

1. After applying either the Broker Service or the Monitor Service hotfix (or both) included in this update, Desktop Studio prompts for a database upgrade. After selecting the settings "Start the automatic Site upgrade > I am ready to upgrade," the "Studio" dialog box appears after the database upgrade is complete. In the "Studio" dialog box, a green check mark appears next to "0 Successful tasks," which is incorrect. The database upgrade is successful.
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]

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 Product Documentation.
• For information about XenDesktop upgrade best practices, see XenDesktop 7 upgrade components or Upgrade XenDesktop 5 in Citrix Product Documentation.

New Fixes 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 XD710BrokerSvcWX64003, XD710HostSvcWX64003, XD710MCSvcWX64003][#LA5090]

2. This fix addresses an intermittent high memory utilization issue of the Broker Service on the Controller.

   [From XD710BrokerSvcWX64003][#LA5629]

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 XD710MCSvcWX64003][#LC0518]

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

   [From XD710MonitorSvcWX64003][#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 XD710MonitorSvcWX64003][#LC0563]

6. When two or more instances of event ID 3012 record in the event log, event IDs 3020 and 3021 also appear in the log and the messages are incorrect. With this fix, if two or more instances of event ID 3012 record, then event IDs 3010 and 3011 correctly appear in the log.

   [From XD710BrokerSvcWX64003][#LC1425]

7. 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 XD710MonitorSvcWX64003][#LC1581]

8. The error messages for event IDs 1110 and 1111 are incorrect in the event log. With this fix, the following correct messages appear in the event log:

   • EventID:1110: To avoid excessive event logging, the service is temporarily suppressing related messages (event IDs 1100-1109, 1112-1116).
   • EventID:1111: The service is no longer suppressing related messages (event IDs 1100-1109, 1112-1116).

   [From XD710BrokerSvcWX64003][#LC1485]

9. 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 XD710BrokerSvcWX64003][#LC2252]

Fixes from Replaced Hotfixes

1. In deployments that use a combination of NetScaler Gateway and StoreFront, launching two VM hosted apps on a single VDA at the same time can cause one of the apps to disconnect and then reconnect while the other VM hosted app fails to launch.

   [From XD710BrokerSvcWX64002][#LA4925]

2. Machine creation and provisioning might fail in XenDesktop 7.1 deployments running standalone Microsoft System Center Virtual Machine Manager with Hyper-V and using local shared storage or Server Message Block (SMB) type storage repositories.

   [From XD710BrokerSvcWX64002, XD710HostSvcWX64002, XD710MCSvcWX64001][#LA5271]

3. 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 XD710MonitorSvcWX64002][#LA5615]

4. SCVMM Hyper-V local storage enumerates but machine provisioning fails unless the local storage is a shared drive.

   [From XD710BrokerSvcWX64002, XD710HostSvcWX64002, XD710MCSvcWX64002][#LA5693]

5. Some Server OS VDAs scheduled for daily restart can fail to power up. The issue occurs with Server OS VDAs that receive the scheduled shutdown request at a time when they are already in a shut down state.

   [From XD710BrokerSvcWX64002][#LC0122]

6. Setting the character locale to "zh-CN" can cause the following error message to appear when setting the "logsite" and when running "Test Site" reports in Citrix Studio:

   "An invalid Configuration Logging locale: ’zh-CN‘ was set."

   [From XD710ConfigLoggingSvcWX64002][#LC0214]

7. When renaming a site by running the command "set-configsite -sitename "newsitename", the Test Site test in Citrix Studio can fail.

   [From XD710BrokerSvcWX64002][#LC0224]

8. This fix addresses an issue that prevents the Machine Creation Service from creating machines in multiple site domains while there are DNS issues anywhere in the domain or any child domains.

   [From XD710MCSvcWX64002][#LC0429]

9. In deployments that use Microsoft System Center Virtual Machine Manager and a standalone Hyper-V where the VMs are stored on Hyper-V's root drive, if you provision a VM by using the Machine Creation Service and then assign the VM to a desktop group, the Controller logs a system event with ID 2006.

   [From XD710BrokerSvcWX64002, XD710HostSvcWX64002, XD710MCSvcWX64002][#LC0905]

Component Versions

Installing This Release

Notes:

• This release is packaged as a .zip file containing the replacement .msi files for the various components of Version 7.1 of the XenDesktop Controller. For more information about deploying msi files, see Microsoft article 884016 or visit the Microsoft Web site and search on keyword msiexec.
• Caution:
  • If upgrading from Update 1 or Base (RTM), by design, the Broker Service and the Monitor Service hotfixes (Broker_Service_x64.msi, Monitor_Service_x64.msi) included in this update modifies the DbSchema of both your Broker data store and your Monitor data store, respectively (the "data store").
  • If upgrading from Update 2, by design, only the Monitor Service hotfix (Monitor_Service_x64.msi) included in this update modifies the DbSchema in your Monitor data store (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.

• 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.1 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 this release:

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.