Could you please clone the base VM and assign a different port group and then take a new snapshot of the base image and publish the pool.
We just upgraded to 8 (2111) from 7.10 and getting the same errors on all the pools on all available vm.
Was there a recent migration of dvS from different vCenter or switch with "Preserve original distributed switch and port group identifiers " option enabled?
Quick fix would be re-align the new dvportgroup for golden image
There was a migration to a new vcenter yes. I can assume "Preserve original distributed switch and port group identifiers " option was enabled as that is what I am seeing it default to. The Gold image was built after the migration though.
How do I "re-align the new dvportgroup" for a vm?
Thanks again for all the assistance!
forgot to say what is the not quick fix to fix it permanently.
so you have the old and new vcenter both setup in horizon?
Could you please clone the base VM and assign a different port group and then take a new snapshot of the base image and publish the pool.
Change the network in your original golden image
It appears to be a "known bug" between VMware Horizon Connection Server 2111 and VMC on AWS.
Work around is to configure desktop pool network to use the same as "golden image" (parent VM/snapshot)
There's an update test build from VMware support that fixes this issue.
sjesse: no the migration was months ago, before we even had horizon. the old vcenter has already been decommissioned and deleted.
kvw2130: that worked! I created a new port-group on the existing distributed switch, cloned it with the new port-group and it deployed. So what can be done about the existing port-groups? everything is connected to those port-groups.
siglert: I did not try your solution since kvm's worked.
Taangy,
Unfortunately I don't know if that applies to me. our environment is on prem. It did not matter if I used the gold images network or another. it was always the same error.