Email to let us know when you will be upgrading and certifying your plug-ins.Review document “ Upgrading your plug-in to maintain compatibility with vSphere 6.7“.
Ensure that you test and update your plug-in now. Our joint customers are demanding vSphere Web Client and vSphere Client plug-ins that are compatible with vSphere 6.7. If your plug-in is incompatible, vSphere 6.7 will display the plug-ins as “Incompatible” in the vSphere Client and vSphere Web Client. Please refer to the document “ Upgrading your plug-in to maintain compatibility with vSphere 6.7” for more details. You must test to ensure that your plug-in(s) installs and functions successfully with vSphere 6.7 for both clients.
The workaround and express patch mentioned above DO NOT address compatibility issues with partner plug-ins that use the classes and libraries missing in the vSphere Web Client (Flash). Once the patch is installed, customers will no longer have to run the script that disables plug-ins that are not certified to work with vSphere 6.7. VMware will fix the product issue in an Express Patch to address the Web Client hang.
This incompatibility results in IMMEDIATE impact to our joint customers when they upgrade to vSphere 6.7 and the vSphere 6.7 Web Client. If you used any of these classes or libraries, your plug-in(s) are now incompatible with vSphere 6.7. The newer versions of Virgo, Spring and Tomcat remove some previously deprecated classes and libraries. In the vSphere 6.7 release, the Virgo server (and as a result Spring and Tomcat) was updated to version 3.7.2 to address security vulnerabilities. Upgrade Your Plug-Ins to Maintain Compatibility with vSphere 6.7” For additional details, be sure to attend the upcoming TAP webinar session: This blog will explain the compatibility concerns associated with the vSphere 6.7 release, and how partners can ensure compatibility for customers using vSphere 6.7.