One of the issues that has faced both MCS and, to a lesser extent, PVS, is when you need to change the name of storage, network, or datacenter paths on your hypervisor after you already create HostingUnits/Resources and Catalogs, the XenApp & XenDesktop Catalog can stop performing as expected.
The first you know that you have an issue is when — either the PVS creation wizard fails to create machines on an existing HostingUnit or if you are using MCS — 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.
However, in XenApp & XenDesktop 7.13, you are now able to 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. This is not quite as seamless as I would like, but is very 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 calling
Update-HypHypervisorConnection -LiteralPath "XDHyp:\Connections\MyConnection"Where “MyConnection” is the name of the connection that contains all the HostingUnits to check.
In Citrix Studio, click on the edit storage option in the Hosting node, this causes all object on the HostingUnit to be checked and updated if required, the wizard can then be cancelled.
After either of the two options are done the hostunit will now point to the correct objects and all operations should carry on a expected.
Things to Note:
Currently, this will only work on connections created 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 can not be correctly found by ID. I am looking at ways that we can derive this information on a upgraded XenDesktop & XenApp and hope that this functionally will be added soon.
While the above screen shot contains an XenServer connection, this functionality will work on all hypervisor types, i.e. XenServer, VMWare, SCVMM, AWS and Azure.