I’ve not yet got my hands really dirty on ESX 3.0.x to ESX 3.5 and VirtualCenter 2.0.x to 2.5 upgrades. Although crudely “play” with the process under the Release Candate. Initially, I had a permissions problem with the VirtualCenter upgrade and my SQL 2000 server. There’s been a length forum thread on this which I have been involved with. It’s become clear that if you have a SQL 2000 server additional permissions are required for an upgrade, which were not previously required in previous upgrades from VC 1>2 or the intra-upgrades from say 2.0.0>2.0.1>2.0.2

A KB article from VMware outlines this issue. As far as I know its not an issue for SQL 2005…

Link: ID: 1003346

This entry was posted on Tuesday, December 18th, 2007 at 11:09 pm and is filed under vCenter. You can follow any responses to this entry through the RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.