Hotfixes Update 3 – For Delivery Controller 7.6 (64-bit) – English

Filename: XA_XD_760_Controller_X64_HFs_3.zip

For: XenApp 7.6 and XenDesktop 7.6 Delivery Controller (64-bit). For operating system requirements, see System Requirements on the Citrix Product Documentation site.

Replaces: BrokerSrvc760WX64001, HostSrvc760WX64001, MCSrvc760WX64001, MonitorSrvc760WX64001, BrokerSrvc760WX64002, ConfigMgrWOL760WX64002, HostSrvc760WX64002, MCSrvc760WX64002, MonitorPSSI760WX64002, MonitorSrvc760WX64002

Date: November, 2015

Languages supported: English (US), Japanese (JA), Simplified Chinese (SC)

Readme version: 1.02

Readme Revision History

Version

Date

Change Description

December, 2016

Link to Smart Check tool added

1.02

February, 2016

Added Known Issues

1.01

January, 2016

Data store information updated in Important Note(s)

1.00

November, 2015

Initial release

Important Note(s)

  • Caution: The Host Service hotfix (HostSrvc760WX64003.msi) included in this update modifies the Host DbSchema of the Site data store. In addition, if you are upgrading from the base 7.6 Controller or from Update 1, the Broker Service hotfix (BrokerSrvc760WX64003.msi) included in this update also modifies the Broker DbSchema of the Site data store.* These modifications are permanent and irreversible. Should you decide, for any reason, to uninstall either of the hotfixes that modify your Site data store’s DbSchema(s) at a later time, these modifications do not revert automatically. As a result and as a matter of precaution, Citrix recommends strongly that you back up your Site data store as described below before installing this update. Doing so allows you to manually restore your Site data store to the backed up version. Even so, any changes you make to your Site data store between backing up and restoring it are lost. For information about backing up and restoring data stores, see Knowledge Center article CTX135207.

    * Depending on which version of the 7.6 Controller you are upgrading from, Update 3 modifies the following DbSchema(s) of your Site data store:

    • If you are upgrading from the base 7.6 Controller or from Controller 7.6 Hotfixes Update 1, both the Host and the Broker DbSchemas of your Site data store are going to be modified. Back up your Site data store before installing this update.
    • If you are upgrading from Controller 7.6 Hotfixes Update 2, the Host DbSchema of your Site data store is going to be modified. Back up your Site data store before installing this update.

    For an automatic database upgrade, the Studio user’s permissions must include the ability to update the SQL Server database schema (for example, the db_securityadmin or db_owner database role). If the Studio user does not have those permissions, initiating a manual database upgrade will generate scripts. The Studio user runs some of the scripts from Studio; the database administrator runs other scripts using a tool such as SQL Server Management Studio. If the SQL scripts are run manually, they should be run using either the SQLCMD utility or using the SQL Management Studio in SQLCMD mode. Inaccurate errors may result otherwise.

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

  • After the upgrade to this release, a prompt appears for the License Server compatibility check in Desktop Studio that makes sure that your License server is the required version. If you are using the License server released with XenDesktop 7.6 or from a more recent version, you do not need to upgrade the License server. Click Continue to proceed with the DBschema upgrade.

  • For information about known issues, see Known issues in XenApp 7.6 and XenDesktop 7.6 on the Citrix Product Documentation site.

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 XenApp and XenDesktop 7.6 on the Citrix Product Documentation site.
  • For information about XenApp and XenDesktop upgrade best practices, see Upgrade a deployment on the Citrix Product Documentation site.
  • For information about installing 7.x Controller hotfixes, see Knowledge Center article CTX201988.

Known Issues

  1. If the hotfix package ConfMgrWOL760WX64003 is installed first, the error message “HCLPluginsManaged Machine Folder not found” appears. To prevent the error, install the following packages first: Broker Services [BrokerSrvc760WX64003], Machine Creation Services [MCSrvc760WX64003] or Host Services [HostSrvc760WX64003]. Citrix strongly recommends that ConfMgrWOL760WX64003 is installed last.

    If you need to remove the hotfixes, uninstall ConfMgrWOL760WX64003 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 FilesCitrix” 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.

