In a customer environment we upgraded to XenDesktop 7.9 and added two new Desktop Controller in order to change the OS from Windows Server 2008R2 to Windows Server 2012R2. After some weeks the customer removed the old Controller from the site and after this we saw several issues regrading the hypervisor connections, for example when we tried to add VMs to catalog:








If you had a closer look to the error for example on the machine catalog directly you will notice that the controller in unable to establish a TLS/SSL connection to the hypervisor:










If you scroll down you will see the connections should be initiated by on of the old controller, which doesn’t exist on the environment anymore. The reason for this an option in the hypervisor connection called „Preferred Controller“:






This can be changed in a simple way:

Load the connection into a powershell variable:

$con = Get-BrokerHypervisorConnection -PreferredController "DOMAIN\OLDCONTROLLER" -Name "VMware"

Change the Preferred Controller to you new value:

Set-BrokerHypervisorConnection $con -PreferredController "DOMAIN\NEWCONTROLLER"


Leave a Comment

Diese Website verwendet Akismet, um Spam zu reduzieren. Erfahre mehr darüber, wie deine Kommentardaten verarbeitet werden.