During an upgrade of vCenter 2.5 to 4.0 at a customer site I decided it would be a good idea to record the steps required. In this video you will see how to upgrade VMware vCenter 2.5 to vCenter 4.0 that uses a Microsoft SQL database. The steps are trivial and I have done more than a handful of these on customers production servers.
The most important thing is to follow the best practices, give your ODBC user db_owner privledge on the MSDB and vCenter database prior to any install or upgrade - then remove the privledge after the installer is complete. Also make sure that IIS or any other webserver is disabled.
:: June 1, 2009 by Rick Scherer
Posted under vCenter, vSphere, this blog has 7,432 views and 10 responses.
(1 votes, average: 5 out of 5)
Loading ...
11:32 pm on December 18th, 2009
Thanks for the great video it is really helpfull
10:01 am on October 23rd, 2009
Great Video…Well done…
I would like to see one focusing on the MSQL
10:48 pm on September 24th, 2009
Nothing really more to the db_owner setting…. you need to assign db_owner to the msdb database during installations and upgrades of vCenter Server (obviously only MS SQL, does not apply to Oracle).
This is because the vCenter Server installer writes some data into the MSDB database. After the installation is complete you can remove this permission.
6:23 pm on September 24th, 2009
You really gloss over the whole db owner stuff. I’m still none the wiser.
5:16 pm on June 28th, 2009
Thanks Rick for this Great video..!!!
12:39 am on June 5th, 2009
Rick,
Thanks for the great video. Helped me realize I was being an idiot and not giving db_owner to the MSDB db. I was focused on doing it to the VCenter database, which it already had, and boggled me. I didn’t realize I was being an idiot until I saw you saying something about REMOVING the role from the vc user in MSDB. Can’t remember the last time I had a /forehead-slap moment like that.
Looking forward to the ESX host upgrade video! You should do more of these!
-Nick
nhowell@ipcm.com