Introduction
In this article I will describe how to remove Instant Clone objects created in VMware Horizon DaaS from your vCenter Server.
I had to do this because I (on one of those famous rough Monday mornings 😉 ) deleted one of my demo tenants in VMware Horizon DaaS without properly clean the tenant first.
Note to self: kill the VDI’s first, than remove the images, etc. properly and THAN delete the tenant!
Unfortunately this wasn’t a very clever move because you can’t delete the remaining objects afterwards due to a lock in the database:
This can be avoided by changing the capacity of the desktop pools to 0 and convert/delete the images before you delete your tenant from the Horizon DaaS Service center.
| Beware! If these actions are outside your comfort zone, reach out to the VMware Support team to assist you with this. When you delete the wrong objects, there will be consequences. |
Preparation
First, you need gather a list of cp-xxx objects you want to remove from the vCenter Server. I did this by listing all the VM objects sitting in the remaining desktop VLAN of my deleted tenant.
Now, export them to a Excel/CSV file.
In the second part of this article we will add a column to the file, so a clear overview is advised.
You can use the Data > “Text to columns” option in Excel to make the list more clear to read. My list looked like this:
Log on to the vCenter Server MOB.
To do this, type the following behind the FQDN of your vCenter Server: /mob/?vmodl=1.
Example: https://vcsa-fqdn/mob/?vmodl=1
After you logged on (use the administrator@vsphere.local account, or equal privileges) to the MOB, Browse to Content.
![vCenter Managed Object Browser > rootFolder > vim.Folder” class=”wp-image-179″/><figcaption>vCenter Managed Object Browser > rootFolder > vim.Folder</figcaption></figure>
<p>We need to navigate to the datacenter where your cp-xxx objects are located: <strong>Navigate </strong>to childEntity > vim.ManagedEntity[] > datacenter-21 (<em>Name of your DataCenter</em>)</p>
<figure class=](https://www.vblog.nl/wp-content/uploads/2018/12/image-19.png)
![vCenter Managed Object Browser > childEntity > vim.ManagedEntity” class=”wp-image-180″/><figcaption>vCenter Managed Object Browser > childEntity > vim.ManagedEntity</figcaption></figure>
<p>Next step is to <strong>find </strong>the <strong>datastore </strong>where the cp-xxx objects are stored.<br>In my situation it’s a NFS datastore: vim.Datastore[] > datastore-56</p>
<figure class=](https://www.vblog.nl/wp-content/uploads/2018/12/image-20.png)
![vCenter Managed Object Browser > datastore > vim.Datastore” class=”wp-image-181″/><figcaption>vCenter Managed Object Browser > datastore > vim.Datastore</figcaption></figure>
<p>Once there, browse to the vm – vim.VirtualMachine[] row and choose more..</p>
<figure class=](https://www.vblog.nl/wp-content/uploads/2018/12/image-21.png)
Remove the lock from the Instant Clone cp-xxx objects
In the following steps we will use MOB to remove the lock from Instant Clone cp-xxx objects.
Log on to the vCenter Server MOB.
To do this, type the following behind the FQDN of your vCenter Server: /mob/?vmodl=1.
Example: https://vcsa-fqdn/mob/?vmodl=1
After you logged on (use the administrator@vsphere.local account, or equal privileges) to the MOB, Browse to Content.
![vCenter Managed Object Browser > authorizationManager > ManagedObjectReference:AuthorizationManager” class=”wp-image-188″/><figcaption>vCenter Managed Object Browser > authorizationManager > ManagedObjectReference:AuthorizationManager</figcaption></figure>
<p><strong><u>If one of these options is missing, close all your browser windows and retry OR open an incongnito window.</u></strong></p>
<p><strong>Navigate </strong>to vim.AuthorizationManager.EntityDisabledMethodInfo[] > enableMethods, A new browser tab will open with three fields: <strong>Entity</strong>, <strong>Method </strong>and <strong>SourceID</strong>.</p>
<figure class=](https://www.vblog.nl/wp-content/uploads/2018/12/image-27.png)
![vCenter Managed Object Browser > authorizationManager > ManagedObjectReference:AuthorizationManager” class=”wp-image-189″/><figcaption>vCenter Managed Object Browser > authorizationManager > ManagedObjectReference:AuthorizationManager</figcaption></figure>
<p>We go back to the <strong>Excel </strong>list with the locked cp-xxx objects and the vm-xxxx <strong>numbers correlated</strong> to the them. We need those vm-xxxx numbers in the steps below.</p>
<p><strong>Copy/Paste</strong> the XML content from the first code block below to the entity > vim.ManagedEntity[] value.</p>
<!-- Crayon Syntax Highlighter v_2.7.2_beta -->
<div id=](https://www.vblog.nl/wp-content/uploads/2018/12/image-28.png)
|
1 2 3 4 5 6 7 |
<!--array start --> <entity type="ManagedEntity" xsi:type="ManagedObjectReference">vm-0001</entity> <entity type="ManagedEntity" xsi:type="ManagedObjectReference">vm-0002</entity> <entity type="ManagedEntity" xsi:type="ManagedObjectReference">vm-0003</entity> <entity type="ManagedEntity" xsi:type="ManagedObjectReference">vm-0004</entity> <entity type="ManagedEntity" xsi:type="ManagedObjectReference">vm-0005</entity> <!--array end --> |
One comment