This issue just caught me out..of course it’s in the 5.5U1 release notes (but who reads ALL the release notes).
Below is the relevant snippet, from the full release document which can be found here.
- VMware Update Manager plugin is disabled when vCenter Server 5.5 Update 1 is upgraded to vCenter Server 5.5 Update 1a*
When you upgrade from vCenter Server 5.5 Update 1 to 5.5 Update 1a, the VMware vCenter Update Manager tab is not visible as the VMware Update Manager plugin gets disabled.
Workaround: To reconfigure the vCenter Update Manager settings without reinstalling vCenter Update Manager:
- Navigate to C:\Program Files (x86)\VMware\Infrastructure\Update Manager.
- Launch VMwareUpdateManagerUtility.exe and log in with vCenter Server credentials.
- After login, from Options select Re-register to vCenter Server.
- Enter vCenter Server IP address or Name, User Name and Password.
- Click on Apply.
- After applying configuration successfully, restart VMware vCenter Update Manager service.
Anyway, the issue came about by me having a PSOD on my new HP Servers, that is despite me Tweeting about it in July 2014 – typical!
— Nick Furnell (@nickfurnell) July 8, 2014
..and been referenced again by Dean later in the same month..
— Dean L. (@saintdle) July 20, 2014
The fix for this issue is clearly explained in this URL BUT although the notes are very clear, it does rely on you using the command line and downloading the correct VIB from HP’s website. The better approach is to add HP’s own VMware Update Bundles to Update Manager:-
Go to In Admin View -> Configuration -> Download Settings -> Add Download Source
http://vibsdepot.hp.com/index.xml for HP bundles
http://vibsdepot.hp.com/index-drv.xml for HP drivers
This method is much better as it uses the Update Manager Snap-In to push the correct update out to the Hosts.
Again, just to credit the original authors the full conversation is here
Good Luck, I hope that this helps someone else