Decommissioned Horizon Connection Server might leave some clone VMs and or clone templates.
Clean up of old VMware (Omnissa) Horizon VDI environment which might leave some clone templates.
Clone VMs cannot be edited on the vCenter as it will state it is "protected" by "horizon.daas".
VMware vCenter Server 7.x
Before undertaking the fix, please take the essential snapshot of the vCenter (OFFLINE for ELM vCenters and ONLINE for standalone vCenter).
The fix requires the vCenter MOB UI by executing enableMethods using AuthorizationManager against the moRefs to enable the methods on the VMs and folders to be removed as seen in the steps below.
<entity type="ManagedEntity" xsi:type="ManagedObjectReference">[moRef of the locked VM, e.g. vm-609344]</entity>
<entity type="MethodName" xsi:type="string">vim.VirtualMachine.unregister</entity>
<entity type="MethodName" xsi:type="string">vim.VirtualMachine.powerOff</entity>
<entity type="MethodName" xsi:type="string">vim.VirtualMachine.powerOn</entity>
<entity type="MethodName" xsi:type="string">vim.ManagedEntity.destroy</entity>
For the ClonePrep folders that are also locked, the process is similar:
<entity type="ManagedEntity" xsi:type="ManagedObjectReference">[moRef of the folder ID, e.g. group-v618248]</entity>
<entity type="MethodName" xsi:type="string">vim.ManagedEntity.destroy</entity>
<entity type="MethodName" xsi:type="string">vim.Folder.unregisterAndDestroy</entity>