Install vSphere Update Manager in addition to vCenter Server Appliance

After I’ve installed the vCenter Server Appliance (vCSA) a few weeks ago the testing process is over and I’ve migrated our production vCenter to the new vCSA 6.0.0b. To be able to update and patch our ESXi hosts I want to install the vSphere Update Manager (vUM). Because there is no option to install the vUM on vCSA directly, you need a Windows host for installation.

Prerequirements

Windows Host (e.g. Windows Server 2012 R2 Standard)
- If not already installed, download an install the SQL Server Native Client.
  
  The Native Client is a component of the SQL Server 2012 SP2 Feature Pack which you can download on the Microsoft Homepage
  Download – Microsoft SQL Server 2012 SP2 Feature Pack (SQL Native Client)
  Select the component sqlncli.msi and click Next
SQL Server > Check the VMware Product Interoperability Matrix because SQL2012 SP1 is supported SP2 not!
- Small deployments (5 Host / 50 VMs) could be installed with SQL2012 Express which is shipped within the installer.
vSphere Update Manager Database on SQL Server
- Create a new database and give the service account dbo rights on Update Manager database and msdb
Create System DSN on the vSphere Update Manager Host (32Bit DSN!)

Installation

Now the installation can begin.

Mount the ISO (e.g. VMware-VIMSetup-all-6.0.0-2800571.iso) Download
Select vSphere Update Manager > Server in the left pane and click on install
You can leave the checkbox active
Next you need to enter the data and login to your vCenter Server
We use a service account with administrative rights in the vCenter
The installer now needs the previous added DSN to the Update Manager Database
If the database is set to full recovery mode you will get a warning. Backup your database periodically and everything is fine :)
If your Host is resolvable via DNS you can use the hostname for port settings. Otherwise you must use the IP address.
If you have a proxy server for internet access you must activate to checkbox. Then the next step wants you proxy settings.
The vSphere Update Manager uses two folder. One program folder and one for the patch and update data.
If the partition which is storing the patch and update data has less the 120GB free space you get a warning message
After installation ends you must check the logs in C:\ProgramData\VMware\VMware Update Manager\Logs vmware-vum-server-log4cpp.log
As you can see the service is trying to connect the database with his computer account. If you find an error like this, you must change the user for the VMware vSphere Update Manager Service to the service account.

[2015-08-20 09:41:45:827 ‘VcIntegrity’ 1940 ERROR] [vcIntegrity, 829] Error initializing database: ODBC error: (28000) – [Microsoft][SQL Server Native Client 11.0][SQL Server]Fehler bei der Anmeldung für den Benutzer ‘AD\VSUM$’.

After restarting the service the log should show the initialization of the database.
Now you can install the vSphere Update Manager Client PlugIn on your vSphere Client