Tips for upgrading from SP1 beta to SP1 release candidate

Tips for upgrading from SP1 beta to SP1 release candidate

Rate This
  • Comments 4


Well, I have finished upgrading all of my Hyper-V servers from the SP1 beta release to the SP1 release candidate – so I thought I would share some notes from my experience.

Unfortunately you cannot go directly from the beta release to the release candidate – instead you need to uninstall the beta (taking your system back to RTM) and then install the release candidate.  This requires some special planning when it comes to virtual machines with Dynamic Memory or RemoteFX enabled.

Hyper-V on the RTM release of Windows Server 2008 R2 does not understand how to read the configuration of a virtual machine which has either of these features enabled.  Once you have uninstalled the beta release of service pack 1 – opening the Hyper-V manager will not show any virtual machines which had these features enabled – and if you check the event log you will see entries like this:

image

Nothing untoward has happened to the virtual machine – and once you install the release candidate build the virtual machine will magically return.

That said – there are two specific things you should check for before beginning the process:

  • Dynamic Memory / RemoteFX should be disabled on critical infrastructure virtual machines. 

    In my case I had to disable Dynamic Memory on my domain controller before attempting the update.  If I had not done this my domain controller would not have come up when I uninstalled the beta – and I would have been in quite a bind.

  • Check to make sure that there are no virtual machines that have Dynamic Memory / RemoteFX disabled – but have snapshots where these features are enabled.

    It is okay to have snapshots present on virtual machines, it is even okay to have a mix of snapshots with these features enabled or disabled, but there is a problem that specifically happens if you have a virtual machine that has Dynamic Memory / RemoteFX disabled – but has snapshots where these features are enabled.  In this case the RTM version of Hyper-V will successfully load the virtual machine configuration – but will fail to load all the snapshots.  This can result in corruption of the missing snapshots.

After you have checked these two items the process is fairly straight forward:

 

  • Uninstall SP1 beta

    • To do this you should first open the Control Panel
    • Then select Uninstall a Program (or Programs and Features if you have changed the default view of the Control Panel)
    • Then select View installed updates
    • After this select the entry labeled Service Pack for Microsoft Windows from under the Microsoft Windows section
    • Finally click Uninstall
    • After a period of time (and a reboot) your system will be back to the RTM release

  • Install SP1 release candidate

    • This is pretty simple – so I will not detail the steps

  • Update integration services on all your virtual machines

Cheers,
Ben

Leave a Comment
  • Please add 2 and 1 and type the answer here:
  • Post
  • Hi! Thanks for thorough describing update process from SP1 Beta to RC from Hyper-V point of view. Haven't mentioned it's these EventID=16302 error messages in Event Log.

    Some other questions came to my mind:

    1) is it needed to uninstall RemoteFX in Role Services for Remote Desktop Services in Server Manager before uninstalling SP1 Beta?

    2) one system hasn't got RemoteFX installed but got some unusual video bugchecks 116, 117, 119 after uninstall rebooted. So uninstall process was reverted back automatically and I needed to investigate memory dumps to figure out the reason. It happened to be Intel HD driver igdkmd64.sys (dated 03.30.2010). After uninstalling the driver, SP1 was removed successfully. Do you think, Windows team needs these memory dumps?

    By the way, I've signed up with WUSignUpTool_xNN.exe and updated both Win7 client and server directly from Microsoft Update as descibed on social.technet.microsoft.com/.../ad7e6b66-1d0b-49f3-83c2-b15903a94d7e

    That counted in additional 37-45 megabytes to current RTM updates only.

  • Hi Ben

    Thanks for the tips.  For info, all runs sweet on my Windows Server Core 2008R2 box for this as well.  As noted boxes with Dynamic Memory enabled don't show in RTM but did magically reappear once the RC was installed.

    For info. for others reading, to see updates within Windows Server 2008 R2 Core, or Hyper-V Server 2008 R2, use:

    wmic qfe

    to uninstall the service pack on these servers use

    wusa /uninstall /kb:976932

    where 976932 is the KB number for SP1 for Windows Server 2008 R2/Windows 7

    as an aside these commands also work on full GUI enabled versions as well :o)  oh and WMIC is a very handy tool...

    eg

    wmic qfe where (installedon like "10/%/2010") get hotfixid,installedon

    Shows all updates installed for October, and only lists the hofixid and the date installed on.

    Cheers

    Janson

  • IL -

    No, you do not need to uninstall the RemoteFX role - and will appear magically after applying the RC.  I do not know what would cause the video issues - but as long as you send crash reports to Microsoft automatically they will go to the right place.

    Janson -

    Thanks for the extra info!

    Cheers,

    Ben

  • Where to download SCVMM 2010 SP1 RTM ???

Page 1 of 1 (4 items)