[Solved] Pool provisioning fails after upgrade VMware Horizon 7 version 7.5.x

Pool provisioning operations are not initiated after doing view upgrade for VMware Horizon 7 version 7.5.x due to the stale jars left behind after upgrade. We see the error messages Pool Info currently inconsistent, skipping determineActions for pool in CS logs at C:\ProgramData\VMware\VDM\logs. Execute below steps on the brokers one at a time and repeat the steps for the other brokers in the cluster.


Step 1: Uninstall broker and adam db.

Step 2: Ensure that all the view folders and jars are deleted.

Step 3: Perform fresh installation of the broker as replica pointing to another standard server.


VMware Knowledge Base: Pool provisioning fails after upgrade (59808)

Published by Thomas Apel

, a dynamic and self-motivated information technology architect, with a thorough knowledge of all facets pertaining to system and network infrastructure design, implementation and administration. I enjoy the technical writing process and answering readers' comments included.