Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

Applying Update Rollup 2 (UR2) to OpsMgr 2012 SP1

Applying Update Rollup 2 (UR2) to OpsMgr 2012 SP1

  • Comments 33
  • Likes




Update Rollup 2 (UR2) for OpsMgr 2012 SP1 has shipped.  This post will be a simple walk-through of applying it.  This hotfix is included on my Hotfix page for SCOM:


Description and download location:

Description of fixes in this release: 

  1. The Web Console performance is very poor when a view is opened for the first time.
  2. The alert links do not open in the Web Console after Service Pack 1 is applied for Operations Manager.
  3. The Distributed Applications (DA) health state is incorrect in Diagram View.
  4. The Details Widget does not display data when it is viewed by using the SharePoint webpart.
  5. The renaming of the SCOM group in Group View will not work if the user language setting is not "English (United States)."
  6. An alert description that includes multibyte UTF-8 characters is not displayed correctly in the Alert Properties view.
  7. The Chinese (Taiwan) Web Console displays the following message even after the SilverlightClientConfiguration.exe program is run:  Web Console Configuration Required.
  8. The Application Performance Monitoring (APM) to IntelliTrace conversion is broken when alerts are generated from dynamic module events such as the Unity Container.
  9. Connectivity issues to System Center services are fixed.
  10. High CPU problems are experienced in Operations Manager UI.
  11. Query processor runs out of internal resources and cannot produce a query plan when you open Dashboard views.
  12. Path details are missing for "Objects by Performance."

Unix and Linux fixes:

  1. The Solaris agent could run out of file descriptors when many multi-version file systems (MVFS) are mounted.
  2. Logical and physical disks are not discoverable on AIX-based computers when a disk device file is contained in a subdirectory.
  3. Rules and monitors that were created by using the UNIX/Linux Shell Command templates do not contain overridable ShellCommand and Timeout parameters.
  4. Process monitors that were created by the UNIX/Linux Process Monitoring template cannot save in an existing management pack that has conflicting references to library management packs.
  5. The Linux agent cannot install on a CentOS or Oracle Linux host by using FIPS version of OpenSSL 0.9.8.

This Update Rollup is also required if you want to use the new System Center Advisor Connector:


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, I don’t really recommend using Windows Update in general.  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. 




You’ll notice some of these updates are a LOT bigger than the previous ones in UR1.

I also notice there is now an update for the “Console” which is new from UR1.  The original release of UR2 was missing the update for the Gateway, which is now included and available to make UR2 truly “cumulative”.

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


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. 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.

***Note:  One of the things you will notice – is that there is no update available for reporting servers.  We will skip the reporting role. 




My new list looks like:

  • Management servers
  • Gateway servers
  • Web console server role computers
  • Operations console Role Computers

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:

    (The Unix/Linux MP location isn't available, and the previous location hasn’t been updated yet.  So this part is still under investigation as well.  I will update this section when I clear this part up)

  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 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

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:



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. 



Next up – run the Web Console update:


This runs much faster.   A quick file spot check:



Lastly – install the console update:



Well, this one required a reboot.  The KB article instructed “If you do not want to restart the computer after you apply the console update, close the console before you apply the update for the console role.”  However – my console was closed….. so you had better prepare that these files might be locked and require a reboot.



After the reboot – a quick file spot check:




I now move on to my additional management servers, applying the server update, then the console update.  My additional management servers did not require a reboot after the console update.


Next, I update the gateways.   


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\



Then I will spot check the DLL’s:









Manually import the management packs?


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



These 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.

Apply the agent update


Approve the pending updates in the Administration console for pushed agents.  Manually apply the update for manually installed agents.


100% success rate.

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



***Note!  The agents behind a gateway are NOT placed into pending actions for an update.  These agents will need to be “repaired” via the administration console, or use Windows Update.  On my agents behind a GW – a repair worked perfectly.



Update Unix/Linux MPs


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

(The link in the KB article doesn’t work at the time of this writing – here is the correct link)


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.

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.4199.0)

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



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


You will likely observe high CPU utilization of your management servers during these MP imports.  Give it 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:





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




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.




Known issues:

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


1.  Agents behind a Gateway will not be placed into pending management for an update.  If you are using Windows Update/WSUS/SCCM to update your agents, then no steps are necessary, as they will receive the agent update automatically.

