I've done the basic upgrade for VC 2.5. Please find below my notes: 1. Consider upgrading SQL server to SQL 2005. VC 2.5 is more designed to work with SQL2005 and also SQL2005 is much fast...
See more...
I've done the basic upgrade for VC 2.5. Please find below my notes: 1. Consider upgrading SQL server to SQL 2005. VC 2.5 is more designed to work with SQL2005 and also SQL2005 is much faster than SQL 2000. 2. VC 2.5 is not working with MSDE, so you need to upgrade MSDE to SQL Express 2005. There is an article on Microsoft web site with upgrade path: 3. Create a proper backup of VC database ( schema update failed few times for me ). Better just detach the DB and make copy of MDF & LDF files and than attach it again. 4. Try to avoid using autorun.exe and install components separately. For VC 2.5 installation run "VMware-vcserver.exe". 5. Use local SQL account with full database permissions ( or "sa" user ) when installation will ask you to provide credentials. I tried with Windows Authentication cause my SQL is located on the same server but it failed. 6. When installing VC do not install Web Components. We are not using it and the web interface is still missing functionality. Also web component is running on "ApacheTomcatJRE" and client is running .Net. I do not know how much alcohol they took at VMWare before making decision to not to follow one single platform for all components 7. At the end of VC upgrade process the database upgrade wizard will run. It will tell you how much free space you need to have for successful schema update. Please pay attention to this number and make sure you have enough space. Also, set the VC database log file to unlimited growth ( this can be only related to SQL Express ). 8. As soon as DB schema will be updated VC service will be restarted automatically. So here is the biggest problem I found. VC started to update agents on all ESX hosts, and some of them failed. I just cannot imagine how hard it will be to track in a big datacenters with hundreds of hosts. Anyway, if agent update failed just go to the console and restart "vpxa" and "mgmt-vmware". Than monitor the vpx log file on the host using "tail -f vpxa.log" I have not installed VC Update Manager and VC Converter as I think it's more related to VC 3.5. Will install these components later when host will be updated to 3.5. The good thing I found is that VC 2.5 is much more faster and VC client is more responsive than the previous version.