Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager 4.5 and later (2015112)

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

Purpose

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).

Cause

This issue occurs if a table in the database contains incorrect data. It can also occur if the virtual machine name has been manually modified in vCenter Server after the pool has been created, causing View Composer and vCenter Server to refer to the same virtual machine with different names.

Resolution

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.

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

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=TheViewComposerServerURL

where:

  • VMname is the name of the virtual machine to remove.
  • TheLocalAdminUser is the name of the user who is part of the local administrator group. The default value is Administrator.
  • TheLocalAdminPassword is the password of the administrator used to connect to the View Composer server.
  • TheViewComposerServerUrl is the View Composer server URL. The default value is https://localhost:18443/SviService/v2_0.

Note: The VmName and 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.

  1. Copy the virtual machine names to a text file and save it as desktops.txt to the same directory in which SviConfig is located.
  2. Copy this into a new text document:

    FOR /F %%A in (desktops.txt) DO sviconfig -operation=removesviclone -vmname=%%A -adminuser=username -adminpassword=password

    where username is the name of the user who is part of the local administrator group and password is the password of the administrator.

  3. Save the text file as RemoveDesktops.bat.
  4. Execute RemoveDesktops.bat.
If the .vmx file of the linked clone is damaged or missing, vCenter Server cannot delete the virtual machine. In this case, right-click the virtual machine in vCenter Server and click Remove from Inventory.

After running the SviConfig command and verifying that the virtual machine is deleted from vCenter Server:

See Also

Update History

03/22/2012 - Added link to article 1008658 07/19/2012 - Updated Product Versions to include 5.1 07/25/2012 - Updated title to include View Composer database

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 7 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 7 Ratings
Actions
KB: