You may encounter a situation where XenApp & XenDesktop Catalog can stop performing as expected when you need to change the name of storage, network or datacenter paths on your hypervisor after you have created HostingUnits/Resources and Catalogs. This is mostly seen in MCS and to an extent in PVS.

When the PVS creation wizard fails to create machines on an existing HostingUnit or if you are using MCS and you are unable to Add, Remove, Update machine or the powerstate of existing machines go to unknown. This is a less-than-desirable state to be in and the only remedy, before XenApp & XenDesktop 7.13, was to manually rename them.

With XenApp & XenDesktop 7.13, you can cause the Hosting Unit (and the catalogs that uses those hosting unit) to check its references to storage, network and root paths that it contains and update them, as required, without having to rename the hypervisor object back to the original name or creating a new Hosting Unit and catalogs.

It is easy to invoke the HostingUnit to check (and update) the names of objects it points to Via powershell, you can update every Hosting Unit on a given connection by
Update-HypHypervisorConnection -LiteralPath "XDHyp:\Connections\MyConnection"
Where “MyConnection” is the name of the connection that contains all the HostingUnits to check.

In Citrix Studio, when you click on the edit storage option in the Hosting node, all objects on the HostingUnit would be checked and updated if required, the wizard can then be cancelled. After either of the two options are done the hostunit will point to the correct objects and all operations would proceed as expected.

Note: This currently works on 7.13 onwards. i.e. if a connection was created on 7.6->7.12 and then the DDC was upgrade the Cmdlet will not fail or report warnings but the hosting unit will not be updated. This is because connections created before 7.13 don’t contain some objects types, so the objects may not be found by ID.
For XenServer connection, this functionality will work on all hypervisor types, i.e. XenServer, VMWare, SCVMM, AWS and Azure.