Tag Archives: Vmware Update Manager


No vQuicky note on this one – just fun to read so read on 🙂

I was working on my lab for a new deep dive blog post and guess what I run into and was actually glad/surprised to notice – VUM is now in vsphere webclient 5.5!

I recently upgraded my home lab with vsphere and vcenter 5.5 and also vmware’s update manager as well. It has been running great ever since and my discovery brought a smile to my face. Not that I keep my hosts up to date all the time but it was more about the convenience of not having to switch back and forth between the Windows client and the web client – now that I am getting used to using it.


Above u see the vmware vsphere update manager plugin installed and enabled. You could disable it which is the only action allowed as expected.

And on the Summary page for the Host – you have a update manager status showing up.

Read More …


vQuicky – For the impatient like me

> No webclient support for plugin installs especially vmware update manager.

> Need to use vsphere client to update your hosts

> Don’t forget to check if your hosts are able to resolve to the vum/vcenter server using the dns or else scanning of hosts will fail


Over the weekend I spent time rebuilding my lab. My lab has servers running on usb sticks @ ESXi 5.0 . I needed them to be on 5.1 but really didn’t want to rekick these boxes.

The only right way to do it was to rebuild my vcenter part of the lab from 5.0 to 5.1. Now the way to do that was to blow away what I have right now and do a proper upgrade because with 5.1 – the Single Sign On has been introduced. Now I can cheat by doing a vcenter simple install – basically an all in one vcenter instance but I wanted to mimic a typical production environment.

So I rolled out 4 vms – a webclient, a SSO, a Inventory service and a vCenter server which also had VUM installed.

The order of installation is SSO first, then comes the inventory service followed by the webclient and then the vcenter server. Once the install is done, you login to the webclient using the [email protected] default id and add the domain in the SSO configuration part. Once done you can login as a domain user and mess around with your vcenter.  Also don’t forget, if you look closely by default, [email protected] has admin access to the vcenter. In a production environment, you may not want this. Again its not a big deal but really, you typically don’t want any stale accounts be granted the admin role when not needed.

I had to login to the vcenter client and get the plugin installed and start to patch my two hosts. Now patch failed at the initial scan. I forgot to update the hosts with the right dns entries so they can lookup the vum server to pull the downloads. After a quick dns update all worked well.

Hopefully I will have a demo going for you in a video.

Feel free to comment or correct me 🙂