Change existing Hypervisorconnection / Move Machines to new Hypervisorconnection

[Dennis Reimer1709157751]

If you are having issues with your existing XenDesktop Hypervisorconnection, maybe Certificate Errors or something else you can simply create a new Hypervisorconnection and move the existing Machinecatalogs/Desktopgroups to the new Hypervisorconnection via the following powershell commands (tested with XenDesktop 7.17):

 

1. PS C:\Users\administrator> add-pssnapin citrix*

2. PS C:\Users\administrator> Get-BrokerHypervisorConnection

Capabilities                           : {PowerOn, PowerOff, SuspendResume, Reset...}
ExplicitPreferredController            : False
HypHypervisorConnectionUid             : 4ebd79c6-e194-4685-9cf0-83cbd562ab95
IsReady                                : True
MachineCount                           : 2
MaxAbsoluteActiveActions               : 100
MaxAbsoluteNewActionsPerMinute         : 10
MaxAbsolutePvdPowerActions             : 50
MaxPercentageActiveActions             : 20
MaxPvdPowerActionsPercentageOfDesktops : 25
MetadataMap                            : {}
Name                                   : XEN01 <-- Existing Hypervisorconnection
PreferredController                    : Domain\DDC01
State                                  : On
Uid                                    : 1 <-- Existing UiD

Capabilities                           : {PowerOn, PowerOff, SuspendResume, Reset...}
ExplicitPreferredController            : False
HypHypervisorConnectionUid             : 42de21c6-c04b-4ace-a1d5-89afa80bdf41
IsReady                                : True
MachineCount                           : 1
MaxAbsoluteActiveActions               : 100
MaxAbsoluteNewActionsPerMinute         : 10
MaxAbsolutePvdPowerActions             : 50
MaxPercentageActiveActions             : 20
MaxPvdPowerActionsPercentageOfDesktops : 25
MetadataMap                            : {}
Name                                   : TestHypervisor <-- New Hypervisorconnection
PreferredController                    : Domain\DDC01
State                                  : On
Uid                                    : 2 <-- New UiD (Note this UiD)

 

3. PS C:\Users\administrator> Get-BrokerMachine -AdminAddress ddc.domain.local | where {(($_.CatalogName -eq "YourMachineCatalogName"))} | ForEach-Object { set-brokermachine -HypervisorConnectionUid 2 -MachineName $_.MachineName }

 

(You only have to change the HypervisorconnectionUid, after that the corresponing values will automatically change!)

 

4. PS C:\Users\administrator>Get-BrokerMachine

 

Search for a Machine within the changed catalog and look for the following lines, it should be showing the new Hypervisorconnection:

 

HypHypervisorConnectionUid  : 42de21c6-c04b-4ace-a1d5-89afa80bdf41
HypervisorConnectionName    : TestHypervisor
HypervisorConnectionUid     : 2

 

Do this for all other machine catalogs and after that:

 

5. PS C:\Users\administrator> Get-BrokerHypervisorConnection

 

look for the line MachineCount of the old HypervisorConnection, wait until it´s showing 0

 

If you now look into your Citrix Director you maybe see powerstate "unknown" for your machines, so you have to restart all Citrix Services on all DDC´s (or just reboot all of them)

 

6. PS C:\Users\administrator> get-service citrix* | restart-service -force

 

7. Use Citrix Studio or powershell to put the old Hypervisorconnection into maintenance mode.

 

If you got lot´s of machines and you are showing the hypervisorconnection column within Director it may be showing the old connection name, it seems like the monitoring database needs some time to get updatet, while I was testing this in a customer environment the monitoring database was still showing the old Hypervisorconnection ID for a few hours.

 

That´s all!!!!

 

Hope this helps

 

Regards

 

Dennis

 

 

[Ray Davis]

Wow man. Thank you.

I'm moving to a new vcenter soon. I will try this first. Much appreciated sir.

[William Fulmer]

Great and timely post. Was actually doing this work this week as well.

 

