pieterjanheyse
Enthusiast
Enthusiast

Unable to create desktop pools after update

After upgrading our Horizon platform to the lastest version (2212), we are now unable to make desktop pools. We're getting the following error on the desktop pool page:
 
Error during Provisioning Cloning of VM 1-vd-a-w11-001 has failed: Fault type is UNKNOWN_FAULT_FATAL - Please check the KMServers. None is available.
 
And in the events we see:
 
Provisioning error occurred for Machine 1-vd-a-w11-001: Resync operation failed.
 
Any ideas?
Reply
0 Kudos
Jubish-Jose
Hot Shot
Hot Shot

Possibly an issue with TPM. Windows 11 requires vTPM on the VMs and we also need to add Key Provider on vCenter. Please see https://core.vmware.com/resource/windows-11-support-vsphere#section1 


-- If you find this reply helpful, please consider accepting it as a solution.
Reply
0 Kudos
pieterjanheyse
Enthusiast
Enthusiast

Thanks for the reply. 

There was indeed no default key provider set. But I am a bit confused on how to set this up.

When adding a standard key provider, tis this connected to the KMS server runnig the volume activation services?

We have a desktop pool with MAK key's that work fine (the desktops are dedicated). I was told when using a floating desktop pool it is not reccomended to use MAK. 

Reply
0 Kudos
adanmohamed2018
Contributor
Contributor

The error message suggests that there may be an issue with the Horizon Connection Server or the vCenter Server. Here are some steps you can take to troubleshoot the issue:

  1. Check the Horizon Connection Server logs: Go to the Horizon Connection Server that is managing the desktop pool, and check the logs located in C:\ProgramData\VMware\VDM\logs\debug. Look for any errors or warnings related to the desktop pool provisioning process.

  2. Check the vCenter Server logs: Go to the vCenter Server that manages the ESXi host, and check the logs located in /var/log/vmware/vpxd. Look for any errors or warnings related to the desktop pool provisioning process.

  3. Verify vCenter Server availability: Make sure that the vCenter Server is online and reachable. You can try to ping the vCenter Server from the Horizon Connection Server to verify connectivity.

  4. Verify vCenter Server credentials: Make sure that the vCenter Server credentials provided in the Horizon Connection Server configuration are correct and have sufficient permissions to manage the ESXi host.

  5. Verify the vSphere API endpoint: Verify that the vSphere API endpoint is accessible from the Horizon Connection Server. You can test this by using a web browser to access the following URL: https://<vcenter-server>/mob. If you are able to access the URL and see a web page, then the vSphere API endpoint is accessible.

  6. Restart the Horizon Connection Server: Try restarting the Horizon Connection Server to see if it resolves the issue.

  7. Contact VMware support: If the issue persists after trying the above steps, contact VMware support for further assistance.

Reply
0 Kudos
yukiafronia
Enthusiast
Enthusiast

Is the cloning method correct for instant cloning?

What did you do before the error occurred, like Windows update on the master VM?

Which button do I select in the Horizon Console to reproduce the error?

If you can reproduce the error, please get the date and time the error occurred and the debug log from C:\ProgramData\VMware\VDM\logs\debug

If you have time, I will take a look.

Reply
0 Kudos
Jubish-Jose
Hot Shot
Hot Shot

The Key Management Server is used for encrypting the VM when Windows 11 is used. No need to set up activation etc. You can add a dummy KMS from the vSpehre console. It just checks whether there is a KMS setup. Check this doc where it shows the steps in a video: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-78DD547A-6FFC-49F... 


-- If you find this reply helpful, please consider accepting it as a solution.
Reply
0 Kudos