Hello,
I have created a fresh View environment that I'm having some difficulties with. I can successfully create a desktop pool but after View clones from the Parent VM it deletes the new VMs right after they finish the clone operation. So, what happens is the Parent VM is cloned, tagged, and then the new VM is deleted.
Environment details:
2 ESX 4.0 Update 2 hosts
1 Physical vCenter 4.0 Update 2 server, also running View Composer
1 Physical View 4.5 Manager Server
vCenter and View Manager are both configured to use an external SQL DB
No Event DB configured
Any ideas? I probably just missed a config step somewhere.
The pool should display the reason why it disabled provisioning.
Sent from my iPhone
What are your pool settings? Specifically look at the Min number of desktops, Max number of Desktops, and Spare Desktops. If Min and Max are set to 0, this behavior will occur.
Thanks for the reply. I've tried a few different pool settings with different numbers in there. If I set the pool to provision them up-front or as needed it still happens.
Any other ideas? I'm scratching my head with this one.
Does the pool disable provisioning after this? Do you see any error messages in the events section of View Admin? Also be helpful to check the the composer logs and see if you can find any error messages when the event happens.
The pool does disable provisioning after this happens. I don't have an Event DB configured in View and won't be able to set one up for a little while. Is there somewhere else I can see what's happening?
The pool should display the reason why it disabled provisioning.
Sent from my iPhone
You are right! It states that "Administrator account used for QuickPrep does not have sufficient permissions." Thanks for your continued help!
Check out this KB on creating the Quick Prep account, http://kb.vmware.com/kb/1025834.
hi..
Were you able to fix this. I am experiencing the same kind of issue.
Running VMView 7.1.0 and requires to deploy a new pool with new VDI of WIndows 10... Am using an AD user with Full permission on the AD container.
But it looks like the cloning is going on, but straight after it compeltes the cloning all VDI clients and replicats gets deleted automatically.
Appreciate if anyone can share me the root cause and fix