In this blog post I will take you true the steps of installing System Center Operations Manager 2012 Sp1 update Rollup 8 to Update Rollup 9
The following issues are fixed in this Update
- Operational Insight through Operations Manager
- Support for “SUSE Linux Enterprise Server systems”
You can download the Update Rollup 9 form here
The downloaded files consist of an update for the “System Center Operations Manager Console” and the “System Center Operations Manager Server.
The following steps outline the process of installing the Update
- Backup the operations Manager Databases and unsealed Management Pack’s
- Install Update to the Management server
- Install update to the secondary Management Servers
- Install Update to the Operations Manager Console
- Run the SQL scripts
- Import Management Pack’s
- Deploy the update to the agents
1. Backup the operations Manager Databases and unsealed Management Pack’s
I did a manual backup from my databases using the SQL Console
- Start the "SQL Server Management Studio"
- Connect to the Database server
- Right click on the database that you want to backup, select "Tasks" and click "Backup
- On the "Backup Database Select the setting that you want to use and click "Ok
- When the Backup is completed click "Ok
- Repeat the steps Above for all the databases
You can backup your management pack’s using the powershell Operations Manager shell and type the following command:
Get-SCManagementPack | Export-SCManagementPack -path D:\Backup\MP
2. Install Update to the Management server
3. Install update to the secondary Management Servers
I installed the update the same way is installed it on the Management Server. So follow Step 2
4. Install Update to the Operations Manager Console
5. Run the SQL scripts
- Start the "SQL Server Management Studio"
- Connect to the Database server and select the “OperationsManagerDW" Database
- On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "UR_Datawarehouse.SQL" file and then click Open.
- When the file is loaded, click "Execute" in the SQL Editor tool bar
- Your Result should look something like:
Next we need to run the following script against the OperationsManager database
- Start the "SQL Server Management Studio"
- Connect to the Database server and select the “OperationsManager" Database
- On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "update_rollup_mom_db" file and then click Open.
- When the file is loaded, click "Execute" in the SQL Editor tool bar
- Your Result should look something like:
6. Import the management Pack
- Start the System Center Operations Manager Console and select the "Administration pane"
- Right click "Management Pack" and click "Import Management Packs…"
- In the "Import Management Packs" and click "Add" and click "Add from Disk…"
- Browse to "D:\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update Rollups" and select the management Pack’s in that folder
- Microsoft.SystemCenter.AlertAttachment.mpb
- Microsoft.SystemCenter.IntelliTraceProfiling.mpb
- Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb which should be installed from SCOM 2012 SP1
- MediaMicrosoft.Windows.InternetInformationServices.Common.mpb which should be installed from the online catalog
- Microsoft.SystemCenter.Visualization.Library.mpb
- Microsoft.SystemCenter.Image.Library.mp
- Microsoft.SystemCenter.Advisor.Internal.mpb
- Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
- Microsoft.SystemCenter.Apm.Infrastructure.mpb
- Microsoft.SystemCenter.Apm.Library.mpb
- Microsoft.SystemCenter.DataWarehouse.Report.Library.mp p
- Microsoft.SystemCenter.DataWarehouse.Reports.mp
- Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp
- Microsoft.SystemCenter.TFSWISynchronization.mpb
- Click "Install"
- Click "Close"
7. Deploy the update to the agents
- Start the System Center Operations Manager Console and select the "Administration pane"
- Select " Device Management" and then "Pending Management"
- Select the a "Agent" and click "Approve"
- On the "Agent Update" page click "Update"
- when you open de the "Agent by Version" view you should see something like this:
More information on installing Update Rollup 9 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 8 I used the deployment plan from Kevin Holman
do not saw any UR9 agent for servers monitoring
Hi Steven,
That is correct.
When you will look under pending managed you will see all you monitored servers there. If you approve the update and you will look in the view: Agents by Version you will see if the patch is installed.
Greatings Roel Knippen
Hi
My SCOM 2012 R2 environment is on Update 7, do I need to go to update 8 first before going to 9 or can I go straight to update 9?
Hi,
Thank’s for the comment. You can go straight into installing update rollup 9.
Greetings Roel Knippen
Hello and thank you for the article.
Is it true that RU9 includes all prior released updates, except UR8 which only contains the new HTML based portal.
https://support.microsoft.com/en-us/kb/3134286
I currently have SCOM 2012 R2 with NO RU, can I install RU9 and then install Self-Service Portal update or I have to install RU8 and then RU9 to get Self-Service Portal update in place before install RU9?
Thank you
Hi Alex,
The site where you are reffering to is for System Center Service Manager. I don’t now how to run the update’s for System Center Service Manager.
GReetings
Roel Knippen
Hello,
How to upgrade manually installed agents? I have run Windows update check on one of my Windows 2003 workgroup server and it shows nothing.
Thank you
Hi Alex,
You can update the manual installed scom agent using the following steps:
Manually-installed agents are agents that were installed manually, either by using the Command Prompt window, or by using the MOMAgent.msi Setup Wizard. Use the following procedure to upgrade these agents.
To upgrade a manually installed Windows agent by using the Setup Wizard
1.Log on to the computer that hosts the agent with an Operations Manager Administrators role account for your Operations Manager management group.
2.Run Setup.exe from the Operations Manager installation media.
3.On the first page of the Setup Wizard, click Local agent. When the Welcome to the System Center Operations Manager 2012 Agent Upgrade Wizard page opens, click Next.
4.In the System Center Operations Manager 2012 Agent Setup dialog box, click Upgrade. The status page displays the progress of the upgrade.
5.When the Completing the System Center Operations Manager 2012 Agent Setup Wizard page appears, click Finish.
Hope it helps
Roel Knippen
Thank you for reply.
“2.Run Setup.exe from the Operations Manager installation media.” Is this Installation media where agent(gateways) was installed first time?
Can I upgrade Gateway and than you MOMagent.msi file from updated gateway to upgrade manually installed agents.
We have complicated environment where we monitor nontrasted domains or workgroups via Gateways (internet connection).
Thank you
Alex
Hi Alex,
When you install update rollup 9 for system center Operations Manager 2012 SP1 there isn’t an update for the gateway.
You can install the agent manually using the momagent.msi. And the check if the certificate chain that is needed for Systm Center Operations Manager 2012 SP1.
Here is nice blogpost from Stefan Stranger
Hope it helps
Roel Knippen
I’ve applied UR9 to all mgmt. servers. My agents are not showing pending management. They still show the UR8 patch in the Agent Version view. I tried manually running the MSP on one of my agents, and that one is reporting UR9. The others won’t change to pending for the update, however.
Hi Mark,
Thanks for the comment.
Agents assigned to a management server will go into pending when that management server has a CU/SP/update applied which affects agents. It will happen only ONCE, at the time of the patch being applied there is a step in the code in which it flags these agents as pending update.
If this does not happen – then something broke while performing the update. Most of the time the issue is with not kicking off the update from the splash screen, which was called from an elevated command prompt.
Do you see warnings or error’s in you Event Log?
Greetings Roel Knippen