5.2

Table 16-2. View Composer Provisioning Errors
(Continued)
Error Description
15 The computer name that View Composer read from configuration-policy file does not match the current
system name after the linked clone is initially powered on.
16 The View Composer agent did not start because the volume license for the guest OS was not activated.
17 The View Composer agent did not start. The agent timed out while waiting for Sysprep to start.
18 The View Composer agent failed to join the linked-clone virtual machine to a domain during customization.
19 The View Composer agent failed to execute a post-synchronization script.
20 The View Composer agent failed to handle a machine password synchronization event.
This error might be transient. If the linked clone joins the domain, the password is fine.
If the clone fails to join the domain, restart the operation you performed before the error occurred. If you
restarted the clone, restart it again. If you refreshed the clone, refresh it again. If the clone still fails to join
the domain, recompose the clone.
Removing Orphaned or Deleted Linked Clones
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 desktops.
Problem
n
You cannot provision a linked-clone desktop pool.
n
Provisioning linked-clone desktops fails, and the following error occurs: Virtual machine with Input
Specification already exists
n
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:
n
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.
n
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.
n
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:
n
The linked clone database entries from the View Composer database
n
The linked clone machine account from Active Directory
n
The linked clone virtual machine from vCenter Server
Chapter 16 Troubleshooting View Components
VMware, Inc. 401