Applying Update Rollup 3 (UR3) to OpsMgr 2012 SP1


Update Rollup 3 (UR3) for OpsMgr 2012 SP1 shipped originally several months back.  I took a cautious approach to this update, as there were some components pulled early for DPM (all have been resolved).  Does not look like anything was an issue in SCOM, beyond the known issues documented at the bottom of this article.  This post will be a simple walk-through of applying it.  This hotfix is included on my Hotfix page for SCOM:  http://blogs.technet.com/b/kevinholman/archive/2009/01/27/which-hotfixes-should-i-apply.aspx

This update is CUMULATIVE.  It includes the updates that were in UR1 and UR2 for System Center Operations Manager 2012 SP1.  It can be applied to System Center Operations Manager 2012 SP1 (as released) or a SCOM 2012 SP1 deployment that has had UR1 or UR2 already applied.

Description and download location:

http://support.microsoft.com/kb/2836751

Description of fixes in this release:

  1. The Audit Collection Services (ACS) dtPrincipal tables sometimes are missing a user’s domain name.
  2. If you decide to see more than two days’ worth of data in a Service Level Dashboard view, the data is displayed from the Daily Aggregated data and does not contain the last two days’ worth of data.
  3. The Health Service stops collecting performance data on Windows Server 2008 R2.
  4. The web console crashes when the Active Alerts view and the Windows Computer State view are accessed at the same time when Internet Explorer 9 is used.
  5. A memory leak may occur in the console when the performance widgets dashboard is left open.
  6. When the Operator role is used, many 26319 events are generated. This causes performance problems.
  7. Health Service availability reports are incorrect because of duplicate entries in the HealthServiceOutage table.
  8. When the Orchestrator Integration pack is under a high-load scenario, a software development kit (SDK) process deadlock may occur.
  9. This update includes fixes to the following Advisor Connector issues:  Group opt-in, Microsoft System Center 2012 Operations Manager gateway and Microsoft monitoring. Windows PowerShell cmdlets, Health state, Microsoft Knowledge Base article links in Operations Manager console alerts

Unix and Linux fixes (via MP Update):

  1. The Solaris agent cannot be installed on Solaris 11.1 because it does not find the prerequisite OpenSSL package.
  2. Knowledge editing pages are not displayed when monitors that were created by the Shell Command templates are edited.
  3. Log files that are encoded in schemes other than ASCII cannot be monitored.

That’s a LOT.  Looks like some very important ones as well…. so lets get this one tested in our labs!

Download the update:

You can get this update “partially” applied by using Windows Update.  However, since there are manual steps involved, and a specific recommended order of operations, management packs, a SQL script…. I don’t always recommend using Windows Update for a complete update to the infrastructure.  It is certainly an option, however.

To download all of the updates, you will need to click the link in the KB above, which will launch the catalog for the individual downloads. 

image

I also notice there is now an update for the “ACS” which is new from UR2. 

Add these to your “basket” then “view basket” and choose a download location to download them all.

Build a plan:

Following the KB – the installation plan looks something like this:

  1. Install the update rollup package on the following server infrastructure:
    • Management server or servers
    • Gateway servers
    • Reporting servers
    • Web console server role computers
    • Operations console role computers
  2. Run Data Warehouse SQL script
  3. Manually import the management packs.
  4. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

***Note:  The release notes are pretty poor here.  One of the things you will notice – is that there is no update available for reporting servers.  We will skip the reporting role.  Additionally, there is an update for ACS, however the documentation makes no mention of when this should be applied.  I will add this ACS step to be done just after the Management server update.

My new list looks like:

  1. Install the update rolloup:
    1. Management servers
    2. Audit collection collector server
    3. Gateway servers
    4. Web console server role computers
    5. Operations console Role Computers
  2. Run Data Warehouse Script
  3. Manually import the management packs.
  4. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

