VMware support informed me the license files weren't compatible between VC 2.0.2 and 2.5. Is this not true? We're using the "served" lic file on our VC. Is there modification that has to take place to use the same license file in VC 2.5? If so, what?
Like almost everyone says before me, Upgrade VC. Just for the new functions and the sleek look of the app, it worth it.
Upgrading the VC first is not just for the new funtions and the sleek look ... Its because you wont be able to manage your 3.5 host in virtualcenter without a 2.5 VC. I'm pretty sure that if you have a VC you'll want to use it and configure your newly upgraded host with DRS/HA/VMotion etc...
And the license file should be good from 2.0.2 to 2.5 I haven't heard of anything different. We just went from 2.0.2 to 2.5 with no issues with the lic file.
Somebody in support was misinformed then, thanks for the info. Just to confirm, after upgrading VC 2.0.2 to 2.5, I can reconnect to all our ESX 3.0.2 hosts? We'll be upgrading our 15 hosts to 3.5 over the next month or so. Also, any issues with the upgrade process to 3.5? Should we go with upgrading to 3.5 Update 3? I know we had strange issues/errors with the 2.x upgrade to 3.0, and ended up vmotioning off the VM's, then doing a fresh install of each host.
I upgraded our VC a couple weeks ago from 2.0.2 to 2.5U3. From what I know is 2.5U3 is a release to fix a lot of bugs that were happening in U2, so I would go that route. I let my VC upgrade sit for about a week to make sure there were no issues. I did a straight up grade and it ran fine. I was able to reconnect all of my 3.0.2 devices like nothing happened. When upgrading your host, we always rebuild from scratch and don't let any residing old files linger on the hosts from an upgrade. That way we know there is a clean install and there should be no issues after that. We're slowly upgrading our hosts from 3.0.2 to 3.5. We're in a mixed environment right now with no issues