I am trying to deploy some windows 7 desktops into a auto deploy pool. I am running esxi 5 and vmView 5. Once the clone is created the vm does power up, but it sticks at customizing. vCenter sees the new name for the VM, but inside the VM it still has the name of the base (template) vm. It is pulling DHCP and does appear to be able to resolve the ip of the view manager server, nslookup worked just fine. Where else do I need to look to find the solution to this problem?
There are composer logs that would help diagnose the issue.
Also, after a while does it timeout (common error being "failed to join domain")
When you updated to View 5 did you make sure to update vComposer, vComposer needs to be version 2.7 to work properly on View5.
I get a Customization operation timed out.
I am going to try to turn on the extended logging and try again.
Check whether enough storage is available for the pool. Mostly long customizing state is due to insufficient disk space. Try creating a pool with the same configuration with less quantity like 2 or 3 desktops.
What is the error that shows up in View Administrator page (Any error number ?)
Check whether the parent VM has kms configured, and configured key management server is reachable.
Also refer the checklist @ Common errors with SVI Pools and View Composer