Since I am monitoring Linux systems, I’ll need to add steps for that from the KB:

  1. Download the updated management packs from the following Microsoft website:

    http://www.microsoft.com/en-us/download/details.aspx?id=29696

  2. Install the management pack update package to extract the management pack files.
  3. Import the following:
    • The updated Microsoft.Unix.Library management pack (from the Microsoft.Unix.Library\2012 SP1 folder)
    • The updated Microsoft.ShellCommand.Library management pack bundle  
    • The Microsoft.Unix.Process.Library management pack bundle
    • The platform library management packs that are relevant to the Linux or UNIX platforms that you monitor in your environment
  4. Update the Unix/Linux agents

Seems simple enough, lets get started.

Install the update rollup package

On the catalog site, I add all the updates to my basket, and click View Basket, and Download.

Next I copy these files to a share that all my SCOM servers have access too.  These are actually .CAB files, so I will need to extract the MSP’s from these CAB files.

Once I have the MSP files, I am ready to start applying the update to each server by role.

***Note:  You MUST log on to each server role as a Local Administrator, SCOM Admin, AND your account must also have System Administrator (SA) role to the database instances that host your OpsMgr databases.

My first server is a management server, and the web console, and has the OpsMgr console installed, so I copy those update files locally, and execute them per the KB, from an elevated command prompt:

image

This launches a quick UI which applies the update.  It will bounce the SCOM services as well.  The update does not provide any feedback that it had success or failure.  You can check the application log for the MsiInstaller events for that.

You can also spot check a couple DLL files for the file version attribute. 

image

Next up – run the Web Console update:

image

This runs much faster.   A quick file spot check:

image

Lastly – install the console update:

image

A quick file spot check:

image

Secondary Management Servers:

I now move on to my second management server, applying the server update, then the console update, then in addition the ACS update. 

The ACS update actually provides feedback with a UI when it is complete.

Updating Gateways:

image

The update launches a UI and quickly finishes.

I do a spot-check to ensure the right files were dropped.  First I will check the Agent update files in C:\Program Files\System Center Operations Manager\Gateway\AgentManagement\

image

Then I will spot check the DLL’s:

image

Apply the Data Warehouse SQL Script

In the path on your management servers, where you installed/extracted the update, there is a SQL script file: 

  %SystemDrive%\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Rollups

Open a SQL management studio query window, connect it to your Operations Manager Data Warehouse database, and execute the script

image

Click the “Execute” button in SQL mgmt. studio:

You will see the following (or similar) output:

image

Manually import the management packs?

We have four updated MP’s to import  (MAYBE!).

image

The Alert Attachment and IntelliTrace MP bundles are only used for specific scenarios, such as Global Service Monitoring, or DevOps scenarios where you have integrated APM with TFS, etc.  If you are not currently using these MP’s, there is no need to import or update them.  The Intellitrace MP will actually fail to import of you are not using these, because of a dependency.  I’d skip this MP import unless you already have these MP’s present in your environment.

However, the Image and Visualization libraries deal with Dashboard updates included in UR3, and these need to be updated.

Apply the agent update

Approve the pending updates in the Administration console for pushed agents.  Manually apply the update for manually installed agents.  ***Note – you can approve the updates in bulk, but all agents selected in a single approval must be assigned to the same management server.

image

100% success rate.

Be sure to check the “Agents By Version” view to find any agents that did not get patched:

image

Update Unix/Linux MPs and Agents

Next up – I download and extract the updated Linux MP’s for SCOM 2012 SP1 UR2

http://www.microsoft.com/en-us/download/details.aspx?id=29696

7.4.3507 is SCOM 2012 SP1. 

7.4.4112.0 is SCOM 2012 SP1 with UR1.

7.4.4119.0 is SCOM 2012 SP1 with UR2.

7.4.4263.0 is SCOM 2012 SP1 with UR3.

Download the MSI and run it.  It will extract the MP’s to C:\Program Files (x86)\System Center Management Packs\System Center 2012 MPs for UNIX and Linux (7.4.4263.0)

Import all the files in the 2012 SP1 folder, and the following:

Microsoft.Unix.ConsoleLibrary.mp

