Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager 4.5 and later (2015112)
- You cannot provision a linked clone desktop pool
- You see the error:
Desktop Composer Fault: 'Virtual Machine with Input Specification already exists'
- Provisioning a linked clone desktop pool fails with the error:
Virtual machine with Input Specification already exists
- The Connection Server shows that linked clone virtual machines are stuck in a Deleting state
This article applies to VMware View 4.5 and later. For View 3.x and 4.0.x, see Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 3.x and 4.0.x (1008658).
If the virtual machine was renamed through the vSphere Client after the pool was provisioned, you can resolve the issue by renaming the virtual machine to its original deployed name.
To resolve database inconsistency, you must delete the virtual machine references from the View Composer database and from the ADAM database so the tables regenerate properly. Then, ensure that no pool desktop names are changed through vCenter Server after the pool is created.
Warning: Before you delete entries from either database, take a complete backup of ADAM and the Composer database and disable provisioning for the pool in View Manager. For more information, see Performing an end-to-end backup and restore for View Manager (1008046).
Removing the linked clone references from the View Composer database
For VMware View Manager 5.1 and later, TheViewComposerServerUrl is the View Composer server URL. The default value is https://localhost:18443/SviService/v3_0.
SviConfig RemoveSviClone command to remove these items:
- The linked clone database entries from the View Composer database
- The linked clone machine account from Active Directory
- The linked clone virtual machine from vCenter Server
SviConfig is located on vCenter Server hosting View Composer at:
- 32bit servers:
Install_drive\Program Files\VMware\VMware View Composer
- 64bit servers:
Install_drive\Program Files (x86)\VMware\VMware View Composer
Before you remove the linked clone data, make sure that the View Composer service is running. On the View Composer computer, run the
SviConfig RemoveSviClone command. The command looks similar to:
SviConfig -operation=RemoveSviClone -VmName=VMname -AdminUser=TheLocalAdminUser -AdminPassword=TheLocalAdminPassword -ServerUrl=TheViewComposerServerURLwhere:
VMnameis the name of the virtual machine to remove.
TheLocalAdminUseris the name of the user who is part of the local administrator group. The default value is
TheLocalAdminPasswordis the password of the administrator used to connect to the View Composer server.
TheViewComposerServerUrlis the View Composer server URL. The default value is
AdminPassword switches are required.
If you need to remove a large number of virtual machines you can create a text file with each virtual machines name and a batch file to execute the sviconfig command against each.
- Copy the virtual machine names to a text file and save it as
desktops.txtto the same directory in which SviConfig is located.
- Copy this into a new text document:
FOR /F %%A in (desktops.txt) DO sviconfig -operation=removesviclone -vmname=%%A -adminuser=username -adminpassword=password
usernameis the name of the user who is part of the local administrator group and
passwordis the password of the administrator.
- Save the text file as
After running the SviConfig command and verifying that the virtual machine is deleted from vCenter Server:
- Click the virtual machine in the View Administration console and click Remove.
- If this does not remove the virtual machine from View, you must remove the virtual machine from the ADAM database. For more information, see Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 3.x and 4.0.x (1008658).
- Performing an end-to-end backup and restore for View Manager
- Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 3.x and 4.0.x
- Connecting to the View ADAM Database