Applying CU1 to OpsMgr 2012 SP1






CU1 for OpsMgr has been released for some time now, this post will be a simple walk-through of applying it.  This hotfix is included on my Hotfix page for SCOM:

Marnix did a great posting on this topic as well, available here:


Description and download location:


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:



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 consoles, or for reporting servers.  So we will skip those roles as they are not applicable.  My new list looks like:

  • Management servers
  • Gateway servers
  • Web console server 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:

    System Center Monitoring Pack for UNIX and Linux Operating Systems


  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.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. Import the updated management pack for each version of Linux or UNIX 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.

My first server is a management server, and the web console, so I copy those two 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. 

I move on to my additional management servers and gateways, and apply the MSP file from the elevated command prompt.  No issues.




Manually import the management packs


The only MP to be updated with this CU1 for SP1 is located on your management servers, at




Only the AlertAttachment MPB should be updated.  The KB article known issues states the other MP should not be imported.  If you don’t use this MP already (Such as for Global Service Monitoring) then there is no need to install this update.  If you ever do go back and enable/install Global Service Monitoring or any MP that requires this Alert Attachment MP – don’t forget to install this updated version!  If not you will see issues with alert views in Dashboards, like console crashes or blank screens.



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:




Update Linux MPs


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

I open the console – and update these MP’s from disk


7.4.3507 is SCOM 2012 SP1.  7.4.4112.0 is SCOM 2012 SP1 with CU1.


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




In this case – there is no need, as the previous version of my agents were already updated.




Lastly – refer to the KB article for this update, as if you are a heavy user of Linux process monitoring using our template – additional steps are required to address the fixes.


All done!


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.



Comments (8)

  1. Kevin Holman says:

    The agents are placed into pending by the server update – we will place agents in pending for a management server, when the server update is applied, and ONLY at that time.  The act of placing agents into pending is something that happens during the application of the MSP update.

    If they did not go into pending, then something broke during your installation.  I'd probably consider re-applying it, and logging verbose to a file.

  2. Kevin Holman says:

    @Wilson –

    Absolutely.  They are available through WSUS directly, or SCCM through WSUS, or SCCM through a software package.

  3. Kevin Holman says:

    @SpanishScomGuy –

    I’m sorry, I don’t understand your question.

  4. scom_guy says:

    I applied CU1 to my SCOM 2012 SP1 test server and it went pretty well except that my agents never appeared in the Pending Management view, even though they were originally push-installed.  Is there something that needs to be done to trigger this?  I tried restarting the MS health service and even rebooting the MS, but neither worked.  I eventually had to just manually update the agents.

  5. Wilson W. says:

    Do the CU1 patches for the agents appear as a distributable patch in WSUS?  If so, then you could simply apply the patches via WSUS instead of pushing them out from the SCOM console…..

  6. scom_guy says:

    I found what my problem was.  The first time I ran the update, I ran as an account that was SCOM admin but did not have SA on the database.  I re-ran the update as an account with both SCOM admin and SA to the database, and it went as expected.  Sheesh!

  7. SpanishScomGuy says:

    Hi Kevin, I need to update an environment with Retail version Scom 2012; reinstall an environment in parallel with Scom 2012 R2 or conversely I updating the platform.

  8. SpanishScomGuy says:

    Sorry Kevin, the environment have an SCOM versión Retail, agent versión 7.0.856.0; the question I was asking you is if I need reinstall all, or on the other side I can update this versión the SCOM 2012.

    Thanks in advance

Skip to main content