The time comes when you have to upgrade your system to add new features and functionality. Sometimes you find bugs and need to troubleshoot a little bit the situation. Precisely what happened to me when upgrading from VCSA 6.0 to VCSA 6.5 with embedded VMware Update Manager (VUM). It took me a little digging here and there and few messages to my colleagues in the VMware community, but finally I came up with the solution. The problem the system presented was this:

Error

Error attempting Vcintegrity Export file does not exist or is corrupted, abort import
Resolution

Please check vcIntegrity migration logs for details.

That came up at the end of the vCenter migration. The cause is that I had a VCSA with an external VUM. The migration assistant won’t help because the process is expecting to find the service in the old vCenter appliance (VCSA 6.0). This is a documented problem, and you’ll see the KB here. The first step is to remove the VUM from the old server, then deregister the Web Plugin from the new vCenter. At this moment go ahead and restart(stop and start) the web client service in the VCSA command line. Use the command “service-control –start vsphere-client” (VMware KB found here). And then either disable the VMware Update Manager plugin from the web client using the GUI or the MOB, these are the steps:

1. In a web browser, navigate to http://vCenter_Server_name_or_IP/mob.
   Where vCenter_Server_name_or_IP/mob is the name of your vCenter Server or its IP address.
2. Click Content.
3. Click ExtensionManager.
4. Select and copy the name of the plug-in you want to remove from the list of values under Properties. For a list of default plug-ins, see the Additional Information section of this article.
5. Click UnregisterExtension. A new window appears.
6. Paste the key (vcIntegrity) of the plug-in and click Invoke Method. This removes the plug-in and results in void.
7. Close the window.
8. Refresh the Managed Object Type:ManagedObjectReference:ExtensionManager window to verify that the plug-in is removed successfully.

The previous steps are found in this other VMware KB.

Then to register the VUM with the vCenter, you need to follow this procedure:

cd /lib/vmware-updatemgr/bin
mkdir backup
cp -p extension.xml backup/
cp -p vci-integrity.xml backup/
cp -p jetty-vum* backup/

Now go ahead and finish the failed registration with this command:

/lib/vmware-updatemgr/bin/vmware-vciInstallUtils -C /lib/vmware-updatemgr/bin/ -L /var/log/vmware/vmware-updatemgr/ -I /lib/vmware-updatemgr/bin/ -v <your vCenter FQDN> -p 80 -U administrator@<your SSO domain> -P <password> -S /lib/vmware-updatemgr/bin/extension.xml -O extupdate

chown updatemgr:updatemgr vci-integrity.xml

service-control --start vmware-updatemgr

In the command above replace the information within the <> with your own, for example <your vCenter FQDN> could be vcenter01.google.com.

Hopefully, that will save you some time in this specific case of a failed vCenter upgrade because the VUM was on a separate server than the vCenter.