Every software needs to be up-to-date in order for their proper functionality. SCOM is no different in this case. Let’s see how applying an Update Rollup can be done in the proper way for SCOM 2012 R2.
I have explained this scenario based on SCOM 2012 R2 UR4 but the process is much similar for UR5 as well.
Performing the Update Rollup Installation
Below is the list of steps that you need to follow when performing a UR installation.
Apply MSPs to relevant server roles
First of all you have download the relevant update packages for the particular UR. If your SCOM servers are configured to receive updates directly from Microsoft Update (WSUS or Internet) for System Center Products you can go ahead and approve the relevant update packages. Here I’m referring the manual method of update installation as most servers are configured with strict update policy.
You can download UR4 update package from here. In UR4 there are 5 updates but based on your deployment you’ll have to apply the updates. As an example no need to apply Web Console update if you haven’t deployed that component in your SCOM environment. After you have downloaded the packages extract them to a central location.
Before you proceed with applying the MSPs perform below tasks.
Make sure all servers are up-to-date with latest patch updates.
Close SCOM Console if it is running in all servers.
In some cases you will have to stop System Center Data Access Service and System Center Management Configuration service on all management servers. But it wasn’t necessary in my case.
To apply the MSPs follow below procedure.
Open a Command Prompt with Elevated Rights (as Administrator)
Browse to the location where you have extracted the MSPs.
Install the MSP from command prompt. There won’t be any notification once it is installed other than it returning a blank cursor. But you can notice file version changes when you install each MSP as described in Kevin Holman’s Blog. Kevin’s post was focused on UR4 but the idea is same. Build numbers for SCOM 2012 R2 as follow and you can see same when you check the file versions as described in Kevin’s blog.
|Build Number||KB||Release Date||Description|
|7.1.10226.0||SCOM 2012 R2 RTM|
|7.1.10226.1011||KB2904678||2014, January 27||SCOM 2012 R2 Update Rollup 1|
|7.1.10226.1015||KB2929891||2014, April 23||SCOM 2012 R2 Update Rollup 2|
|7.1.10226.1037||KB2965445||2014, July 29||SCOM 2012 R2 Update Rollup 3|
|7.1.10226.1046||KB2992020||2014, October 28||SCOM 2012 R2 Update Rollup 4|
|7.1.10226.1052||KB3023138||2015, February 10||SCOM 2012 R2 Update Rollup 5|
Install the MSPs in below order (Yes the order matters)
- Management server or servers
- Gateway servers
- Web console server role computers
- Operations console role computers
Once you have installed the MSPs it’s critical that we check whether the installation was successful as intended. There is an excellent PowerShell script written by Jure Labrovic which can be found in TechNet Gallery which will help you to achieve this. Note that this script is validating against UR4 bust it’s just a matter of tweaking the script to make it work for UR5. I did not use Operations Manager Shell but I did use regular PowerShell with administrator elevation. (You may need to Set-ExecutionPolicy to Unrestricted if you already haven’t done that.)
Here is my result when I run this script in one of my management servers.
Execute SQL scripts on SCOM databases
This part is rather is but you need to do several important tasks that you need to perform before you do so.
Stop System Center Data Access Service and System Center Management Configuration service on all management servers.
Perform a full backup of both OpeartionsManager & OperationManagerDW databases. This is just in case if anything goes wrong.
Here is how you execute the SQL scripts.
You can find the scripts at %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server \SQL Script for Update Rollups\ in any management server that you have updated with MSPs.
There are two scripts that need to be executed. Execute Update_rollup_mom_db.sql in OperationsManagerDB and UR_Datawarehouse.sql in OperationsManagerDW.
If you get an error when you run any of the scripts do not continue. Try running same multiple time before you move into the other script. Usually this happen if you haven’t stopped the services in management servers which results in deadlocks in the databases.
Manually Import Management Packs
Now you have to manually import some management packs that were updated in the UR. These can be found at %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups. Here is the list of MPs that you need to import in UR4.
- Microsoft.SystemCenter.TFSWISynchronization.mpb (There is a dependency Microsoft.SystemCenter.AlertAttachment.mpb for this MP. This can be found in Installation media for SCOM 2012 R2)
Apply agent update to manually deployed agents
For agents that you have previously installed via push installation, you will notice that they are under Pending Management view now. You can approve them to update the MOM agent. For manually installed agents you will have to install the updated agent which can be found in SCOM installation path of any management servers.
Update Linux/Unix MP and update *nix agents (Optional)
This is an optional step if you have deployed *nix agents. More information can be found in this KB article.
And that’s how we deploy a UR for SCOM 2012 R2.