Knowledge Base

Removing the virtual machine from the ADAM database

1. Connect to the View ADAM Database. For more information, see Connecting to the View ADAM Database (2012377).
2. Locate the GUID of the virtual machine.
   
   To locate the GUID of the virtual machine:
   
   
   1. Right-click the Connection View ADAM Database [localhost:389], and click New > Query.
   2. Under Root of Search, click Browse.. and select the Servers organizational unit.
   3. Click OK.
   4. In the Query String, paste this search string:
      
      (&(objectClass=pae-VM)(pae-displayname=VirtualMachineName))
      
      Where VirtualMachineName is the name of the virtual machine for which you are trying to locate the GUID. You may use * or ? as wildcards to match multiple desktops.
      
      
   5. Click OK to create the query.
   6. Click the query in the left pane. The virtual machines that match the search are displayed in the right pane.
      
      
3. Record the GUID in cn=<GUID>.

1. Locate the OU=SERVERS container.
2. Locate the corresponding virtual machine's GUID (from above) in the list which can be sorted in ascending or descending order, choose Properties and check the pae-DisplayName attribute to verify the corresponding linked clone virtual machine object.
3. Delete the pae-VM object.

• Check if there are entries under OU=Desktops and OU=Applications in the ADAM database.
• A broken pool that does not contain any desktops can be removed from View Manager by removing the pool entry from both the Server Groups and Applications organizational units. However, removing one entry and not the other from the ADAM database results in the java.lang.nullpointerexception error when attempting to view the pools or desktops inventory in View Manager.

Removing the linked clone references from the View Composer database

1. Open SQL Manager > Databases > View Composer database > Tables.
2. Open the dbo.SVI_VM_NAME table and delete the entire row where the virtual machine is referenced under the NAME column.
3. Open the dbo.SVI_COMPUTER_NAME table and delete the entire row where the virtual machine is referenced under the NAME column.
4. Open the dbo.SVI_SIM_CLONE table, find the virtual machine reference under column VM_NAME and note the ID. If you try to delete this row, it complains about other table dependencies.
5. Open the dbo.SVI_SC_PDISK_INFO table and delete the entire row where dbo. SVI_SIM_CLONE ID is referenced under the PARENT_ID column.
6. Open the dbo.SVI_SC_BASE_DISK_KEYS table and delete the entire row where dbo.SVI_SIM_CLONE ID is referenced under the PARENT_ID column.
7. If the linked clone was in the process of being deployed when a problem occurred, there may be additional references to the clone left in the dbo.SVI_TASK_STATE and dbo.SVI_REQUEST tables:
   
   
   1. Open the dbo.SVI_TASK_STATE table and find the row where dbo.SVI_SIM_CLONE ID is referenced under the SIM_CLONE_ID column. Note the REQUEST_ID in that row.
   2. Open the dbo.SVI_REQUEST table and delete the entire row where dbo.SVI_TASK_STATE REQUEST_ID is referenced.
   3. Delete the entire row from the dbo.SVI_TASK_STATE table.
      
      
8. In the dbo.SVI_SIM_CLONE table, delete the entire row where the virtual machine is referenced.

Removing the virtual machine from Active Directory

1. Log into the Domain Controller as Administrator.
2. Navigate to Start > Administrative Tools > Active Directory Users and Computers.
3. Remove the virtual machine from Computers.

Deleting the virtual machine from vCenter Server

1. Log into vCenter Server using the vSphere Client.
2. Right-click the linked clone virtual machine and click Delete from Disk.