Installing Update Rollup 4 SCOM 2012 Sp1

Standard

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

    1. Backup the operations Manager Databases and unsealed Management Pack’s
    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
    6. Install update to the gateway servers
    7. Run the SQL scripts
    8. Import Management Pack’s
    9. 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

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server
    3. Right click on the database that you want to backup, select "Tasks" and click "Backup

      BackupDatabase2012

    4. On the "Backup Database Select the setting that you want to use and click "Ok

      BackupDatabase2012OK

    5. When the Backup is completed click "Ok
    6. 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"

    backupMPPowershell

    2. Install Update to the Management server

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2880799-AMD64-Server.msp"

      UpdateManagementServer

    4. Installation is running. This can take some time. (The update doesn’t give any feedback. Check the application event-viewer if the setup is still running)

      SystemcenterOperationManagementserverUpdate

    3. Install Update to the Web Console

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2880799-AMD64-ENU-WebConsole.msp"

      UpdateWebconsole

    4. 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

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2880799-AMD64-ENU-Console.msp"

      UpdateConsole

    4. 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

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2880799-AMD64-Gateway.msp"

      UpdateGateway

    4. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

    7. Run the SQL scripts

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server and select the OperationManager Datawarehouse Database
    3. On the tool bar, click New Query

      newsqlquery

    4. 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.
    5. When the file is loaded, click Execute in the SQL Editor tool bar
    6. Your Result should look something like:

      RowsAffected

    8. Import the management Pack

    1. Start the System Center Operations Manager Console and select the "Administation pane"
    2. Right click "Management Pack" and click "Import Management Packs…"
    3. In the "Import Management Packs" and click "Add" and click "Add from Disk…"
    4. 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
    5. Click "Install"
    6. Click "Close"

    9. Deploy the update to the agents

    1. Start the System Center Operations Manager Console and select the "Administation pane"
    2. Select " Device Management" and then "Pending Mangement"
    3. Select the a "Agent" and click "Approve"

      ApproveAgent

    4. On the "Agent Update" page click "Update"

      UpdateAgent

    5. when you open de the "Agent by Version" you should see something like this:

      AgentUp2Date

    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

    8 thoughts on “Installing Update Rollup 4 SCOM 2012 Sp1

    1. michel

      Hi,

      Nice post. One correction to the install SQL step:

      You wrote:
      2.Connect to the Database server and select the OperationManager Database

      but i should be :
      2.Connect to the Database server and select the OperationManager datawarehouse Database

      Michel

    2. David

      Hi Roel, hi everybody

      thanks for the documentation. After updating, we are having an issue with the reports. All Reports are listed but any report cant be run. Is anybody having the same issue?

      I select a report (doesn’t matter which one, same issue everywhere), a blank report window appears and after more or less 30 seconds a prompt “Cannot initialize report. (rsProcessingAborted).

      Report Services OS: win 2012
      SQL Version: sql 2012 sp1

      url http:///reports &
      http:///ReportServer
      are working. Reports are listed but cant be run. same error prompt

      “A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 – The semaphore timeout period has expired.)”

      thanks for any feedback!
      cheers
      David

    3. Sebastian mellebeek

      I’ve also ran into the issue, after some research I found that the exchange 2010 report MP could be the cause of reports showing up empty.

      I followed the solution steps from this article: http://thoughtsonopsmgr.blogspot.be/2011/09/empty-reports-in-scom-whats-happening.html

      The reporting in our environment is now “rebuilding” (I guess) slowly. This morning I could only see data until the 7th of January, in the mean time I can see data until the 10th, If I select a different data 11th until 17th for example, the report is empty. So I’ll just have to wait a little longer.

    Leave a Reply

    Your email address will not be published. Required fields are marked *