This also works should you be performing a DR failover for statically assigned machines, say from one cluster of machines to another - irrespective of hypervisor - VMware ESXi (managed by a separate vCenter), Hyper-V Host, using Hyper-V Replication, or Nutanix AHV to another Nutanix cluster.

 

By parsing the 'unknown' machines and then updating the HypervisorConnectionUid, this allows Citrix Studio to properly report Power Management of the machines.

 

 

[Anton Ivanov1709156621]

Thank you @Dennis Reimer great article and worked for me. It's save a lot of my time. I've been thinking to create a new machine catalogs...also it is possible.

 

 

[Domas Civilka]

I was about to go through this process and then saw this post :) Works in 7.15 LTSR.

Thanks Dennis, great stuff. 

[Anton Ivanov1709156621]

I forgot to add which version I've migrated all workers to new vcenter. It's working on 7.6.300 as well.

[Vishnu vardhan]

Hi Guys,

 

we are unable to change the hypervisor connection and getting below error while working with MCS Catalog, can some one confirms, it will only works for non MCS machines/Catalogs

 

"Neither hypervisor connection nor machine ID can be specified for an MCS-provisioned machine"

 

please find the below details:

 

·         Desktop Delivery Controller: 7.6.0.5029

·         Catalog type : Citrix Machine Creation Services

·         VDA: 7.6.0.5026

·         VDA OS: Windows Server 2008 R2 (including all critical updates)

·         Hypervisor: Hyper-V 2012

[CarlStalhood]

For MCS, you should be able to create a new Catalog on the new Hosting Connection and then delete the old Catalog.

 

Why are you running 7.6.0, which is unsupported? The oldest supported is 7.6.300, but that should be updated to 7.6.5000. Or upgrade to 7.15.1000, or newer.

[Anton Ivanov1709156621]

Hi Vishnu,

 

I've never tried to migrate MCS catalogs to new hypervisor connection. I've been thinning it is possible only with a new MCS catalog. This is special service and it is not possible in this way. 

[Vishnu vardhan]

Hi Carl, Antoni

 

Thank you so much for your details/Confirmation

 

Yes, we are planning to migrate the existing infra to 7.15 LTSR coming weeks

[Ray Davis]

I just migrated Xenapp/XenDesktop from 1 vcenter to a completely different vcenter, with different Storage and all.

This script saved much time. Thank you for sharing this.

 

[Mehdi Sasani]

Hi Everyone,

We have recently purchased Nutanix system with AHV. I have Citrix 7.15 LTSR on Hyper-v and planning to migrate to Nutanix. I called Citrix yesterday and they mentioned there is no way to do this and have to build the farm from scratch!

 

Easy for them to say that but moving 2000 people to a new farm is time-consuming. I have two DDC and two storefronts and MCS for machine creation. 

I was wondering if this article is applicable for my scenario or anyone has done this before and what are the steps?

 

I really app[reciate your assistance as I am under pressure to get this migration done asap.

[CarlStalhood]

What kind of VDAs? If non-persistent, then simply migrate your masters to AHV and create new Catalogs.

 

For persistent machines, you'll have to migrate them one at a time. Then add the migrated machines to a Manual catalog.

[Mehdi Sasani]

Thanks Carl, I appreciate your response. my concern is more around DDCs and SFs. I assume migrating them to AHV and installing AHV plugin shouldn't cause any impact on the site?

Also for Netscaler do we need to have a specific version?

[hara prasad nayak]

On 5/8/2019 at 3:15 AM, Carl Stalhood1709151912 said:

What kind of VDAs? If non-persistent, then simply migrate your masters to AHV and create new Catalogs.

 

For persistent machines, you'll have to migrate them one at a time. Then add the migrated machines to a Manual catalog.

Hi Carl,

 

I want to move nearly 500 persistent VDIs from one Vcenter to another. We don't have DRS enabled on the existing Hypervisor cluster. While planning to move the VDI's do I need to plan to get the Hypervisor moved 1st then migrate the associated VDIs ??