In this blog post I will take you true the steps of installing System Center Operations Manager 2012 Sp1 update rollup 3 to Update Rollup 4
The following issues are fixed in this Update
- When you try to run a Windows PowerShell script or module in an AllSigned environment.
- Location points are not displayed on the GSM Map dashboard because of an SQL time-out error.
- An incorrect message description is generated when security event 5140 is monitored.
- An empty target group is created when endpoints are enumerated.
- By default, when a generic performance report is exported, the object information (such as server name, disk label, and so on) is collapsed, and the information is missing.
- When you start the network node dashboard on a computer that’s running a 32-bit edition of Windows 7 Service Pack 1, CPU usage is near 99 percent, and the console may stop responding.
- A user role that is created by using Windows PowerShell on a non-United States locale-based system does not show the Display name and Description fields in the console.
- When network discovery is run, duplicate entries for the same device may be added to the database.
- Availability Reports may be displayed as blank because the vStateDailyFull aggregate is returned empty.
- The monitored health state of the System Center Advisor agent is always in a "Warning" state on the Advisor Health State dashboard.
- Application Performance Monitoring (APM) is not functional when you upgrade to later versions of Operations Manager.
- A website cannot be discovered or monitored on a system that’s running Internet Information Services 8 if the HTTP binding is missing from the website configuration.
- In rare cases, the Monitoringhost.exe process on the Management Server may crash with an access violation 0xc0000005 when log files are monitored on UNIX and Linux computers.
- When discovering a Linux computer, discovery fails during secure shell (SSH) discovery, or the operating system name and version are determined incorrectly.
You can download the Update Rollup 4 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:\Backups"
2. Install Update to the Management server
3. Install Update to the Web Console
4. Install Update to the Operations Manager Console
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
7. Run the SQL scripts
- Start the "SQL Server Management Studio"
- Connect to the Database server and select the OperationManager Datawarehouse 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:
8. Import the management Pack
- Start the System Center Operations Manager Console and select the "Administation 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.Advisor.Internal.mpb
- Microsoft.SystemCenter.AlertAttachment.mpb
- Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
- Microsoft.SystemCenter.Apm.Infrastructure.mpb
- Microsoft.SystemCenter.Apm.Library.mpb
- Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
- Microsoft.SystemCenter.DataWarehouse.Reports.mp
- Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp
- Microsoft.SystemCenter.Image.Library.mp
- Microsoft.SystemCenter.IntelliTraceProfiling.mpb
- Microsoft.SystemCenter.Visualization.Library.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 om installing Update Rollup 4 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 4 I used the deployment plan from Kevin Holman