Under certain conditions, linked-clone data in View, View Composer, and vCenter Server might get out of synchronization, and you might be unable to provision or delete linked-clone machines.
If the virtual machine name was renamed in vSphere Client after the desktop pool was provisioned, try renaming the virtual machine to the name that was used when it was deployed in View.
If other database information is inconsistent, use the 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
The SviConfig utility is located with the View Composer application. The default path is C:\Program Files (x86)\VMware\VMware View Composer\sviconfig.exe.
Only experienced View Composer administrators should use the SviConfig utility. This utility is intended to resolve issues relating to the View Composer service.
Take these steps:
Verify that the View Composer service is running.
From a Windows command prompt on the View Composer computer, run the SviConfig RemoveSviClone command in the following form:
sviconfig -operation=removesviclone -VmName=virtual machine name [-AdminUser=local administrator username] -AdminPassword=local administrator password [-ServerUrl=View Composer server URL]
sviconfig -operation=removesviclone -vmname=MyLinkedClone -adminuser=Admin -adminpassword=Pass -serverurl=ViewComposerURL
The VmName and AdminPassword parameters are required. The default value of the AdminUser parameter is Administrator. The default value of the ServerURL parameter is https://localhost:18443/SviService/v2_0
For more information about removing virtual machine information from View LDAP, see VMware Knowledge Base article 2015112: Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager and VMware Horizon View.