XenDesktop on vSphere error : The Hypervisor could not be contacted

Scenario
xd2
For the first time when you run the Site Configuration wizard in the Desktop Studio management console, at a point where you need to set the Host Connection, you provide your hypervisor information (in this case, it is VMware vSphere) such as Host Connection as https://<vCenter FQDN address>/sdk followed by its administrative credentials and hit Next you get the error “The Hypervisor could not be contacted”.
 Cause
Generally, this is a known issue and occurs when the vCenter Server does not have a valid SSL certificate that means it uses a default SSL certificate. The XenDesktop/Desktop Studio fails to identify the vCenter/SDK and thus throws the error
Workaround
Connect to the Xendesktop Controller machine using RDP, open the web browser, type in the vCenter FQDN/IP address, you’ll get a SSL certificate warning, accept it, and then near the IE address bar you’ll see the invalid SSL certificate, Import the certificate as shown below in screenshots into the physical store of the certificate.
Open vCenter IP/FQDN address in a browser
 
 
xd3 
 
 
 
 
 
 
 
 
 
 
Click on the red cross beside the address bar and click on the Certificate Invalid
 
 
xd4
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
click View Certificates
xd5 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Click on Install Certificate
xd6
 
 
 
 
 
 
 
 
Hit Next, Select Place all certificates in the following store.
Click Browse and select certificate store
xd7
 
 
 
 
 
 
 
 
 
Scroll down to the bottom, tick mark the check box “Show physical stores”
xd8
 
 
 
 
 
 
 
 
Expand Trusted People > select Local Computer  or Enterprise(if server 2012) > click OK
xd9
xs2 

 
  
 
 
 
 
 
 
 
Back to the initial window, click Next
xd10 
 
 
 
 
 
 
click Finish
 
xd11You will see the message “The import was successful”
xd12
 
 
 
 
 
 
 
To verify, open Microsoft management console (MMC), Add the Certificates snap-in  navigate to the Trusted certificates and you can see the vCenter default certificate. 
 
Now at this stage, return to your Controller/Desktop Studio and re-run the Site Configuration wizard and it should now connect to the vSphere hypervisor.
 
Hope this helps…

About cloudray

Predominantly based around Virtualization, but will include other technology related information and anything else I find interesting and feel the need to share with you. I also use this Blog as both a place to store useful information that I think that will come in handy to me at some point in the future, and also a place to help aid my learning. I find a great way to learn about something is to research about it and then write it up in my own words. I'm Pushpal Ray, from India. As a certified VCP3/4/5 professional, I am currently working as an Independent Consultant. Over 10 years of IT-industry experience, currently focused around the Desktop Virtualization(End-User Computing). I also have extensive experience in Windows Administration, Datacenter Migration, Workload profiling & benchmarking. At my leisure, I enjoy hiking, running, photography, spend hours in my fav coffee shop & spend quality time with my wife. Occasionally, catch up with few friends for a drink!
This entry was posted in Desktop Virtualization, Enterprise Virtualization, vSphere, XenDesktop and tagged , . Bookmark the permalink.

3 Responses to XenDesktop on vSphere error : The Hypervisor could not be contacted

  1. Robert Sheasby says:

    Can xendesktop connect to two different vSphere servers? I have two clusters on different servers using two instances of vSphere server to control each. Reason being different versions of VMware 4.1 and 5.1 doing a migration.

  2. Max says:

    This article helped me past the certificate error perfectly, thanks

  3. Pingback: Xendesktop 7.5 – cannot connect to the vcenter server due to a certificate error | cloudray

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s