CTX139460<\/a>. This points to a change in the vCenter networking config, but supposedly there weren’t any changes. Time to do some digging. I asked them to get networking info from both vCenter and CItrix using PowerShell.<\/p>\n\n\n\nTo get the hypervisor networking I asked him to log in to one of the delivery controllers, launch PowerShell as administrator, and run the following:<\/p>\n\n\n\n
Add-PSSnapin Citrix*
dir XDHyp:\\HostingUnits | Select PSPath,HostingUnit*,*Network* | Format-List<\/pre>\n\n\n\nThe output of this was:<\/p>\n\n\n\n
PSPath : Citrix.Host.Admin.V1\\Citrix.Hypervisor::XDHyp:\\HostingUnits\\DR_Cluster-vm_dr
HostingUnitName : DR_Cluster-vm_dr
HostingUnitUid : bddd641a-a55c-4f0e-bd62-9331502fd908
NetworkId : Network:network-641<\/strong>
NetworkPath : XDHyp:\\Connections\\PRDVCENTER01\\DR.datacenter\\DR Cluster.cluster\\VM Network 201.network
...<\/pre>\n\n\n\nThe thing to take note of is the ‘NetworkId<\/strong>‘ for the DR hosting connection. This Id is the vCenter MoRef (Managed Object Reference) for the VM network. I then had him pull the VM networks from vCenter using PowerCLI.<\/p>\n\n\n\nTo get the VM networks (with MoRef) from vCenter I asked him to launch VMware PowerCLI as administrator and run the following:<\/p>\n\n\n\n
Connect-VIServer prdvcenter01.domain.com
Get-View -ViewType Network | Select Name,MoRef
<\/pre>\n\n\n\nThe output of this was:<\/p>\n\n\n\n
Name MoRef
---- -----
VM Network 201 Network-network-4790
...<\/pre>\n\n\n\nThe MoRef was network-641<\/strong> in MCS, but network-4790<\/strong> in vCenter even though the VM network names were the same. From this it was clear there was a networking change performed on the vCenter side at some point. After stating this, it was revealed that port groups were deleted and recreated (which generated new MoRef ids) in this DR cluster. At this point we have to reconfigure the hosting connection networking with the new MoRef and this cannot be done in Citrix Studio. To do this we have to reconfigure the ‘NetworkPath<\/strong>‘ in the hosting connection, but use the same ‘NetworkPath<\/strong>‘ since the network name did not change. Running this will force the network MoRef to be queried and updated in the MCS hosting connection.<\/p>\n\n\n\nTo reset (or change if needed) the ‘NetworkPath<\/strong>‘ in the hosting connection you take the ‘PSPath<\/strong>‘ from the first command and copy everything starting with ‘XDHyp<\/strong>‘. I took that path and provided them with this command to run:<\/p>\n\n\n\nSet-Item \u2013Path \u2018XDHyp:\\HostingUnits\\DR_Cluster-vm_dr\u2019 \u2013NetworkPath \u2018XDHyp:\\Connections\\PRDVCENTER01\\DR.datacenter\\DR Cluster.cluster\\VM Network 201.network\u2019<\/pre>\n\n\n\nFinally, I asked them to re-run the first ‘dir<\/strong>‘ command again to verify the network MoRef updated. After doing this they were able to successfully update the machine catalog.<\/p>\n","protected":false},"excerpt":{"rendered":"I recently received a call from a former colleague where they were unable to update a machine catalog. They stated nothing had changed in vCenter, Citrix, or the master image. The error they were receiving was: Error Id: XDDS:919D761EException: Citrix.Console.Models.Exceptions.ProvisioningTaskException Create Catalog failed with an unknown reason, see terminating error for more details. at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.CheckForTerminatingError(SdkProvisioningSchemeAction […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[63,61],"tags":[29,10,31,30,14,9,32,33],"class_list":["post-68","post","type-post","status-publish","format-standard","hentry","category-citrix","category-vmware","tag-citrix","tag-esx","tag-machine-creation-services","tag-mcs","tag-vcenter","tag-vmware","tag-xenapp","tag-xendesktop"],"_links":{"self":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts\/68","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=68"}],"version-history":[{"count":7,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts\/68\/revisions"}],"predecessor-version":[{"id":118,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=\/wp\/v2\/posts\/68\/revisions\/118"}],"wp:attachment":[{"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=68"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=68"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.markdepalma.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=68"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}