I am able to create a new pool from my snapshot, but if i use the same snapshot and try to publish to existing pool, it fails. So strange. Any ideas?
thanks
Open a ticket with support if you have it, because I'm pretty sure you need to restart your connection servers and vcenter, I've seen that before, but without looking at the logs I can't confirm it for sure.
basically the cached information about vcenter is different then what vcenter actually has, and this clears it and rebuilds it. Depending on how your users connect there probably won't be any interruptions to existing connections, just any new ones while the servers are restarting
I will give it a try. Thanks.
This fix worked for me... for a day. lol. back to the same issue again. I opened a ticket with support. Will update this when they call me.
thanks for the help.
Check resources usuage on your connection servers, do they look like they are getting close to running our of memory or cpu? Also check that the time is correct, but you probably need support to scour the logs if a restart only worked for day.
As a test I cloned my master VM and created a new pool from that image. I then made some changes (windows updates) and snapped it. Used the new snapshot to publish and it went without an a problem. The issue seems to be the one master image I have. That is the one that is failing to re-publish. Think I might just remove tools and agent from it and re-install again.
If you did a direct clone of your parent/master image and a new one worked, just do a push with the new parent, you don't need to use the same vm. What I do is have one I label as "golden" do windows updates and then clone separate parent images for each desktop pool and create one snapshot and use those separate vms for all the parent vms. Its an extra few steps but it works better in my opinion then having one parent image for everything, you still only update the one. Its a VMware practice as well, its at the end of the following article
Creating an Optimized Windows Image for a VMware Horizon Virtual Desktop | VMware
I can't do that because one Master/Parent image has GPU drivers and the other does not. Other than that they are identical.
Try just cloning the one with the GPU drivers into a new one though, you could be right and something is wrong with that specific vm.
so I cloned the clone (if that make sense) and used it to push the image. So far so good. I wont know until I make a change, snap it and then re-push. But it looks promising. Also i noticed that the new image that was cloned boots MUCH faster than the original. I have a very good feeling that my original master image was messed up somehow.