In View Administrator, linked-clone desktops are stuck in a Deleting state. You cannot restart the Delete command in View Administrator because the desktops are already in the Deleting state.

Cause

This issue occurs if the View Composer database contains information about linked clones that is inconsistent with the information in View LDAP, Active Directory, or vCenter Server. Several situations can cause this inconsistency:

■

The linked-clone virtual machine name is changed manually in vCenter Server after the pool was created, causing View Composer and vCenter Server refer to the same virtual machine with different names.

■

A storage failure or manual operation causes the virtual machine to be deleted from vCenter Server. The linked-clone desktop data still exists in the View Composer database, View LDAP, and Active Directory.

■

While a pool is being deleted from View Administrator, a networking or other failure leaves the virtual machine in vCenter Server.

Solution

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 on the computer on which View Composer is installed in the following location:

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