2.  OM12 SP1 UR#2 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
  • Savision.LiveMaps.Presentation.SummaryWidget.WebConsole.mpb (Version

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

  • Hi and thanks for a great post as Always.

    The KB also states to update the web.config so I did that as well.



  • If there is no Gateway update, from where the agents that reports to a Gateway are going to take the upgrade?

    What I did  I copied form a Managemt Server the folders C:\Program Files\System Center 2012\Operations Manager\Server\AgentManagement\amd64 and x86 to the Gateway Server folder C:\Program Files\System Center Operations Manager\Gateway\AgentManagement

  • That's a GREAT point and I will run that one up the chain.

  • Kevin - have you read / heard anything about UR5 (KB2822776) that is out there?

  • @Scott -

    UR5 is only for customers still running SC 2012 RTM (non-SP1).  UR2 is the most current for SC 2012 SP1.  My recommendation to all customers would be to move to SC 2012 SP1, unless there is something that is holding back the ability to upgrade.

  • Anyone after deploying cu2 with the same Problem in the Webconsole?

    Please provide the following information to the support engineer if you have to contact Microsoft Help and Support :

    System.Reflection.ReflectionTypeLoadException: [ReflectionTypeLoad_LoadFailed]


    Debuggingressourcen-Zeichenfolgen sind nicht verfügbar. Oft enthalten der Schlüssel und die Argumente genügend Informationen zur Diagnose des Problems. Weitere Informationen erhalten Sie unter

      bei System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)

      bei System.Reflection.RuntimeModule.GetTypes()

      bei System.Reflection.Assembly.GetTypes()

      bei Microsoft.EnterpriseManagement.Presentation.DeclaredAssemblyLoader.LoadModuleCatalogFromAssembly(IModuleCatalog bootstrapperCatalog, ModuleCatalog catalog, Assembly assembly)

      bei Microsoft.EnterpriseManagement.Presentation.DeclaredAssemblyLoader.CreateModuleCatalog(IEnumerable`1 assemblies)

      bei Microsoft.EnterpriseManagement.Presentation.DeclaredAssemblyLoader.LoadInternal(IEnumerable`1 assemblies)

      bei Microsoft.EnterpriseManagement.Presentation.DeclaredAssemblyLoader.Load(DeclaredAssembly assembly)

      bei Microsoft.EnterpriseManagement.Monitoring.Components.ComponentRegistry.<>c__DisplayClass38.<GetAssemblies>b__36(DeclaredAssembly declaredAssembly)

      bei System.Reactive.Linq.Observable.<>c__DisplayClass413`2.<>c__DisplayClass415.<Select>b__412(TSource x)

  • One of the fixes included in this UR was for alert links not opening in the web console after SP1 applied.  I had that issue prior to the update.  Alert links would just spin and spin and never open in the web console.  After this update I'm not getting 500 Internal Server Error messages when trying to load alert links.  Does anybody have any ideas as to how to fix this?

  • Sorry, that should be I'm NOW getting 500 Internal Server Error messages....

  • I'm also getting the same "System.Reflection.ReflectionTypeLoadException" error in my web console after UR2. A remove/reinstall of the component didn't make a difference.

  • Never mind.  I figured it out.  It was my mistake.

  • SCOM_guy  what was your mistake?  Maybe I have the same issue.  We've been wrestling with the Web Console as well throuout the versions and upgrades....and general patches.  It workls, then it doesnt , we reininstall everything, it works again then it doesnt.

  • Are there any hints, solutions or workarounds for the "System.Reflection.ReflectionTypeLoadException" problem?

    remove/install do not fix my problem, too! same as David Gallay!

    Anybody more with the Problem?

    @Kevin: have you heard somthing about a problem like this?

  • Hi Kevin,

    We are still using SCOM 2012 RTM and going to upgrade to SP1. In the UR2 (KB2802159), it says "Do not install the update rollup package immediately after you install the System Center 2012 SP1 server. Otherwise, the Health Service state may not be initialized."

    Question here:

    1. How long shall I wait after SP1 upgrade to install this UR2?

    2. Is it okay to leave agents (both Windows agents and Linux agents) at 2012 RTM level and upgrade directly to SP1 UR2 level?


  • Hello Kevin,

    Can I apply CU2 on SCOM 2012 SP1 directly? Without applying CU1 at all?



  • @Cannonballflyer

    No - I don't have any info on that specific error.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs