Release date: June 27th 2022
Welcome to my VMware Horizon series. At a customer, I recently ran into a problem with pushing a new golden image and snapshot to the Desktop Pool. The error-message was: “Error during Provisioning Initial publish failed: Fault type is VC_FAULT_FATAL – javax.xml.ws.soap.SOAPFaultException fault was thrown by the VC server: https://xxx.xxx.xxx:443/sdk. Error: The object ‘vim.dvs.DistributedVirtualPortgroup:dvportgroup-xxxx’ has already been deleted or has not been completely created::dvportgroup-xxxx not found“
While creating the golden image, everything looked good, the same distributed port group was used and network connectivity was excellent. However, when trying to publish this through the Connection Server, the error above appeared and provisioning was disabled. After some troubleshooting, we found that this distributed port group was visible on the vCenter server, but not on the ESXi hosts. To work around this, we created a new port group in vSphere, same VLAN as the original, cloned the golden image vm and change network to the new port group, which solved the problem. Next, we deleted the original distributed port group and renamed the new port group to the original port groups name. Tested again and everything worked without issues.
So, what could be the culprit here? Most likely, somewhere in the past, someone had done a dvS migration from a different vCenter and enabled the option: “Preserve original distributed switch and port group identifiers”. Hopefully, this can be helpful for anyone else out there that runs into this issue.
VMware Horizon planning, deployment etc.
Disclaimer: Every tips/tricks/posting I have published here, is tried and tested in different it-solutions. It is not guaranteed to work everywhere, but is meant as a tip for other users out there. Remember, Google is your friend and don’t be afraid to steal with pride! Feel free to comment below as needed.
bjosoren's IT-Tech blog 