In some cases you may have a pending VMware Horizon View pool deletion task that does not finish for several reasons: usually when you have modify or delete some VM’s pool directly from the VMware vCenter Server instead from the View Manager.
In those cases you will not be able to remove those pool anymore and probably you will not able to build VM with the same pattern.
You can fix this issue manually using those VMware KB: Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 4.5 and later (2015112) or Manually deleting linked clones or stale virtual desktop entries from VMware View Manager 3.x and 4.0 (1008658).
Basically first, on the View Connection Server you have to edit the LDAP structure with ADSI edit (in a similar way as used to fix the vCenter Plugins list for removing the Enterprise Converter). Connection data are:
- Select Select or type a Distinguished Name or Naming Context.
- In the field below, type dc=vdi,dc=vmware,dc=int
- Select Select or type a domain or server.
- In the field below, type localhost
Then you have to work on your Composer Server in order to fix also its database, otherwise you will no able to re-use the previous VM names. For this purpose you can use the command line tool:
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 isAdministrator
.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 ishttps://localhost:18443/SviService/v2_0
.
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