During a new pool creation, an administrator notices that the virtual machines are stuck in the Provisioning state during cloning.
What is the most effective way to correct this issue?
A. Delete the virtual machines and clone them again.
B. Change the snapshot on the pool to a newly-created one.
C. Disable the pool, save the changes, then enable the pool again.
D. Use vdmadmin -v to delete the stuck virtual machines.
vdmadmin -V
Allows data to be recovered from a local desktop by decrypting its virtual machine. See Decrypting the Virtual Machine of a Local Desktop Using the ‑V Option.
Unlocks or locks virtual machines including local desktops and View Transfer Server instances. See Unlocking or Locking Virtual Machines Using the ‑V Option.
Answer D is wrong
Apologies….I am thinking it is A again as digging deeper on this, vdmadmin -V doesn’t “delete” anything, it just unlocks machines which are stuck. This is just a badly worded question.
I disagree. I believe it is D. If some of the machines were provisioned properly, I can see A being the answer. It is clearly stated this is a new pool and the machines are “stuck” in a provisioning state which is what D would help with.
A is correct.
https://docs.vmware.com/en/VMware-Horizon-7/7.3/horizon-virtual-desktops/GUID-400B0BBA-5C9B-4FAC-922F-DEBAB6543825.html