Skip navigation

Hello User,


Have you upgraded your windows based vCenter to 6.7 and not able to see update manager plugin in the web client ?


The chances are high that you may face this issue especially when running vCenter on Windows version.


Note : The update manager plugin will not be available for HTML client for windows vCenter 6.7 however you should still be able to access it via the Flash client.


The following article helps to get the update manager plugin visible to the flash client in case if it is showing errors as below screenshot"


to write kb.JPG


To isolate this issue further restart only the web client service and navigate to C:/ProgramData/VMware/vCenterServer/logs/vsphere-client/logs/vsphere_client_virgo.log

Search for term "vcIntegrity" from the bottom to top of the log file

Validate if you are seeing the errors as mentioned below and only proceed further if the errors matches with your environment.


[2020-06-26T14:56:44.888-04:00] [WARN ] vc-extensionmanager-pool-93  70000042 100002 200001 com.vmware.vise.vim.extension.VcExtensionManager                  Detected an invalid signature for plugin: com.vmware.vcIntegrity: - com.vmware.vise.extensionfw.signing.PluginSignatureException: No META-INF/MANIFEST.MF entry found in the plugin zip file.

[2020-06-26T14:56:44.889-04:00] [INFO ] plugin-validation1            com.vmware.vise.extensionfw.impl.OsgiUsageValidationService       Started validation of OSGi bad practices.

[2020-06-26T14:56:44.889-04:00] [INFO ] plugin-validation1            com.vmware.vise.extensionfw.impl.OsgiUsageValidationService       Finished validation of OSGi bad practices.

[2020-06-26T14:56:44.891-04:00] [WARN ] vc-extensionmanager-pool-93  70000042 100002 200001 com.vmware.vise.extensionfw.impl.PackageManifestParser            Plugin id mismatch between the registered extension key (com.vmware.vcIntegrity) and the id specified in plugin-package.xml (com.vmware.vumclient). The registration id will be used but you should keep them in sync.

