Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 3.x and 4.0.x
Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 3.x and 4.0.x Symptoms 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 Cause This issue occurs when: a table in the database contains incorrect data. the virtual machine name has been changed in the vCenter Server manually after the pool has been created, causing View Composer and vCenter Server to refer to the same virtual machine with different names. Resolution This solution applies to VMware View 3.x and 4.0.x. For View 4.5 and later, see Manually deleting linked clones or stale desktop entries from VMware Vie...