I finally managed to upgrade my VMWare server to 2.0 build 11xxx (not the latest one).

There were two reasons for the upgrade delay:

• I keep receiving incomplete/failed download, until 2/3 weeks ago
• Once downloaded, I keep getting distraction on performing the upgrade

So, here are a couple things that I noticed:

• The new release, changed its console from application into web-based. The 'VMWare Server Console' changed into 'VMware Server Homepage'
• During installation, the installer asked for two unused (TCP) ports in the host for management access. One is for http and the other one is for https access. The default is 8222 and 8333 for http and https.
• The guest console is no longer directly accessible from within the management console. Instead, it is now using browser plugin that pops-up a separate browser window for guest console access.
• ... and the blue theme is lovely (it's only one bar on top, so don't ask me where is the theme)

The steps that I did for performing the upgrade were quite straight forward:

• Download the installer (d'oh!)
• Execute the installer (d'oh!) -> for Windows Vista host, remember to run the installer as administrator
• There will be one dialog box that asked for the address and port to be used for http and https. NOTE THIS DOWN! The default is using http://hostname:8222 and https://hostname:8333. If you like some fancy security stuff, you can change the hostname into the FQDN. Alas, those two ports will still listen to all interface anyway.
• Once done, restart the vmware server service (linux) or reboot the whole system (Windows)
• After the service restarted or system rebooted, try to login through web browser using the address that you noted above. Use http for simpliicity of access.
• Once logged in, check that all your VMs were intact (they are all listed nicely, resources like ram, cpu, disk, nic are instact, etc). Oh, the login was the same login when you use the previous version. For the new install, normally they won't ask for login credential. Simply use your login or local administrator (or even domain administrator) login.
• Make sure the NIC connections are all in place. If you have VMXnet0 pointing to your first NIC, make sure it stays the same. Unfortunately, if you perform upgrade, the VMWare virtual network settting were wiped off. In order to change it, access it through 'start | programs | vmware server | manage virtual network' shortcut. If you have two NICs, the 'auto bridge' annoying settings will be back again (ta da!!!). Note: if you are using Windows Vista, make sure you run the'manage virtual network' as administrator. Otherwise, you will see the auto bridge option is dimmed and inacessible/ unchangeable.
• Access your V's console, install the browser plugin if needed. For Internet Explorer, it will launch vmware-vmrc-win32-x86.exe, while for Firefox, the plugin will be offered for installation just like a typical plugin request (at least for Firefox 3.x. For Firefox 2.x -> please upgrade to 3.x)
• Once you have managed to access your VM's console, check your VM's completeness and access (pinging here and there might be the easiest way). For Internet Explorer users, once the vmrc installed, your browser will be closed and your computer will be blown off .

Nah, just kidding. For Internet Explorer users, unfortunately, once the plugin installation completed, and you just simply hit enter (or close or OK or whatever button in the last installation window dialog), then your browser will be closed and you have (must!) re-run your Internet Explorer (and all of their instances, since the default option to to close all IE instance, hah!)

• ... done!
• (you can pack and go to Hawaii now, knowing that your VMWare Server upgrade is complete and intact)
• Hang on ... didn't you forgot something? VMware tools!
• The installation of VMware tools is the same like when you install it the first time you created your VMs in the earlier version.

Conclusion: the steps was quite straight forward right?

Make sure you read whatever presented in your screen during upgrade, reboot, console access, etc. Then you don't need to get back to this page (or even consult the upgrade manual). Except when your circumstances are totally unique, and the upgrade forces you to reinstall the whole system.

Hope this article helps enlightening the path for those looking for VMWare Server upgrade to 2.0.

Feedback to VMware team:

• Good job! The access to management console is now simplified. Even though I am wondering that now seems like many management console really goes to web-based
• If there is a way to restart the browser after the vmrc plugin, it will be awesome. Especially the IE-based admins. The intention to provide more hand exercise on re-running IE might be a good idea, but the rest will complaint that all IE instances are shut down right after the plugin installation.
• The VMware tools for linux has warning messages that shows if the kernel headers might have been altered or slightly changed from the original state -> that's good. But, does this mean the team at VMware were unable to find what went wrong? The vmware tools installed properly anyway, and this saves VMware team in case it doesn't work due to the warning messages (tricky, but smart way to save vmware some support call)
• The web-based management console provides further information on getting the commercial version of VMware product ->nice strategy! Or is this one reason that you folks thought of using browser based? So new update and offering can be framed within the management console? Niceeee
• One last thing: which one is the correct spelling: VMWare or VMware? I thought I always read it with capital 'W'?