MichaelLeone
Enthusiast
Enthusiast

Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins

So I am about ready to start upgrading my 4.1 U1 datacenter to v5. And I have a couple last questions.

My DB is SQL 2008, but it's not local; we have a DB server that hosts a number of DBs for various applications. The 2 days "What's new in v5" class I took used local DBs. Having it non-local should not be an issue, I don't think. It should Just Work, right? (presuming I tell it to upgrade the database, as I should)

My vCenter currently runs as a LOCALSYSTEM account; should I change it to use a domain account? (we run Win 2008 AD) If so, are there special access rights I should grant to it (such as Local Administrator)? I have an account I use, that is a member of the AD group "ESX Admins", to run PowerCLI scripts with, etc.

Also, the v4 vSphere client should connect to the newly upgraded vCenter? It's installed on a number of our employee's machines; will they still be able to connect, or will they need to upgrade their client before accessing the new v5 vCenter?

Also, we have one 3rd party vCenter plugin, from Emulex, for upgrading the firmware on the FC cards. Do I need to uninstall this before upgrading, or will the upgrade process just automatically disable any 3rd party plugins it finds? (I realize I will have to go get the v5 plugin and install it, after the upgrade is done)

OK, so that was a bit more than a "couple". :slightly_smiling_face: Just want to be thorough ...

Reply
0 Kudos