The View Composer brings the linked clone technology to the View solution. Due to that the environment will need less storage for the virtual desktops. Form a technical View the Parent VM and the Snapshot will be combined as one VM or Entity. The virtual machine will be protected from deleting in the vCenter due to different linked clones a referencing to it.
The right way to manage the VM’s is not the vCenter, it’s the View manager/View Composer. If a linked clone is created, recomposed or deleteted this information will be set in the Entity. Rarely it is possible that something fails and there is a need to manually delete the clone from the vCenter. Due to the protection it is not possible to directly deletete the VM even not as Administartor. The View Composer comes with a tool called SVICONFIG.EXE which can be found in the folder: "C:\Program Files\VMware View Composer\SviConfig.exe". You’ll need to use this tool to unlock the VM’s for deleting.
The following steps describe the unlocking of the main directory and the contained virtual machines.
- On the vCenter/View Composer server: Start / Run../ CMD
- Change to directory "C:\Program Files\VMware\ VMware View Composer"
- Execute the following command (change the vCenter URL)
*“SviConfig -operation=UnprotectEntity -VcUrl=https://my.vc/sdk
* -Username=admin -Password=pass -InventoryPath="/My*
* Datacenter/vm/MyReplicaFolder" -Recursive=True*”*
If the process was sucessfull a message stating that is given. After that it’s possible to delete the orphaned entries in the vCenter.