There are two known issues regarding vCenter HA in vSphere 6.7. VMware Engineering is aware is actively working to address these in the future.
The first issue affects some (non-critical) service startup after failover and the second issue affects patching a vCenter HA enabled system to 6.7 U2.
Currently, the first issue requires you to remove vCenter HA, perform a workaround, and re-enabled vCenter HA so my advice to you would be to remove vCenter HA before you begin your update to 6.7 U2 since you’re going to have to remove it post-update anyways.
If you’re already on 6.7 U2 with vCenter HA enabled, you’ll also need to remove vCenter HA to resolve the first issue.
In this step-by-step guide we are going to walkthrough how to converge three vCenter
Server Appliances using external Platform Services Controllers to vCenter Server Appliances with embedded Platform Services Controllers.
Just a quick heads up about Virtual Hardware Version 15 which released as part of vSphere 6.7 Update 2.
Usually new virtual hardware versions only come about with a full major release of vSphere but this is the first time, as far as I can remember, that a new virtual hardware version has been introduced as part of an update release.
The important thing to note about virtual hardware versions is that they do not run on earlier versions of ESXi than the version they first released with.
Virtual hardware version 15 was released with ESXi 6.7 U2, therefore it will not run on any earlier version of ESXi, including ESXi 6.7 GA or 6.7 U1.
vSphere 6.7 U1 saw a CLI based version of the vCenter Server Appliance convergence tool. In vSphere 6.7 U2 we now have all that great functionality built right into the vSphere Client. If you are currently running with external Platform Services Controllers, now has never been a better or easier time to move to embedded.
Over the past 18 months VMware has announced several deprecations with regards to vCenter Server.
The Flash based vSphere Web Client and Windows based vCenter Server were first to see their time expiring and this wasn’t much of a surprise to anyone as the HTML5 based vSphere Client began to approach full functionality and the vCenter Server Appliance having been positioned as the preferred version of vCenter Server.