With the Beta program for Virtual Server 2005 SP1 (as it was named when released to the web) having come to a close last week, and the imminent release of Virtual Server 2005 R2, here's run through of the steps to get you to the production release.
Critically, saved state information (.VSV) is not compatible between builds of Virtual Server 2005. Therefore, to ensure no data is lost, saved state data must be removed from the equation by shutting down each guest currently running. In addition, any guests sitting on the shelf in a saved state must either be restored and shutdown.
Take a backup of files relating to your Virtualised environment. This falls into two categories - those for guests themselves, and those for the Virtual Server configuration.Guests: - .vmc, .vhd, .vud (Configuration, Hard Disks & Undo drives respectively)Virtual Server: - .vnc files (Virtual Network Configuration) - Options.xml (Site config under Documents and Settings\All Users\Application Data\Microsoft\Virtual Server
If you are running the Virtual Server 2005 SP1 Beta software, you must uninstall it fully. [For MSFT employees reading this with access to later Virtual Server 2005 R2 internal builds, this applies equally as well]. Upgrades are not supported from any beta or pre-releases. This also applies if you are using the Trial Version of Virtual Server 2005.
To remove Virtual Server 2005:
At this point, for a production server, I would strongly recommend you now consider installing Windows Server 2003 SP1 if you have not already done so. Upgrades from Virtual Server 2005 as released last year are supported and you do not need to complete the uninstall first. The upgrade is treated as per a fresh install. Full information on this is well documented in the Virtual Server 2005 R2 Release Notes. For reference purposes, after installation, these will also be available in \Program Files\Microsoft Virtual Server\Documentation\relnotes.htm
Virtual Machine Additions Update
For optimal performance, you must ensure the latest version of the Virtual Machine additions are installed in each and every guest.
Are the new addtions also compatible with Virtual PC, and are they 'Vista' friendly?
Thanks in Advance
Hi - There _should_ be no problem using these additions under Virtual PC, although I haven't tried it yet (and FYI, neither do the product group). However, officially, only the additions provided with Virtual PC are supported.
Excellent post. I've got a number of VS2005 B1 machines in need of an upgrade... and this post will come in handy. Now if I could just get the R2 bits off MSDN I'd be a happy camper. Keep up the good posting - and thanks for the link ;)
I just installed windows 7 and it seems like the virtual server 2005 r2 doesn't work. How do i go about making the VS Comply with windows 7
Solomon - VS is not supported on Windows 7.