I did a huge rebalance after adding new datastores and all went well... until the last few VM's It appears the account that View uses to communicate with the Composer database and vCenter Server was locked out (another story) so several VM's were partially rebalanced which caused them to be non-operational and couldn't delete them through the View Connection Server Admin console.
I removed the VM's from the ADAM database with ADSI Edit and removed the remnants from the Composer Database (the manual method). I removed the VM's from Active Directory and from vCenter Server using the vSphere Client and by browsing the datastores when needed.
When I re-enabled the pool to provision, all the VM's were recreated but one VM number was skipped. The pool is for 60 Win7VM's but VM7 isn't being recreated, it made a VM61 to meet the minimum of 60.
How can I force it to make VM7? We are required to list all the computer names in a security profile and a gap in numbering will be a pain in the butt. Not to mention my OCD will drive me crazy! 