[2020-06-26T14:56:44.892-04:00] [WARN ] vc-extensionmanager-pool-93  70000042 100002 200001 com.vmware.vise.extensionfw.impl.PackageManifestParser            Plugin version mismatch for com.vmware.vcIntegrity between the plugin registration info ( and the version specified in plugin-package.xml (6.7.0). The registration version will be used but you should keep them in sync.

[2020-06-26T14:56:44.895-04:00] [WARN ] vc-extensionmanager-pool-93  70000042 100002 200001 com.vmware.vise.extensionfw.ExtensionManager                      Plugin package com.vmware.vcIntegrity: not deployed: it is marked incompatible either in your setup's compatibility-matrix.xml or internally in this release.


Now it is time to review if your compatibility-matrix.xml got modified.

The file is located @ C:/ProgramData/VMware/vCenterServer/cfg/vsphere-client/compatibility-matrix.xml


The file should be similar to what is shown below:




     <!-- ###VMWARE_KB_WHITELIST### -->

     <PluginPackage id="com.vmware.vsphere.(client|ds|ssoadminui|client.modules|client.srupload|client.telemetry)" status="compatible"/>

     <PluginPackage id="com.vmware.ds" status="compatible"/>

     <PluginPackage id="com.vmware.ssoadminui" status="compatible"/>

     <PluginPackage id="com.vmware.license.client" status="compatible"/>

     <PluginPackage id="com.vmware.opsmgmt.client" status="compatible"/>

     <PluginPackage id="" status="compatible"/>

     <PluginPackage id="com.vmware.vsphere.client.h5vsan" status="compatible"/>

     <PluginPackage id="com.vmware.vcIntegrity.vcIntegrity" status="compatible"/>

     <PluginPackage id="com.vmware.vum.client" status="compatible"/>

     <PluginPackage id="com.vmware.imagebuilder.imagebuilder" version="[6.6.0,)" status="compatible"/>

     <PluginPackage id="" status="compatible"/>

     <PluginPackage id="com.vmware.vco" version="[6.5.0,)" status="compatible"/>

     <PluginPackage id="com.vmware.vrops.install" status="compatible"/>

     <PluginPackage id="com.vmware.fallback.mixed" status="compatible"/>

     <!-- Known compatible plugins -->

     <PluginPackage id="com.vmware.vrUi" status="compatible"/>

     <PluginPackage id="com.nimblestorage.hi" version="[5.0.0,)" status="compatible"/>

     <PluginPackage id="" version="[4.2.0,)" status="compatible"/>

     <!-- TODO: Add more plugins here to enable them in the vSphere Client -->


     <PluginPackage id=".*" status="incompatible"/>






In 6.7 the VUM plugin ID is referred as "com.vmware.vcIntegrity" and  "com.vmware.vumclient"

However in the above xml file we see the VUM ID is mentioned as "com.vmware.vcIntegrity.vcIntegrity" and  "com.vmware.vum.client"

This causes the update manager plugin to fail to validate during the startup of web client service.




The resolution is simple, remove all the unwanted/stale plugin from the vCenter MOB page.

You can access vCenter MOB page and remove the stale plugins following this KB - VMware Knowledge Base



Example Screenshot showing list of unwanted plugins on the vCenter server which are not in use


Once the plugins are removed, take backup of the existing compatibility-matrix.xml

Now in the original "compatibility-matrix.xml" file, copy past the following and save it



   The 'id' value allows for standard java regular expressions. The actual plugin id

   is matched against this regular expression.



   The 'version' values must be a string in any of the following formats. If skipped

   it indicates any version.



   Version: An exact version, e.g. 6.0.0, 5.5, etc. The format allows for maximum

      of 4 dotted numbers.



   Interval: (, 6.4], [6.5, 7.0), (7.5, ). Use empty strings to mark infinity values.



   Range: Several versions and intervals can be mixed in one single string

      producing a set of value, e.g. ( ,6.4), 6.8.3, 6.9.1, [, ).



      Each item in the set is separated from the others using comma ",".

      Each item in the set can be either version or interval.



   The 'status' can be any of the following strings: unknown,

      incompatible, compatible, certified





        'Incompatible' plugins are not loaded. You can use this to 'blacklist'

        plugins if needed. To prevent specific plugin package(s) from

        loading, use the template entry below as guidance how to add new records

        with the actual id and version of the plugin you want to prevent from loading.



        The plugin ids can be taken from the plugin-package.xml file of each plugin.



        A few well known set of plugins locations (on the vCenter Appliance):






        On Windows the following locations can be checked:

           <INSTALL DRIVE>\ProgramData\vCenterServer\runtime\vsphere-client\plugin-packages

           <INSTALL DRIVE>\ProgramData\vCenterServer\cfg\vsphere-client\vc-packages

           <INSTALL DRIVE>\ProgramData\vCenterServer\cfg\vsphere-client\cm-service-packages



     <PluginPackage id="" version="1.0.0" status="incompatible"/>

     <PluginPackage id="" version="(,2.1]" status="incompatible"/>









        The sample section below shows 'whitelist' definition. Compatible plugins

        are loaded. All others are declared as incompatible (due to the id regex),

        thus effectively forbidding them.



        The approach limits the list of plugins loaded only to a small 'white' list.

        This allows for vsphere-client to work in a 'safe-like' mode.



        Below are predefined sets of plugins for your convenience:

        1st-party, core:









        1st-party extended (in addition to the above):





        2nd-party (basically anything that comes already pre-bundled with the

        vCenter Appliance and is not in the above two sets):





     <PluginPackage id="com.vmware.vsphere.(client|ds|ssoadminui|client.modules)" status="compatible"/>

     <PluginPackage id="com.vmware.license.client" status="compatible"/>

     <PluginPackage id="com.vmware.opsmgmt.client" status="compatible"/>



     <PluginPackage id=".*" status="incompatible"/>




Now restart vSphere web client service and you should be able to see the update manager listed and no longer marked as incompatible.

If you still see VUM plugin missing, review the virgo logs and start over again.


Happy Troubleshooting 




vSphere 7.0 Converge & Migration Process


Glad that you are seeking options to upgrade to our brand new offering vSphere 7.0

Please note that starting from vCenter 7.0, it will be only appliance based no options for integrating with any external database.


Community Support:

Did you know that VMware has a dedicated Install/Upgrade community ?

This sub community has an active user base and helps on common queries/errors during upgrade.

If you ever encounter any errors during the upgrade, feel free to post in our official install/upgrade forum - vSphere Upgrade & Install


This article focuses on migrating 6.5 Windows vCenter with external PSC to 7.0 vCenter Server

The steps are more or less same for migrating 6.7 windows to 7.0 vCenter Server


What has been deprecated in vCenter 7.0:

  • No option provided for deployed external PSC
  • No option provided for deploying Windows based vCenter
  • No inclusion of flash based Web client


Who can upgrade:


Source vCenter (Appliance or Windows)Destination vCenterUpgrade/Migrate
vCenter 5.5 & 6.0 (any version)vCenter 7.0Not Supported
vCenter 6.5 & 6.7 (any version)vCenter 7.0Supported


Click here to check the vCenter Server version upgrade compatibility

Click here to get update sequence for vSphere 7.0

Don't forget to read the vSphere Back-in-time release upgrade restriction



For vSphere 7.0, the existing license needs to be upgraded and you can contact VMware licensing team for upgrade options specific to your existing license.

Click here to learn more about licensing requirement for vCenter Server 7.0



Click here to download the latest version of vCenter 7.0


What you require:

  • A jump box, preferably windows 10 or any windows server 2008/20212/2016
  • It is advised to keep the jump box and the destination vCenter 7.0 on the same subnet, same port group/VLAN as the source vCenter appliance that you are planning to upgrade

          This way we can eliminate most of the network related errors during the upgrade phase.

  • User has access to windows based external PSC and vCenter
  • Make sure you have taken complete backup of the vCenter database


A quick summary of actions we will be performing for this migration process:


The migration task is split into stage 1 and stage 2.

Stage 1

Deploy a new 7.0 vCenter VM with active network connection set to communicate via the temporary IP address


Stage 2

The installer exports the data from the existing 6.5 vCenter to the new 7.0 vCenter using temporary IP

Performs convergence, shuts down source vCenter and reverts the network back to the same IP as the source vCenter

Performs First-Boot of vCenter 7.0 services and then imports copied data to the 7.0 vCenter


Steps with Screenshot :



Stage 1



Once you have read the above documents proceed to mount the downloaded image on the jump box

Inside the mounted directory, copy the "migration-assistant" folder

Log into the source windows vCenter server and paste the "migration-assistant" folder




<On the source 6.5 windows vCenter>

Navigate to the folder and Run the migration assistant as Administrator




Enter the SSO password and wait for the installer to perform pre-checks and shows prompt "waiting for migration to start"






<Login back to the Jump Box where you have mounted the installer ISO>

Navigate to the following directory and run the installer as Administrator and Select "Migrate"



Once the installer starts, on the Introduction page, we have a quick recap of the two stage process which we had discussed earlier

Click "Next" and accept the EULA (End User License Agreement)




Here you need to enter the FQDN of the source vCenter server

Also your local SSO administrator username and the password and click "Next"

(Make sure to correct the domain vsphere.local in case if you have set a different local SSO domain)


The installer gives prompt "Converge to an embedded Platform Services Controller"

This is to let users know that it has read the underlying vCenter configuration.

It automatically detects that the source vCenter has external SSO and will perform a converge operation during Migration





Enter the host/vcenter name or IP on which the new 7.0 VM is going to get deployed

Since I have set the host IP address, I have set the username as root

If you had entered vCenter name, you should be entering the SSO admin user which is administartor@vsphere.local




The VM name is the name on which the new VM will be deployed on the inventory

Also here you are given option to set the root password for the 7.0 vCenter




Set the appliance deployment size based on your environmental requirement

You can refer the table in the above screenshot to size it accordingly





You select the Datastore where the new VM will be deployed




It is advised you select the same port-group where the source vCenter VM resides

Provide the temporary IP address, subnet, gateway and DNS server

All these steps are mandatory and cannot be skipped





You are given one final view of all the network settings provided

Once confirming the details, click on Finish to start Stage1 deployment




The deployment of the new vCenter 7.0 VM starts

You can check its progress by logging into the ESXi host and check the tasks pane

The installer might freeze at 80% but do not panic as this is common

At 80% is where it installs the RPM packages for the appliance




Once completed, you should see the screen as above



At this point, it is advised to take a snapshot of the newly deployed vCenter 7.0 appliance

If by any chance if the installer fails, you can revert back to the end of Stage1 installation and retry the upgrade again


To restart the upgrade from this point, you just simply enter the temporary IP address with port 5480

Example: If my temporary IP is

Then I restart the upgrade process from browser



Stage 2


Click continue to go to Stage 2 Introduction page where the process is explained

Click "Next" to take you to the "Connect to source vCenter" page





The installer detects the existing vCenter details which were provided earlier

Click "Next" to run the pre-migration checks for Stage 2




This is the new option introduced

You can select the default option in case if you have single PSC and vCenter like we used in this guide




Optional - Only for reference purpose

This is how you can select to manage convergence in case if the PSC has multiple vCenter registered





You are given option to enter the username which has privilege to add machines to the Domain

This step automatically adds vCenter appliance to the AD domain




You can choose to keep tasks, events and performance charts data

You can also skip and go only with the configuration data of the source vCenter




You can check this box to join VMware customer experience improvement program

Click "Next" to continue




You are given options to validate your inputs

You have to check the "I have backed up..." to continue

If all the entered data is correct, start the final step by clicking on "Finish"




Stage 2 starts and it will power off the source vCenter

The new vCenter 7.0 VM will take the same IP as the source and the temporary IP will be deleted

Once complete you will see installation successful 100% complete.


This marks the end of Stage 2 and completion of the migration process



Additional Notes:

Only the source windows vCenter is only powered off

If you notice the source PSC is still powered on

Also if you check the replication partner, you will still see the source PSC registered with the new vCenter 7.0 appliance

This is kept so that customers can continue the migrate paths for other vCenter which are connected to the same PSC

Once the entire environment is migrated, you can decommission the source windows PSC following this link


- Jonathan Ebenezer

Tell us your upgrade story for a chance to win a MacBook Air or an iPod Touch.

Has upgrading to VMware vSphere already delivered a noticeable impact on your IT environment?  Are you able to quantify the results and share them with us? 

Tell us your upgrade story for a chance to win an Apple MacBook Air laptop (bundled with VMware Fusion) or an Apple iPod Touch.  

Read the Contest Rules for more details.


Submit your story by 17 August, 2009 to enter.


Success Story Guidelines and Criteria

Tell us how VMware vSphere has solved specific IT issues (business continuity and disaster recovery, desktop management, IT Service Delivery etc).

In your responses, be sure to include information about:

  1. Business and technical problem(s) you solved (pain points, uniqueness of problem).

  2. VMware vSphere features/technologies you used to solve the problem(s).

  3. Size and scope of your VMware Infrastructure 3 and vSphere deployments.

  4. Benefits of using VMware to solve a problem (ROI, TCO, other quantifiable business results).


Responses will be judged based on your ability to demonstrate:

  1. An understanding about the general benefits of using virtualization, as well as the features and benefits of VMware vSphere.

  2. The specific advantages of using VMware vSphere to solve your particular business and/or technical challenge(s).

  3. Quantifiable results and/or other metrics you have gathered.

  4. Creativity! You are encouraged to include videos, diagrams and other media uploads in your response.


With vSphere now in GA, we've added a bunch of stuff to the Upgrade Center:


Coming later this month: The Path to vSphere Unleashed -- A detailed guide on how to complete the transition from VI3 to vSphere 4.

Be among the first to get training on the industry's first cloud operating system. If you're upgrading from VMware Infrastructure 3, VMware vSphere: What's New covers new features and how to perform the upgrade. If VMware vSphere is your first virtualization experience, VMware vSphere: Install, Configure, Manage covers all the skills you need to get started.

Feedback from students who've attended our instructor-led courses:


&quot;The best training course I've ever taken from an instructor led standpoint. The most focused, and well formatted training. Instructor was best I've ever had in any course (about 40 courses to date) stayed on track, while answering misc. questions asked from the Class. I will be recommending this course to all co-workers, and because of this course, have to decided that there is a place for this product in our environment.&quot;



"This was my first online technical class, and I found the format and content far better than any other technical training class I've taken. The lab setup, course materials, and instructors are all top notch."

&quot;After several VMware seminars, webinars and discussions with colleagues that have worked with VMware, this course finally revealed the magic behind the curtains. My mind is overflowing with creative designs and uses of VMware in our current environment. I look forward to implementing VMware in our environment and promoting this technology across other sister companies within our corporation. The course gave me enough information to help design our VMware infrastructure, plan for implementation and coordinate post implementation tasks and clean-up. Keep up the great work!&quot;



As many of you already suspected, VMware vSphere 4 GA has been released tonight.  You can now download and evaluate the product for free, for 60 days, and purchase it through the VMware Store.  For all your vSphere needs, visit the VMware vSphere Community - your VMware vSphere headquarters!



VMware vSphere Community



Thanks, Badsah



The VMware vSphere upgrade center went live tonight along with the launch of VMware vSphere on the website. The VMware vSphere upgrade center was designed to help VMware Infrastructure customers plan for a smooth migration to VMware vSphere.


Upgrade Center features:

Understanding VMware vSphere licensing

What's new with VMware vSphere

Plus lots of great migration videos and technical resources.


Be the first to check it out! We hope you enjoy the upgrade center.

Check back here or subscribe to the RSS feed to get updates on the upcoming product launch.


The VMware Team

Filter Blog

By date: By tag: