This installment in the vSphere 5.1 Update 1 installation series will install VUM (VMware Update Manager) on your system. In Part 10 of this series we configured the VUM DSN in preparation for installing VUM. So now we are ready to deploy VUM. You can co-locate it on your vCenter server in small environments, or have a dedicated VM for medium to large environments.
Before we get started, listed below are the other related articles in this series:
Part 1 (SSO Service)
Part 2 (Create vCenter SSL Certificates)
Part 3 (Install vCenter SSO SSL Certificate)
Part 4 (Install Inventory Service)
Part 5 (Install Inventory Service SSL Certificate)
Part 6 (Create vCenter and VUM Databases)
Part 7 (Install vCenter Server)
Part 8 (Install Web Client)
Part 9 (Optional SSO Configuration)
Part 10 (Create VUM DSN)
Part 12 (VUM SSL Configuration)
Part 13 (VUM Configuration)
Part 14 (Web Client and Log Browser SSL)
Part 15 (ESXi Host SSL Certificate)
Install VUM 5.1 Update 1
1. Start the vSphere Update Manager installation from the vSphere 5.1 main menu.
2. Select vSphere Update Manager and click through the wizard until you get to the following screen. If your system is on the internet then leave the box checked, so that you will have all of the latest patches. If you are on a disconnected/secure network, then uncheck the box so it doesn’t try to access the internet.
3. On the next screen enter the FDQN of your vCenter server and the username that VUM will use to access vCenter. In this case I just re-used the vCenter service account, since I don’t see a reason to have yet another service account just for VUM. But you certainly could, assuming you gave it appropriate rights in vCenter. Note: If the install hangs at this point, I’ve seen an issue using the FQDN vice the IP address. Should it hang you can kill the process called vciInstallutils.exe and try again with different credentials, hostname, or IP.
4. If the DSN is properly configured then it should be listed on the next screen.
5. In the drop down change the setting from the IP address to the FQDN.
6. I would strongly urge that you use a different drive for the patch repository, as it can get big and you don’t want it filling up your C drive.
7. Sit back and wait for the installation to complete, which shouldn’t take very long.