SCOM 2012 R2 UR4 Upgrade Procedure

A while ago I wrote myself a SCOM UR upgrade checklist. Information is gathered from various Blogs including Kevin Holman’s Blog.
Here are few points I follow:

1. Update All Servers (Windows Updates) before applying UR (uncheck URs while applying updates).
You can also reboot server before upgrade to see if there are any errors before we proceed with upgrade.
2. Close Console on server before applying updates
3. Run MSPs in Elevated CMD (As an administrator)
4. Run MSPs as SQL Admin

This are the steps I take:

1. Install the update rollup packages in following Order:
a. Apply MSPs on All Management Servers (Server MSP)
b. Apply MSPs on All Gateway servers (Gateway MSP)
c. Apply MSPs on Web console server role computer (Web Console MSP)
d. Apply MSPs Servers with Operations console (Operations Console MSP)

2. Run This PowerShell Script to check if SCOM was successfully upgraded to UR4. More information on how to use it can be found Here.

3. Apply SQL scripts (see installation information).
a. Update_rollup_mom_db.sql => OperationsManagerDB
b. UR_Datawarehouse.sql => OperationsManagerDW

Scripts Can be found here:
%SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\SQL Script for Update Rollups\

NOTES:
If you get an Error Do not continue. Try rerunning the script. If that does not help Turn off:
“System Center Data Access Service” and “System Center Management Configuration service.” on All Management Servers.

If you see a warning about line endings, choose Yes to continue.

4. Manually import the management packs.
a. Microsoft.SystemCenter.TFSWISynchronization.mpb (this one has dependency: Microsoft.SystemCenter.AlertAttachment.mpb – it can be found on media)
b. Microsoft.SystemCenter.Visualization.Library.mpb
c. Microsoft.SystemCenter.Visualization.Component.Library.mpb
d. Microsoft.SystemCenter.Advisor.mpb
e. Microsoft.SystemCenter.Advisor.Internal.mpb
f. Microsoft.SystemCenter.2007.mp

Files Can be found here:
%SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups

5. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.
6. Update Unix/Linux MP’s and Agents if needed
7. Update JEE if needed
8. Update Remaining Consoles…

And Here is a List I follow so I do not miss any of the steps:

SCOMupgradeToDo
Hope this was helpful
Jure

Advertisements
This entry was posted in Operations Manager, Update Rollup, UR and tagged , , , , , , , . Bookmark the permalink.

13 Responses to SCOM 2012 R2 UR4 Upgrade Procedure

  1. Curtiss says:

    for all you cutters and pasters out there, there’s an extra space after ‘server’ in the scripts path above (which you’ll need to remove)

  2. Thyfere says:

    Hi Jure,

    Should I apply UR1, UR2, or UR3 before applying this update?

  3. Thyfere says:

    That’s great! Thanks Jure…

  4. Thyfere says:

    Hi Again,

    I have Three servers, i.e. DB, MS1 and MS2. Both MS servers are with Operations Console. I didn’t configure Web Console yet. Should I update both MS servers with UR4 – Operations Manager first and then UR4 – Operations Manager Console?

    Second, I can see UR4 in Windows Update, do I still need to download and apply MSPs?

    • jurelab says:

      Hi,
      I First update All MS servers first, then All GW Servers,…

      You could apply it through updates. I apply them manually since we also need to run Scripts on Database server. Manual procedure is also faster by my opinion.

      Regards
      Jure

  5. Thyfere says:

    Hi Jure,

    Thanks again for your prompt reply. One more thing, do I need to run the MSP as SQL Admin too?

  6. Thyfere says:

    I have successfully applied the MSPs through elevated CMD but getting the following error:

    ———————-
    Management Server: ******** is Not Updated to UR4
    Files were not upgraded or user does not have read permissions..

    ———————-
    Management Server: ******* is Not Updated to UR4
    Files were not upgraded or user does not have read permissions.

    That’s why I asked, should I applied the MSPs as SQL Admin too?

    • jurelab says:

      Hi,

      Se Above.. One of the things I folow is: “Run MSPs as SQL Admin”

      Is it working if you run it as SQL admin?

      Regards
      Jure

  7. Thiren says:

    Thanks for this guide, it really helped with my upgrade

    my scenario though, is

    10 Management Servers
    1 Always On SQL OPSDB 2012 with 4 Nodes
    1 Always On SQL OPSDW2012 with 4 Nodes

    we just had to do a quick check with SQL before applying the Updates, as the Primary Replica’s gave a small issue

    But other than that, followed all the above to the point, and it worked

    Thanks
    T

  8. Pingback: SCOM 2012 R2 UR5 Upgrade Procedure | Rather Serious SCOM Blog

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