New Fixes in This Release

  1. This fix addresses a memory issue in an underlying component the occurs when running System Center Virtual Machine Manager (SCVMM) connections.

    [From BrokerSrvc760WX64003, HostSrvc760WX64003, MCSrvc760WX64003][#LC1730]

  2. The tabs in the “Trends” page and “Filters option” page in Desktop Director might fail to show the data with an error message.

    [From MonitorSrvc760WX64003][#LC2035]

  3. The following error message might be incorrectly logged in the application log each time the Citrix Monitor Service starts even though the service is working correctly:

    “Error querying the Broker via GetBrokerObjects to obtain ‘Controller Machine Details'”

    [From MonitorSrvc760WX64003][#LC2239]

  4. After upgrading the Desktop Controller from Version 7.x to Version 7.6, if the PowerShell command “Set-MonitorConfiguration” is run, the following error message appears:

    “A database operation failed and cannot be recovered.”

    [From MonitorSrvc760WX64003][#LC2745]

  5. Attempts to add more than 999 virtual machines (VMs) to a single catalog might fail.

    [From BrokerSrvc760WX64003][#LC2873]

  6. With this fix the following issues can be resolved:

    • When the host connection is configured to US-East-1e regions, the Amazon Web Services (AWS) connection can be established, however, the machine creation might fail.
    • When attempting to add AWS host connection to use EU-Central-1, the host connection creation might fail with an authentication error.

    [From BrokerSrvc760WX64003, HostSrvc760WX64003, MCSrvc760WX64003][#LC3239]

  7. Machine Creation Services (MCS) might not honor the “AvailableForPlacement” flag on System Center Virtual Machine Manager (SCVMM) 2012 hosts. As a result, the machine creation might fail if a host with insufficient resource is chosen.

    [From BrokerSrvc760WX64003, HostSrvc760WX64003, MCSrvc760WX64003][#LC3426]

  8. After the latest Microsoft Hotfix Rollup Pack 7 in the System Center Virtual Machine Manager (SCVMM) 2012 R2 environment is installed, catalog creation with Machine Creation Services (MCS) might fail.

    [From BrokerSrvc760WX64003, HostSrvc760WX64003, MCSrvc760WX64003, ConfigMgrWOL760WX64003][#LC3822]

Fixes from Previously Released Hotfixes

  1. If the XenServer parameter “TimeOffSe” exists on the master image virtual machine (VM), creating the Machine Creation Services (MCS) catalog fails. To check the existence of the parameter, in the XenServer console, run the command “xe vm-list uuid= params=other-config”. To resolve this issue, apply this hotfix or manually remove the parameter by running the XenServer command “xe vm-param-remove uuid= param-name=other-config param-key=timeoffset”.

    [From BrokerSrvc760WX64001, HostSrvc760WX64001, MCSrvc760WX64001][#LC1071]

  2. The Monitoring Service prematurely deletes the application instance history after seven days instead of the default 90 days. This occurs in XenDesktop and XenApp deployments with Platinum Edition licensing.

    [From MonitorSrvc760WX64001][#LC1129]

  3. In Desktop Director, on the “Trends > Hosted Applications Usage” tab, the totals for each application do not equal the sum total for all applications. This occurs in environments running for seven days or longer.

    [From MonitorSrvc760WX64001][#LC1130]

  4. 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 BrokerSrvc760WX64001, HostSrvc760WX64001, MCSrvc760WX64001][#LC1295]

  5. 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 MCSrvc760WX64002][#LC0518]

  6. 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 BrokerSrvc760WX64002, ConfigMgrWOL760WX64002, HostSrvc760WX64002, MCSrvc760WX64002][#LC1201]

  7. When provisioning VDAs by using the Machine Creation Service, the primary DNS suffix changes for the VDAs.

    [From MCSrvc760WX64002][#LC1300]

  8. If a VDA in a shared delivery group is tagged and the tag is used as part of a policy filter, the policies are not applied to other VDAs in the delivery group.

    [From BrokerSrvc760WX64002][#LC1506]

  9. Creating new catalogs fail after upgrading to XenDesktop 7.6 and if the master VM image contains a nested hardware virtualization property that is enabled on VMware vSphere 5.1.

    [From BrokerSrvc760WX64002, HostSrvc760WX64002, MCSrvc760WX64002][#LC1586]

  10. In the Powershell snap-in, running the command Get-Help set-MonitorConfiguration -detailed returns the error message -“GroomApplicationInstanceRetentionDays <Int32> FIXME”.

    [From MonitorPSSI760WX64002][#LC2176]

  11. 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 FilesCitrix” and this might not be the same location where you originally installed Delivery Controller.

    [From BrokerSrvc760WX64002, HostSrvc760WX64002, MCSrvc760WX64002, MonitorSrvc760WX64002][#LC2252]

  12. If a virtual graphics processing unit (VGPU) is enabled in the VM master image in VMware vSphere 6 with a GRID board, the machine creation process fails.

    [From BrokerSrvc760WX64002, HostSrvc760WX64002, MCSrvc760WX64002][#LC2326]

  13. When users log off from a session, the End Date updates incorrectly in the database, including all application instances running within a session and applications that are closed before the session ended.

    [From MCSrvc760WX64002, MonitorSrvc760WX64002][#LC2435]

  14. The VDA provisioned by integrated Hyper-V appears unregistered after subscribing successfully.

    [From BrokerSrvc760WX64002, HostSrvc760WX64002, MCSrvc760WX64002][#LC2722]

  15. This release adds support for the Linux Broker Agent.

    [From BrokerSrvc760WX64002][#LC3146]

Component Versions

Component Hotfix Name Version MSI Name

Citrix Broker Service

BrokerSrvc760WX64003

7.6.3.5024

BrokerSrvc760WX64003.msi

Citrix ConfigMgr WOL

ConfigMgrWOL760WX64003

7.6.3.5014

ConfigMgrWOL760WX64003.msi

Citrix Host Service

HostSrvc760WX64003

7.6.3.5021

HostSrvc760WX64003.msi

Citrix Machine Creation Service

MCSrvc760WX64003

7.6.3.5020

MCSrvc760WX64003.msi

Citrix Monitor Service

MonitorSrvc760WX64003

7.6.3.5014

MonitorSrvc760WX64003.msi

Citrix Monitor Service PowerShell snap-in

MonitorPSSI760WX64002

7.6.2.5014

MonitorPSSI760WX64002.msi

Installing This Release

Notes:

  • This release is packaged as a .zip file containing the replacement .msi files for the various components of XenApp 7.6 and XenDesktop 7.6 Controller. For more information about deploying msi files, see Microsoft article 884016 or visit the Microsoft Web Site and search on keyword msiexec.
  • Caution: The Host Service hotfix (HostSrvc760WX64003.msi) included in this update modifies the Host DbSchema of the Site data store. In addition, if you are upgrading from the base 7.6 Controller or from Update 1, the Broker Service hotfix (BrokerSrvc760WX64003.msi) included in this update also modifies the Broker DbSchema of the Site data store.* These modifications are permanent and irreversible. Should you decide, for any reason, to uninstall either of the hotfixes that modify your Site data store’s DbSchema(s) at a later time, these modifications do not revert automatically. As a result and as a matter of precaution, Citrix recommends strongly that you back up your Site data store as described below before installing this update. Doing so allows you to manually restore your Site data store to the backed up version. Even so, any changes you make to your Site data store between backing up and restoring it are lost. For information about backing up and restoring data stores, see Knowledge Center article CTX135207.

    * Depending on which version of the 7.6 Controller you are upgrading from, Update 3 modifies the following DbSchema(s) of your Site data store:

    • If you are upgrading from the base 7.6 Controller or from Controller 7.6 Hotfixes Update 1, both the Host and the Broker DbSchemas of your Site data store are going to be modified. Back up your Site data store before installing this update.
    • If you are upgrading from Controller 7.6 Hotfixes Update 2, the Host DbSchema of your Site data store is going to be modified. Back up your Site data store before installing this update.

    For an automatic database upgrade, the Studio user’s permissions must include the ability to update the SQL Server database schema (for example, the db_securityadmin or db_owner database role). If the Studio user does not have those permissions, initiating a manual database upgrade will generate scripts. The Studio user runs some of the scripts from Studio; the database administrator runs other scripts using a tool such as SQL Server Management Studio. If the SQL scripts are run manually, they should be run using either the SQLCMD utility or using the SQL Management Studio in SQLCMD mode. Inaccurate errors may result otherwise.

  • 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.6 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.
  • For information about installing XenDesktop/XenApp 7.x Controller hotfixes, see Knowledge Center article CTX201988.

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.

Related:

  • No Related Posts

Leave a Reply