A short article today as yesterday I installed VUM for the first time in a while and I stumbled a bit. How quick you forget when you work so much and in things that change often! But here is some quick reminders before you install VMware Update Manager (VUM). Whether it is the first time, or the 10th, this might help.
- Create the database, and the ODBC connection before you start.
- The service account you run VUM under, and or use for connecting VUM to vC, should have vCenter admin rights, and also local admin rights too. I name the SQL account the same as this one.
- The SQL account needs to have db_owner (DBO) rights on the MSDB database.
- The database should have a Simple Recovery model.
- You need to create a 32 bit ODBC even though VUM is is installed in a 64 bit environment. That is due to it being a 32 bit application – even though you must install it in 64 bit OS. Use the info here if you need reminders on how to do that. But you may remember %windir%\SysWow64\odbcad32.exe.
- SQL needs to support both Windows and SQL account mode since VUM needs you to use a SQL account. I create a SQL account that is the same as the Windows Account I use as a service account and I use the SQL account to own the VUM database. If your SQL doesn’t support SQL accounts – like mine didn’t it is easy to change but does require a restart of SQL.
- SQL when installed does nothing for the Windows firewall. So remember to create a TCP inbound rule for port 1433. If you are not using SQL but rather SQL Express the port is not the standard port of 1433. More info on this can be found here, and here. (BTW, the SQL server is found –> C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn\Sqlservr.exe).
- Use the SQL Native Client – found here for Win2K12 and here for Win2K8.
- I tested this with Win2K12 with current patches to hold VUM, vCenter 5.5 Update 2 VUM, and SQL 2012.
- 2/25/16 – Seems I had a misspelled odbc32.exe rather then odbcad32.exe.
- 5/11/15 – added SQL file name and path above.
- 4/17/15 – added comment about SQL account needing DBO in MSDB db.
- 3/11/15 – added the comment about the service account.
- 3/8/15 – I implied above that you need to have both Window and SQL account for VUM and that is not correct. The way this article is written you only need SQL account support. SQL account is easier, and I like using it but many customers I suspect will want to use Windows account for things so that means both should be supported.
- 3/8/15 – as seen in Comments – thanks Jon, you can in fact use the a Windows account with SQL for VUM but you need to make sure the VUM service runs with that account.
Hope that this helps,
=== END ===