Step-by-Step – SCOM 2012 R2 Update Rollup 12 (UR12) Install Procedure

My personal notes for installing SCOM 2012 R2 Update Rollup 12, Step-by-Step. UR12 (Update Rollup) has a lot improvements, please see below the many updates being provided in this UR. One thing to mention, UR12 also has resolved an issue with respect to Reporting — please see notes below. Also, it is rather nice to see updates (still) being pushed out for SCOM 2012R2 along with other System Center 2012 products.

It is highly recommended to upgrade your lab/Dev environments first before upgrading your Production environment(s). The step by step procedures below are the steps I took and in no way shape or form do I accept responsibility for any data loss, and/or issues within your environment. It is advised to always take a backup of your SQL databases and/or snapshots of your SCOM environment(s). Please take these notes as suggestions. Always refer to Microsoft’s KB (posted below) for full documentation steps.

7

Here are the key updates for UR12 (source Microsoft):

Issues that are fixed in Operations Manager Update Rollup 12

  • When you try to upgrade System Center 2012 R2 Operations Manager Reporting Server to System Center 2016 Operations Manager reporting server, the upgrade fails for the following configuration:
      • Server A is configured as System Center 2012 R2 Operations Manager including Management Server.
      • Server B is configured as System Center 2012 R2 Operations Manager, including Operations Manager Database (OpsMgrDB), Operations Manager Data Warehouse (OpsMgrDW) and Operations Manager Reporting Server.
  • Recovery tasks on “Computer Not Reachable” messages in the System Center Operations Manager Monitor generate failed logons for System Center Operations Manager Agents that are not part of the same domain as the Management Groups.
  • When a Management Server is removed from the All Management Servers Resource Pool, the monitoring host process do not update the Type Space Cache.
  • SHA1 is deprecated for the System Center 2012 R2 Operations Manager Agent and SHA2 is now supported.
  • Because of incorrect computations of configuration and overrides, some managed entities go into an unmonitored state. This behavior is accompanied by event 1215 errors that are logged in the Operations Manager log.
  • IntelliTrace Profiling workflows fail on certain Windows operating system versions. The workflow cannot resolve Shell32 interface issues correctly.
  • There is a character limitation of 50 characters on the custom fields in the notification subscription criteria. This update increases the size of the limitation to 255 characters.
  • You cannot add Windows Client computers for Operational Insights (OMS) monitoring. This update fixes the OMS Managed Computers wizard in the System Center Operations Manager Administration pane to let you search or add Windows Client computers.
  • When you use the Unix Process Monitoring Template wizard to add a new template to the monitor processes on UNIX servers, the monitored data is not inserted into the database. This issue occurs until the Monitoring Host is restarted

Install Procedure

Once you are ready to begin your upgrade, it is recommend you do the following server/roles in the order below:

  1. Install the update rollup package on the following server infrastructure:
  • Management server or servers
  • Audit Collection Services
  • Gateway servers
  • Web console server role computers
  • Operations console role computers
  • Reporting Services
  • Agent Updates
  1. Apply SQL scripts.
  2. Manually import the management packs.
  3. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

Once you have downloaded the rollup files, I like to extract and only keep the language I need, in this case, ENU (English). You will need to install these with Administrative rights, I like to use PowerShell as Local Administrator. It really does frustrate me, as there is no indication that the rollup installed correctly, (other than looking at the file version number change via File Explorer).

1

2

Personally, I prefer to execute the MSP files via PowerShell (RunAs Administrator) console.

Again, the order needs to be:

  1. Management Servers
  2. Audit Collection Services
  3. Gateway Servers
  4. Web Console Role Servers
  5. Operations console role computers
  6. Reporting Services
  7. Agent Updates

Once the updates are installed, server(s) are rebooted, etc., you will now need to apply the SQL scripts. First update the Data Warehouse, then followed by the OpsMgr DB.

The scripts can be found here, “%SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\SQL Script for Update Rollups

Please note, the user executing these scripts needs to have read and write permissions to the database(s).

Execute the SQL queries in the following order:

  1. UR_Datawarehouse.sql
  2. update_rollup_mom_db

3

4

5

 

Once you have successfully executed the SQL scripts, you will now need to import the updated Management Packs (MP). These MPs can be found here, “%SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups“.

You will need to import the following MPs, please see below:

  • Microsoft.SystemCenter.TFSWISynchronization.mpb, which has the following dependencies:
    • Microsoft.SystemCenter.AlertAttachment.mpb, which should be installed from the System Center Operations Manager 2012 R2 media.
    • Microsoft.SystemCenter.Visualization.Library.mpb
  • Microsoft.SystemCenter.Visualization.Component.Library.mpb
  • Microsoft.SystemCenter.ClientMonitoring.Library.mp
  • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
  • Microsoft.SystemCenter.ClientMonitoring.Views.Internal.mp
  • Microsoft.SystemCenter.Apm.Infrastructure.mpb
  • Microsoft.SystemCenter.Apm.Library.mpb
  • Microsoft.SystemCenter.Apm.Library.Resources.(LANGUAGECODE_3LTR).mpb
  • Microsoft.Windows.InternetInformationServices.2016.mp (this MP has to be downloaded separately from the Microsoft Update Catalog) which has the following dependency:
    • Microsoft.Windows.Server.2016.Discovery.mp (this MP has to be downloaded separately from the Microsoft Update Catalog)
  • Microsoft.SystemCenter.Visualization.Library.mpb
  • Microsoft.SystemCenter.Advisor.mpb
  • Microsoft.SystemCenter.Advisor.Internal.mpb
  • Microsoft.SystemCenter.2007.mp
  • Microsoft.SystemCenter.Advisor.Resources.(LANGUAGECODE_3LTR).mpb
  • Microsoft.SystemCenter.SyntheticTransactions.Library.mp
  • Microsoft.SystemCenter.OperationsManager.Library.mp
  • Microsoft.SystemCenter.OperationsManager.Internal.mp
  • Microsoft.SystemCenter.Apm.Web.IIS10.mp, which has the following dependencies:
  • Microsoft.SystemCenter.ClientMonitoring.Internal.mp, which has the following dependency:
  • Microsoft.SystemCenter.OperationsManager.AM.DR.2007.mp

 

6

Once the MPs have been imported, you should now go back to your Pending Management view, under the Administrations pane, and update all servers.

8

And that is that! You are now on the latest and greatest System Center release for SCOM 2012 R2 Update Rollup 12!

Advertisements

6 thoughts on “Step-by-Step – SCOM 2012 R2 Update Rollup 12 (UR12) Install Procedure

  1. Does this Fix Data Warehouse issues as Im UR11 currently and have many critical alerts:

    Data Warehouse Event Data Collection Writer Recovery State
    Processing Backlogged Events Taking a Long Time.

    Like

  2. I updated to UR 12 for SCOM 2012 R2 and I did not have any agents update. I did run the update from a command prompt run as administrator. The agents are monitoring 2008 R2 serves. The agent version is 7.1.10184.0 is this the correct version or do they need a upgrade?

    Like

    1. Hi Mike, that is odd, you should have been required to update the MMA agents to UR12. Were the agents installed manually or deployed via console? After applying UR12, your build version should be, “7.1.10226.1304”.

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s