In this blog post I will take you true the steps of installing System Center Operations Manager 2012 Sp1 update rollup 4 to Update Rollup 5
The following issues are fixed in this Update
- An error occurs when you run the p_DataPurging stored procedure. This error occurs when the query processor runs out of internal resources and cannot produce a query plan.
- By default, data warehouse bulk-insert commands use an unchangeable 30-second time-out value that may cause query time-outs.
- Many 26319 errors are generated when you use the Operator role. This issue causes performance problems.
- Diagram component does not publish location information in the component state.
- Renaming a group works correctly on the console. However the group appears with the old name when you try to override a monitor or scope a view based on group.
- SCOM synchronization is not supported in the localized versions of Team Foundation Server.
- An SDK process deadlock causes the Exchange correlation engine to fail.
- In rare cases, the agent on a Solaris Zone that is configured to use dynamic CPU allocation with Dynamic Resource Pools may hang during routine monitoring.
- Availability Reports may be displayed as blank because the vStateDailyFull aggregate is returned empty.
- If the agent fails to retrieve process arguments from the getargs subroutine on an AIX-based computer, the monitored daemons may be incorrectly reported as offline.
- The Universal Linux agent fails to install on Linux computers with OpenSSL versions greater than 1.0.0 if the library file libssl.so.1.0.0 does not exist.
- Spurious errors that are related to the InstanceID property of the SCX_Endpoint are logged in the System log every four hours.
You can download the Update Rollup 5 form here
The following steps outline the proces of installing the Update
- Backup the operations Manager Databases and unsealed Management Pack’s
- Install Update to the Management server
- Install Update to the Web Console
- Install Update to the Operations Manager Console
- Install update to the secondary Management Servers
- Install update to the gateway servers
- 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
U can backup your management pack’s using the following command:
Get-SCManagementPack | Export-SCManagementPack -path D:\Backup\MP
2. Install Update to the Management server
- Extract the cabinet file
- Start a "elevated command prompt"
- Run the "KB2904680-AMD64-Server.msp"
- Installation is running. This can take some time.
- The update will give a reboot screen. Click "Yes to restart the server
3. Install Update to the Web Console
- Extract the cabinet file
- Start a "elevated command prompt"
- Run the "KB2904680-AMD64-ENU-WebConsole.msp"
- The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.
4. Install Update to the Operations Manager Console
- Extract the cabinet file
- Start a "elevated command prompt"
- Run the "KB2904680-AMD64-ENU-Console.msp"
- The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.
5. 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
6. Install update to the Gateway server
- Extract the cabinet file
- Start a "elevated command prompt"
- Run the "KB2904680-AMD64-Gateway.msp"
- The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.
7. Run the SQL scripts
- Start the "SQL Server Management Studio"
- Connect to the Database server and select the OperationManager Database
- On the tool bar, click New Query
- 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" 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 OperationsManagerDB database
- Start the "SQL Server Management Studio"
- Connect to the Database server and select the OperationManager Database
- On the tool bar, click New Query
- 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:
8. 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.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"
9. Deploy the update to the agents
- Start the System Center Operations Manager Console and select the "Administation pane"
- Select " Device Management" and then "Pending Mangement"
- Select the a "Agent" and click "Approve"
- On the "Agent Update" page click "Update"
- when you open de the "Agent by Version" you should see something like this:
More information on installing Update Rollup 5 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 5 I used the deployment plan from Kevin Holman