Tuesday 8 May 2012

Updated Update Rollup 1 for System Center 2012

No sooner do I finish pushing out my SCOM agents do I then see that Microsoft have released Update Rollup 1 for Operations Manager.

Normally I'd be quite happy and plod along with getting the update installed, but hang on a second, this update looks very familiar.

The article that I saw referenced in the update announcement is KB2686249, the same one that I blogged about here a couple of weeks ago.

In fact, it is the very same update, just with Operations Manager 2012 added, along with the updated Virtual Machine Manager Management Packs.

Now I'm not one to moan (yeah, I'm not going to get away with that statement!) but updating an update without increasing the rollup/update number isn't exactly the best way to go about it in my opinion.  Does this mean when the ConfigMgr update is ready we'll see yet another addition to the Update Rollup 1 package but with no name change?

The only reason this probably half bothers me is that I'm in the middle of setting up my new testlab/customer experience center for work and having just updated VMM and App controller by using Windows Update for a change rather than pulling the file down manually and I'm now a bit perplexed as Windows Update is unable to find the SCOM update for the console that is installed on my VMM server (not that it finds it for the SCOM management server either via WU).

And then to make matters worse, there's a "known issue" with the update:
  • No updates items appeared in Control Panel ARP after installing Update Rollup 1 (UR1). After installing UR1 on server and all roles (except Agent and Gateway), no update item appears in Control Panel ARP list.
  • The version number of the console does not change after installing Update Rollup 1 in the UI. After installing Update Rollup 1 ,the version number of the console is still 7.0.8560.0 in the UI
  • Why is this a problem?  Well if you were planning to distribute the console update via ConfigMgr then you're going to have to fall back to file version checking for targeting and it makes it just that tad harder for verification checking when you can't just simply ask a user to check their console version by check "help about"

    I'm not going to blog about the whole installation order/methodology as Kevin Green has already written this up nicely here:

    One thing he doesn't mention though is that after installing the Web Console fix, the following line requires adding to the web.config file.

    From the KB Article:
    Web console fixes will work after adding the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:

    <machineKey validationKey="AutoGenerate,IsolateApps"
    decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

    The line should be added under <system.web>, as described in the following article in the Microsoft Knowledge Base:
    911722 (http://support.microsoft.com/kb/911722/ ) You may receive an error message when you access ASP.NET Web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0
    All in all, there are 17 core updates to SCOM, 3 for Unix/Linux Monitoring and a lovely new feature - Oracle Solaris 11 (x86 & SPARC) support included in this updated update so it's definitely one to go and install.

    The VMM & App Controller update parts are available either through Windows Update or from here:

    The Operations Manager update packages can be downloaded from here:


    Kevin Greene said...

    Cheers dude, blog post now updated :)

    Anonymous said...

    Thank you so much for providing this feedback. I appreciate your opinion on this and will make note of the feedback for System Center Sustained Engineering.