Update Manager missing in vCSA 6.5 build 4944578?

[housec]

I deployed a new vCSA 6.5 build 4944578 and Update Manager is not visible on the Home page, nor the Home menu, nor is there an Update Manager tab on a datacenter, cluster, or host view.

The vSphere Update Manager service is "Good" and "Running".

Does anybody else see this with vCSA 6.5 build 4944578?

I have a separate vCSA 6.5 on an earlier build 4602587 where Update Manager is present.

Tearing my hair out here... (what little is left of it)

[a_p_]

Do you have any items (e.g. hosts) in the new vCSA's inventory yet?

André

[housec]

Yes, a cluster of 3 hosts and several dozen VMs.

[fgl]

Are you using the "vSphere Client (HTML5)" client?  As VUM is not available in the HTML5 client if so you will need to use the "vSphere Web Client (Flash)" client for VUM.

vSphere Client (HTML5) and vSphere Web Client 6.5 FAQ (2147929) | VMware KB

VUM also is fully available in the vSphere Web Client. Both plug-ins will be available in the HTML5 vSphere Client in the future.

[housec]

Nope, using the normal (flash) web client.

[housec]

Coworker gave me the idea to try a URL similar to what works on the older 6.5 vCSA build. It errors out.

The URL i tried going to is /vsphere-client/?csp#extensionId%3Dcom.vmware.vum.itemsView

... this is the same URL that you would go to if you were able to click on the Update Manager icon on the Home screen or Home menu (I do not have it in either menu or home screen). I get these errors below:

Is there a plugin missing?

[a_p_]

Just a guess. Did you delete the browser cache, and/or try another browser yet to see whether the issue persists?

André

[housec]

Indeed, have tried different browsers, different PCs. Feels like the UI plugin is missing or something.

[housec]

VMware Update Manager plugin is not listed in the 6.5 vCSA build 4944578:

... but it is in vCSA 6.5 build 4602587

[fgl]

Under Home>Administration>Solutions>Client Plug-Ins do you see VMware Update Manager listed and if so is it enabled or disabled?

[housec]

see previous message for the screenshot, it is not listed at all.

[Aviator20111014]

Hi.

Same Problem here with VCSA 6.5.0.5500 Build Number 5318154.

I opened a support request in April, but still no solution.

I tried the following:

• Reregister VUM using /usr/lib/vmware-updatemgr/bin/updatemgr-util register-vc on the appliance Linux shell
  
• Cleaning up the Serenity DB (see <https://kb.vmware.com/kb/2089949>​)

Did you exchange any SSL certificates on the VCSA? I did,maybe that's the cause for the missing VUM.

Cheers

David

[timbot]

mine was missing also, but was visible from the ms server running as vcenter. problem ended up being even though they are in linked mode, i still had to go directly to the vcenter server's url i wanted to use update manager for. i.e. vcserver1 (win) url only showed update manager tab for itself, but not the vcsa. vcserver2 (vcsa) url showed update manager tab for both. weird.

[Noiden]

Any solutions to this yet? I have the same problem.

[grep_boy]

I SOLVED THIS FOR ME!!!!! FINALLY

So, Folks - without the help of VMware, I inspected my other instance and figured out how to bypass all of the crap and get the VUM client installed and working....

Before starting this, make sure on your VCSA, you can locate /usr/lib/vmware-updatemgr/bin/docroot/vci/downloads/vumclient.zip.

Now perform the following steps:

1. cd /etc/vmware/vsphere-client/cm-service-packages/com.vmware.cis.vsphereclient.plugin
2. mkdir com.vmware.vcIntegrity.vcIntegrity-6.5.0
3. chown vsphere-client:users com.vmware.vcIntegrity.vcIntegrity-6.5.0
4. chmod 755 com.vmware.vcIntegrity.vcIntegrity-6.5.0
5. cd com.vmware.vcIntegrity.vcIntegrity-6.5.0
6. unzip /usr/lib/vmware-updatemgr/bin/docroot/vci/downloads/vumclient.zip
7. chown -R vsphere-client:users *
8. chmod 744 plugin-package.xml
9. cd plugins
10. chmod 744 *
11. service-control --stop --all
12. service-control --start --all

I gave it a few minutes and then logged into VCSA, and low and behold, my update manager client is now there.

The problem is definitely a certificate issue when it tries to download the vumclient.zip. Clearly VMWare support has no idea how to fix that.

Anyway, I hope this work around works for you!

[virtualbarker]

This worked for me as well.  Nice work!

[joseares]

The solution provided by grep_boy also worked for us! Thank you very much!

[doublemt]

Did the trick for me !!!!!!