Update on System Center 2012 SP1 Update Rollup 2 (UR2) for Virtual Machine Manager

Update on System Center 2012 SP1 Update Rollup 2 (UR2) for Virtual Machine Manager

  • Comments 7
  • Likes

Posted on behalf of Carmen Summers

Greetings All,

This is Carmen Summers and I lead System Center Cloud and Datacenter Management Sustained Engineering.  I wanted to take the time to announce we are making an addition to System Center 2012 SP1 Update Rollup 2 and convey some important information regarding this addition. 

As of April 23rd we are adding Update Rollup 2 for System Center 2012 SP1 Virtual Machine Manager to System Center 2012 SP1 Update Rollup 2 release.  I have heard your feedback in the past that you all don’t prefer when we add content to Update Rollup releases in a delayed manner like we are doing and I agree with you.  We have been working very hard to avoid this over the past year, but in this circumstance we felt compelled to make an exception and add the content as opposed to making our customers wait until the next Update Rollup release window.   Please accept my apologies for this late addition and thank you in advance for your patience and understanding.

The master KB article for  System Center 2012 SP1 Update Rollup 2 has been updated to reflect the summary of issues and installation instructions for Update Rollup 2 for System Center 2012 SP1 – VMM.  You can refer to it here

Important actions for Update Rollup 2 for System Center 2012 SP1- Virtual Machine Manager

In order to install Update Rollup 2 package for System Center 2012 SP1-  Virtual Machine Manager, you will need to uninstall Update Rollup 1 for System Center SP1 - Virtual Machine Manager package from your system. 

- If you download Update Rollup 2 package for System Center 2012 SP1 Virtual Machine Manager from Microsoft Update Catalog and install Update Rollup 2 without un-installing Update Rollup 1  you should un-install Update Rollup 2 package for Virtual Machine Manager and then un-install Update Rollup 1 for System Center 2012 SP1 - Virtual Machine Manager via control panel. 

- If you are using WSUS to update System Center 2012 SP1 - Virtual Machine Manager and you have already installed Update Rollup 1 for System Center 2012 SP1 – Virtual Machine Manager then you will not receive Update Rollup 2 notification until Update Rollup 1 is uninstalled.

Why is this necessary?

When Update Rollup 2 is applied to a system which is running System Center 2012 SP1 Virtual Machine Manager with UR1, the installer does not patch files correctly. This is caused by the way UR 1 was packaged. As such the product fixes in UR1 are correct; it is the packaging of UR1 that causes this issue. If you do not need UR2, then you should continue to operate with UR1.   However, if you choose to stay on Update Rollup 1 for System Center 2012 SP1 Virtual Machine Manager and a later Update Rollup is released that you need to implement you will still need to remove Update Rollup 1 first.

We apologize for any inconvenience this causes your organization.  We have performed root cause analysis on the issue and have processes in place to prevent future recurrences of this situation. 

Carmen Summers

System Center, CDM Sustained Engineering Lead

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • ouch...I'm assuming that ru1 will have the same impact on all future rollups?

  • This is unbelievable! And, no, it's not necessary if you did the updates properly in the first place.

  • Here are the command lines to uninstall both UR1 and UR2 (in case you need to roll back a faulty installation sequence). Handy for Server Core deployment or scripts.

    %SystemRoot%\System32\MSIExec.exe /Package {CDFB453F-5FA4-4884-B282-F46BDFC06051} /Uninstall {392CA022-BA3C-42BC-9865-B19924804A19}

    %SystemRoot%\System32\MSIExec.exe /Package {59518B15-FC64-4CF9-A4D1-0EE1B4A63088} /Uninstall {B20D25E4-A501-4420-A507-B3C22F93621E}

    %SystemRoot%\System32\MSIExec.exe /Package {CDFB453F-5FA4-4884-B282-F46BDFC06051} /Uninstall {32A2C205-610D-4C45-B5C0-ADC606346D2E}

    %SystemRoot%\System32\MSIExec.exe /Package {59518B15-FC64-4CF9-A4D1-0EE1B4A63088} /Uninstall {4EA74929-330D-49EC-B8EC-8A3219869A62}

  • Thanks for the instructions, they worked perfectly.  It's a shame that I had to go here to find out about it.  Why weren't they on the KB article about UR2?

    Also, after installing UR2 I needed to move the database to a different SQL server.  I went to uninstall SCVMM with the keep database option and was greeted with a message saying that I can't upgrade to 2012 SP1 without uninstalling 2012 with no service pack.  There was no way to get past the message.  I managed to fix it by uninstalling UR2.  After that I was greeted with the normal uninstall wizard.

  • We have an issue when updating VMM Agent on Perimeter Network Host Machine.

    what is the process of updating Perimeter Network Hosts?

  • This pertains to update rollup 3, but do we need to manually update each client agent and also manually add the update for every new P2V, V2V, and template?

  • never mind...answered my own question