Check out the posting on the Windows Virtualization Team blog here for more details.

As usual its a one way upgrade process.  Once you go forward there is no coming back! :)

Hyper-V RC0 to RC1 Upgrade Considerations
*Saved-state files are not supported between RC0 and RC1 releases of Hyper-V.  All virtual machine saved states should be discarded before upgrading to RC1, or prior to resuming virtual machines after upgrading to Hyper-V RC1. 

*Online snapshots contain virtual machine save-states and thus online snapshots taken with Hyper-V RC0 are not supported after updating to Hyper-V to RC1.  Either apply any online snapshots and shut down the VM or discard the virtual machine save state associated with the snapshot before or after the update to Hyper-V RC1.

*System Center Virtual Machine Manager 2008 Beta does not support Hyper-V RC1.

*New Integration Components (ICs) must be installed for your supported guest operating systems.  Integration Components are specific to the build of Hyper-V.  RC1 Integration Components for all supported Windows Operating Systems are provided using the ‘Action’ -> ‘Insert Integration Services Setup Disk’ action.

RC1 Integration Components for all supported Windows Operating Systems are now part of the IC Setup Disk.  This now includes Windows Server 2008!  Simply install the Hyper-V RC1 Integration Components for Windows Server 2008 the same way you do all other Windows ICs (‘Action’ -> ‘Insert Integration Services Setup Disk’). 
Note You need to close the found new hardware wizard before setup will begin on all Windows Operating Systems.

Improvements Over Hyper-V RC0
In addition to bug fixes and stability improvements we also made some additional changes largely based on feedback from customers, I might have missed a few I’ll add to this list if so…
   *Integration Components For Windows Server 2008 guest’s included in Integration Services Setup Disk
   *New Graphics for Hyper-V Manager and Virtual Machine Connection – including a “Now” icon in the snapshot pane
   *IPv4 Address Migration - when creating a new Virtual Network bound to an adapter with a static IPv4 address the IPv4 settings are migrated to the new virtual adapter

I'm just about to update my own Hyper-V installation so fingers crossed.

Since Vista RTM’d people have complained to me about UAC (User Account Control) and how often they get warnings and popup’s.  They just never seemed to get the point of it.  I leave it on for all my Vista machines, even the VMs and even during demos to customers.  Why?  Easy.  It protects my system from drive by style installations or modifications to my Vista machines.  Its never really proven to be a hindrance to me, even during demos.

A colleague of mine tipped me off to the following articles.

PCWorld

Reading them was quite interesting.  Tests showed that with UAC on, root kits couldn’t install themselves on Vista without alerting the user.  No silently slipping onto the OS.  However, its the comments at the end of each article that really intrigue me.  Some people think Microsoft use UAC as a way of avoiding responsibility.  Others, and rightly so in my mind, point out that the best you can do is warn/alert a user that something is attempting to modify their system … but if they don’t take the time to even read what’s on screen malware will always find its way onto a system.  Software will always have its flaws.

UAC isn’t just about stopping malware … its about protecting users from themselves.  It would appear that you can lead a horse to water but you cant’ stop it clicking continue, ok, yes I’m sure, no problem and diving right in.

The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of Microsoft. These posts are just the ramblings of few nerds. Inappropriate comments will be deleted at the authors discretion. All code samples are provided "AS IS" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. This means don't run the scripts blindly without testing. Be sure to take the appropriate backup/backout precautions before making ANY change to production systems.  You have been warned!

Here is a great post from James O'Neill.

http://blogs.technet.com/jamesone/archive/2008/03/13/expensive-hypervisors-a-bad-idea-even-if-you-can-afford-them.asp

As Microsoft get ready with Hyper-V, VMware are beginingg their marketing blitz in an attempt to justify their pricing.  As James points out in his post you can manipulate figures to come to any conclusion you want ... even if its way off base.  Microsofts Hyper-V will cost a fraction, per socket, when compared to VMWare.  While the VMWare products are slightly more mature Hyper-V is only a small part of the Virtualisation offering from Microsoft.  Windows Server 2008 really brings Mircosoft virtual offerings to the forefront as an end-to-end solution.  Check out http://www.microsoft.com/virtualization/default.mspx for more details.