Microsoft.Unix.Process.Library.mpb

Microsoft.Unix.ShellCommand.Library.mpb

Also add any platform specific MP’s for versions on Unix or Linux in your monitoring environment.

image

You will likely observe VERY high CPU utilization of your management servers during and immediately following these MP imports.  Give it plenty of time to complete the process of the import and MPB deployments.

Next up – you would upgrade your agents on the Unix/Linux monitored agents.  You can now do this straight from the console:

image

image

You can input credentials or use existing RunAs accounts if those have enough rights to perform this action.

image

Lastly – refer to the KB article for the UR1 update, as if you are a heavy user of Linux process monitoring using our template – additional steps are required to address the fixes.  You must open, edit, and re-save any process templates that you had previously created in order to apply the fixes to each.

Now at this point, we would check the OpsMgr event logs on our management servers, check for any new or strange alerts coming in, and ensure that there are no issues after the update.

image

Known issues:

See the existing list of known issues documented in the KB article.

Additional:

1.  OM12 SP1 UR#2/3 Web Console Error: System.Reflection.ReflectionTypeLoadException: [ReflectionTypeLoad_LoadFailed]  Savision has released updated versions of the Live Maps Summary Widget management packs that resolve this issue. The versions can be downloaded here. The download contains the following files:

  • Savision.LiveMaps.Presentation.SummaryWidget.Library.mpb (Version 1.2.1.0)
  • Savision.LiveMaps.Presentation.SummaryWidget.WebConsole.mpb (Version 1.2.1.3)

The problem should be fixed by importing the 2 management packs into your environment.

http://www.savision.com/resources/news/fix-om12-sp1-ur2-web-console

Comments (8)

  1. Anonymous says:

    Hi Kevin,

    We followed the same steps & implemented the UR3 in our environment. But agents are not popping up in the Pending Management view.

    Could you please help me on this?

    Sunil Kumar S

  2. Anonymous says:

    Hi Kevin,

    Thanks for the post.

    How about the section mentioned in the original article?

    •To enable the web console fixes, add the following line to the %windir%Microsoft.NETFramework64v2.0.50727CONFIGweb.config file:

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

    Regards,

    Tibor

  3. Kevin Holman says:

    @Tibor –

    You are correct – if that is applicable to your environment you should additionally make that change.  As far as I am aware – that modification has to do with FIPS compliance, so I am not 100% sure it would be necessary in all environments.

  4. Kevin Holman says:

    @ Philippe  –  good catch – I have added that step now.

  5. Philippe Augras says:

    Hi Kevin,

    I can't see anything in your article about the UR_Datawarehouse.sql script that is to be applied on the data warehouse database. Did I miss something ?

    Regards,

    P. Augras

  6. RHC says:

    Once again, thank you for a brilliant post.

  7. Raju' says:

    Hi Kevin,

    I installed Rollup 3 update in one of our Azure management group and found that discovery is not happening for the newly deployed MPs after that. Same azure MP is working fine on non-rollup3 management group. I would like to uninstall the rollup3 and check in production. Could you please let me know the steps to do that- Thanks!!

  8. NarenSV says:

    Hi Kevin,

    I could not find “UR7 for SCOM 2012 SP1 – Step by Step” from this blog. I applied UR7 by following steps from UR7 on SCOM 2012 R2.
    After I have applied successfully, few of the agents have been shown up in the Pending Management and approved. Some of the agents which were still needs to be updated the UR7 agent (apart from manually pushed agents).

    How to update the UR7 agent to the servers which are showing as “Remotely manageable as ‘Yes'”?
    I also did not run the ACS related and Gateway (since we don’t have a gateway server skipped gateway). How to verify whether ACS needs to be applied. Is it a mandatory or any dependency to be applied.

    We have to apply UR8, 9 & 10 as well. Can we skip updating the agents which were still with UR6 only and apply UR8? Please reply asap, as I need to proceed further.

    Thanks,
    Naren.

Skip to main content