Installing Update Rollup 8 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 7 to Update Rollup 8

The following issues are fixed in this Update

  • The Health Service bouncing that is caused by high memory usage in the MonitoringHost process.
  • This update includes a fix to prevent resynchronization of all managed entities from the Operations Manager to the Operations Manager Data Warehouse (OMDW) database and to prevent the failure to sync that this causes because of duplicate entries.
  • The import of Visualization.component.library and Visualization.library binary files (.mpb) fails. The import succeeds on a successive try.
  • System Center Operations Manager agents randomly time out when authenticating to the Gateway or Management Server because of domain controller or network performance issues. The time-out value was set to 1 second earlier. A fix was made to increase server time out to-20 seconds and client time out to 5 minutes.

You can download the Update Rollup 8 form here

The following steps outline the process 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 secondary Management Servers
  4. Install update to the gateway servers
  5. Install update to the ACS servers
  6. Install Update to the Web Console
  7. Install Update to the Operations Manager Console
  8. Run the SQL scripts
  9. Import Management Pack’s
  10. 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

    BackupDatabase

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

    BackupRunning

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

backupMP

2. Install Update to the Management server

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

    UpdateManagementServer

  4. Installation is running. This can take some time.

    UpdateManagementServerRunning

  5. On the Dialog Screen "System Center Operations Manager 2012" klik "Yes" to restart the server

    UpdateManagementServerRestart

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 gateway servers

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

    UpdateGatewayServer

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

5. Install update to the ACS servers

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB2991997-AMD64-ENU-ACS.msp"

    UpdateACS

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

6. Install Update to the Web Console

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

    UpdateConsole

  4. Installation is running. This can take some time.

    UpdateWebConsoleRunning

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

7. Install Update to the Operations Manager Console

  1. If you don’t want to reopen the System Center Operations Manager Console close the
  2. Extract the cabinet file
  3. Start a "elevated Powershell command prompt"
  4. Run the "KB2991997-AMD64-ENU-Console.msp"

    UpdateConsole

  5. Installation is running. This can take some time.

    UpdateConsoleRunning

 

8. Run the SQL scripts

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManagerDW" Database

    SelectOperationManagerDW

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

    RowsAffected

Next we need to run the following script against the OperationsManager database

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManager" Database

    SelectOperationManager

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

    RowsAffected3

9. Import the management Pack

  1. Start the System Center Operations Manager Console and select the "Administration 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.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
    • Microsoft.SystemCenter.Visualization.Component.Library.mpb
  5. Click "Install"

    UpdateManagementPacks

  6. Click "Close"

10. Deploy the update to the agents

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

    Aprove

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

    Update

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

    Ready

More information on installing Update Rollup 8 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

Installing Update Rollup 6 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 5 to Update Rollup 6

The following issues are fixed in this Update

  • Service Level Objectives (SLO) dashboards sometimes load in several seconds and sometimes take minutes to load. Additionally, in some cases, the dashboard is empty after it loads.
  • SQL Time Out Exceptions for State data (31552 events) occur when you create Data Warehouse work flows.
  • This update rollup includes a fix for the dashboard issue that was introduced in Update Rollup 5.
  • Adding multiple regular expressions (RegEx’s) to a group definition causes a SQL exception when adding or running the group.
  • The System Center Operations Manager console is slow to load views if you are a member of a custom Operator role.
  • All IBM WebSphere application servers that run on Linux or AIX computers will not be automatically discovered by the Management Pack for Java Enterprise Edition (JEE) if multiple application servers are defined in a single WebSphere profile.

    You can download the Update Rollup 6 form here

    The following steps outline the process 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 secondary Management Servers
    4. Install update to the gateway servers
    5. Install update to the ACS servers
    6. Install Update to the Web Console
    7. Install Update to the Operations Manager Console
    8. Run the SQL scripts
    9. Import Management Pack’s
    10. 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

      BackupDatabase

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

      BackupRunning

    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:\Backup\MP

    backupMP

    2. Install Update to the Management server

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

      kb2929885ManagementServer

    4. Installation is running. This can take some time.

      kb2929885ManagementServerRunning

    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 gateway servers

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

      kb2929885Gateway

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

    5. Install update to the ACS servers

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

      kb2929885Acs

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

    6. Install Update to the Web Console

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

      kb2929885Webconsole

    4. Installation is running. This can take some time.

      kb2929885WebConsoleRunning

    5. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.
    6. After installing the update, you need to add the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:

      < machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

      I did that using the following steps:

      • Start "Powershell" as administrator and stop the IIS Service "iisreset /Stop"
      • In a text editor such as Notepad, open the application-level Web.config.default file.
      • In the Web.config.default file, locate the "<system.web>" section.
      • Under the "<system.web>" add the following line:

        < machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

      • Start "Powershell" as administrator and stop the IIS Service "iisreset /Start"

    7. Install Update to the Operations Manager Console

    1. If you do not want to restart the computer after you apply the console update, close the console before you apply the update for the console role.
    2. Extract the cabinet file
    3. Start a "elevated command prompt"
    4. Run the "KB2929885-AMD64-ENU-Console.msp"

      kb2929885Console

    5. Installation is running. This can take some time.

      kb2929885WebConsoleRunning

    6. I did a restart of the computer.

    8. Run the SQL scripts

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server and select the OperationManagerDW" Database

      SelectOperationManagerDW

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

      RowsAffected

    Next we need to run the following script against the OperationsManager database

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server and select the OperationManager" Database

      SelectOperationManager

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

      RowsAffected3

    8. Import the management Pack

    1. Start the System Center Operations Manager Console and select the "Administration 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.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
      • Microsoft.SystemCenter.Visualization.Component.Library.mp
      • Microsoft.SystemCenter.Visualization.Component.Library.mpb
    5. Click "Install"
    6. Click "Close"

    10. Deploy the update to the agents

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

      Aprove

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

      Update

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

      Ready

    More information on installing Update Rollup 6 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 6 I used the deployment plan from Kevin Holman

    Installing Update Rollup 5 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 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

      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

        BackupDatabase

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

        BackupRunning

      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:\Backup\MP

      backupMP

      2. Install Update to the Management server

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

        kb2901680

      4. Installation is running. This can take some time.

        kb2901680Runnning

      5. The update will give a reboot screen. Click "Yes to restart the server

        reboot

      3. Install Update to the Web Console

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

        kb2901680Webconsole

      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 "KB2904680-AMD64-ENU-Console.msp"

        kb2901680Console

      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 "KB2904680-AMD64-Gateway.msp"

        kb2901680Gateway

      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 Database
      3. On the tool bar, click New Query

        UpdateRollupMomDb

      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

      Next we need to run the following script against the OperationsManagerDB database

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

        UpdateRollupMomDb

      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 "update_rollup_mom_db" 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:

        RowsAffected2

      8. Import the management Pack

      1. Start the System Center Operations Manager Console and select the "Administration 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.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
      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"

        Aprove

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

        Update

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

        Ready

      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

      Installing Cumulative Update 7 SCOM 2007 R2

      Standard

      In this blog post I will take you true the steps of installing System Center Operations Manager 2007 r2 Cumulative Update 7

      The following uses are fixed in this Update

      • Console performs poorly when User Roles are used to scope object access.
      • Availability data is not shown for the current day when daily aggregation is used.
      • Behaviour is inconsistent between some views on web console and console.
      • Log files do not roll over when the Unicode log file is monitored.
      • Several security issues are fixed.
      • Logical disk performance statistics are not collected for some volume types on Solaris computers.
      • Some Network Adapters on HP-UX computers may not be discovered.
      • Network adapter performance statistics are not collected for HP-UX network adapters.
      • The Solaris 8 and 9 agent may not restart after an ungraceful shut-down.

      You can download the Cumulative Update 7 form here

      The following steps outline the process of installing the Update

      1. Backup the operations Manager Databases and unsealed Management Pack’s
      2. Apply the hot fix to the RMS
      3. Run the SQL Scripts after you updated the RMS
      4. Import the management Pack provided
      5. Install update to the secondary Management Servers
      6. Install update to the gateway servers
      7. Deploy the update to the agents
      8. Install the update to the computers that using the Console
      9. Install the update to the web console
      10. Install the update to the ACS Servers
      11. Update the manual installed 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

        BackupDatabaseSCOM

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

        RunBackupScom

      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-managementpack | export-managementpack -path c:\backup"

      2. Apply the hot fix to the RMS

      First you need to install the hot fix Utility

      1. Run the "SystemCenterOperationsManager2007-R2CU7-KB2783850-X86-X64-IA64-ENU.MSI"
      2. On the "System Center 2007 R2 Hot fix Utility License Agreement" page click "I Agree" and click "Next"
      3. On the "System Center 2007 R2 Hot fix Utility Information" page click "Next"
      4. On the "Select Installation Folder" page, Put in the settings you want and click "Next"

        InstallHotfixFolder

      5. On the "Confirm Installation" page click "Next"
      6. On the "Installation Completed" page click "Close"

      Now its time to do the update on the RMS

      1. Browse to the place you installed the hot fix Utility and start the "Launch Cumulative Update Set-up"
      2. On the "System Center Operations Manager 2007 Software update" splash screen click "Run Server update"

        RMSupdate1

      3. The installation Process will start automatic and click finish when completed

        RMSUpdate2

      4. You have to click finish three times

      3. Run the SQL Scripts after you updated the RMS

      Now Run the SQL Scripts that must be applied manually to the database

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

        NewSQLQuery

      4. On the File menu, click Open, browse to C:\program files (x86)\System Center 2007 R2 hot fix utility\KB2783850\SQLUpdate, select the "CU_Database.sql" file that was extracted by the Windows installer (.msi file), and then click Open.
      5. When the file is loaded, click Execute in the SQL Editor tool bar
      6. Your Result should look like:

        CUdatabasesSQLResult

      7. Select the OperationsManagerDW database
      8. On the File menu, click Open, browse to C:\program files (x86)\System Center 2007 R2 hot fix utility\KB2783850\SQLUpdate, select the "CU_DataWarehouse.sql" file that was extracted by the Windows installer (.msi file), and then click Open.
      9. When the file is loaded, click Execute in the SQL Editor tool bar
      10. Your Result should look like:

        CUDatawarehouseSQLResult

      4. Import the management Pack provided

      1. Start the System Center Operations Manager Console and select the "Administration 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 (x86)\System Center 2007 R2 Hot fix Utility\KB2783850\ManagementPacks" and select the management Pack’s in that folder
        • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
        • Microsoft.SystemCenter.WebApplication.Library.mp
        • Microsoft.SystemCenter.WSManagement.Library.mp
      5. Click "Install"
      6. Click "Close"

      5. Install update to the secondary Management Servers

      I installed the update the same way is installed it on the RMS. So follow Step 2

      6. Install update to the gateway servers

      I installed the update the utility on the gateway server and instead of running the Run Server Update I ran the "Run gateway update"

      7. Deploy the update to the agents

        1. Start the System Center Operations Manager Console and select the "Administration pane"
        2. Select " Device Management"

      and then "Pending Engagement"

      • Select the a "Agent" and click "Approve"
      • On the "Agent Update" page click "Update"

        UpdateAgent

      • When the Update of the agent is finished you should see:

        UpdateAgentSuccesfull

      8. Install the update to the computers that using the Console

      1. Run the "SystemCenterOperationsManager2007-R2CU7-KB2783850-X86-X64-IA64-ENU.MSI"
      2. On the "System Center 2007 R2 Hot fix Utility License Agreement" page click "I Agree" and click "Next"
      3. On the "System Center 2007 R2 Hot fix Utility Information" page click "Next"
      4. On the "Select Installation Folder" page, Put in the settings you want and click "Next"

        InstallHotfixFolder

      5. On the "Confirm Installation" page click "Next"
      6. On the "Installation Completed" page click "Close"
      1. Browse to the place you installed the hot fix Utility and start the "Launch Cumulative Update Set-up"
      2. On the "System Center Operations Manager 2007 Software update" splash screen click "Run Server update"

        RMSupdate1

      3. The installation Process will start automatic and click finish when completed

        RMSUpdate2

      4. You have to click finish three times

      9. Install the update to the web console

      I run my web console on a management server witch I all ready updated to Cumulative Update 7 So the only thing that I need to adjust is:

      1. Open the "Web.config" file
      2. Add the following configuration "" or when U using https ""

      10. Install the update to the ACS Servers

      When you have a standalone ACS server follow the steps mentioned in step 2 of the post

      1. Browse to the place you installed the hot fix Utility and start the "Launch Cumulative Update Setup"
      2. On the "System Center Operations Manager 2007 Software update" splash screen click "Run ACS update"

        RMSupdate1

      3. The installation Process will start automatic and click finish when completed

        RMSUpdate2

      When your finished you need to run a update to SQL database "OperationsManagerAC" on your database Server

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

        NewSQLQuery

      4. On the File menu, click Open, browse to %SystemDrive%\Windows\System32\Security\AdtServer\DbUpgV6toV7.sql , select the "DbUpgV6toV7.sql" file that was extracted by the Windows installer (.msi file), and then click Open.
      5. When the file is loaded, click Execute in the SQL Editor toolbar
      6. Your Result should look like:

        DbUpgV6toV7SQLResult

      11. Update the manual installed agents

      You can install this manual using the following command "msiexec.exe /p "C:\temp\CU7_Agent\KB2783850-x64-Agent.msp" REBOOT="ReallySuppress"

      More information on installing System Center Operations Manager 2007 r2 can be found here. To install this Cumulative update I used the deployment plan from Kevin Holman

      System Center Operations Manager Updates

      Standard

      In this blogpost I will give information on the released Cumulative Updates for System Center Operations Manager 2007 r2 and System Center Operations Manager 2012. I will try to keeping this post up to date when a new update is released. Most information in this blogpost can also be found on Microsoft Technet and some information is directly copied from Microsoft Technet.

      Last Update 16-01-2013

      Here are all the Cumulative Update Rollups for System Center Operations Manager 2012.

      • Service Pack 1 : System Center Operation Manager 2012 Service Pack 1 is released on January 2, 2013. This Update Resolves the following Issues:
        • Support for IIS 8
        • Monitoring of WCF, MVC and .NET NT services
        • Azure SDK support
        • Monitoring of SharePoint 2010 with APM (.NET application performance monitoring)
        • Integration with Team Foundation Server 2010 and Team Foundation Server 2012
        • Conversion of Application Performance Monitoring events to IntelliTrace format
        • Support for monitoring of CentOS, Debian, and Ubuntu Linux
        • ACS support for Dynamic Access Control in Windows Server 2012
        • Global Service Monitor – cloud based capability to monitor the health of your web applications from geo-distributed perspective
        • Additional network devices models supported

        More Information on Service Pack 1 can be found here. Kevin Greene wrote a greath blog series on how to install Service Pack 1. Kevin Greene blog series can found: Part 1 Part 2 Part 3

      • Cumulative Update Rollup 3: System Center Operation Managener 2012 Cumulative Update Rollup 3 is released on October 9, 2012. This Update Resolves the following Issues:
        • When you use the 32-bit version of Windows Internet Explorer to start a web console, the “Microsoft.EnterpriseManagement.Presentation.Controls.SpeedometerGaugeUIController” controller does not work correctly
        • When you run a Windows PowerShell cmdlet, you receive the following error message: “Get-BPAModel is not recognized as the name of a cmdlet“.
        • When you try to change a URL in the “web application availability monitoring” template instance, the change is not applied.

        More Information on Cumulative Update Rollup 3 can be found here and can be download from here. Kevin Greene wrote a greath blogpost on how to install Cumulative Update Rollup 3. Kevin Greene blogpost can found here

      • Cumulative Update Rollup 2: System Center Operation Managener 2012 Cumulative Update Rollup 2 is released on July 24, 2012. This Update Resolves the following Issues:
        • The Windows PowerShell module runspace configuration cache grows indefinitely. This causes memory usage to increase.
        • The Set-SCOMLicense cmdlet fails if the management group evaluation expiration time-out has expired.
        • The System Center Operations Manager agent may crash on Oracle Solaris root zones that are configured to use a range of dedicated CPUs.
        • The UNIX/Linux agent process provider may not enumerate running processes if a process has arguments that include non-ASCII characters. This prevents process/daemon monitoring.
        • The .rpm specification file for the agent for Red Hat Enterprise Linux does not specify the distribution.

        More Information on Cumulative Update Rollup 2 can be found here and can be download from here. Kevin Holman and Kevin Greene both wrote a greath blogpost on how to install Cumulative Update Rollup 2. Kevin Holman blogpost can be found here and Kevin Greene blogpost can be found here

      • Cumulative Update Rollup 1: System Center Operation Managener 2012 Cumulative Update Rollup 1 is released on May 8, 2012. This Update Resolves the following Issues:
        • Environment crashes in Operations Manager due to RoleInstanceStatusProbe module in AzureMP.
        • When multiple (2-3) consoles are running on the same computer under the same user account the consoles may crash.
        • Cannot start or stop tracing for Reporting and Web Console if they were installed to a standalone IIS server.
        • Connected Group alert viewing is not working but no error is given in console.
        • Task result – CompletedWithInfo not supported with the SDK2007 assemblies.
        • SeriesFactory and Microsoft.SystemCenter.Visualization.DatatoSeriesController need to be public to allow the controls extensibility and reuse
        • WebConsole is not FIPS compliant out of the box.
        • Network Dashboard should overlay Availability when displaying health state
        • Dashboards: Group picker does not show all groups in large environment
        • IIS Discovery: prevent GetAdminSection from failing when framework version was detected incorrectly by IIS API
        • Performance Counters do not show up in Application list view of AppDiagnostics.
        • Console crashes when state view with self-contained object class is opened.
        • PerformanceWidget displays stale ‘last value’ in the legend due to core data access DataModel
        • Availability Report and “Computer Not Reachable” Monitor show incorrect data.
        • Web Services Availability Monitoring Wizard – Console crashes if wizard finishes before test has finished

        More Information on Cumulative Update Rollup 1 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update Rollup 1. This can be found here

      Here are all the Cumulative updates that are released by Microsoft for System Center Operations Manager 2007 r2. A summary of the cumulative Updates can be found here

      • Cumulative Update 7: System Center Operation Managener 2007 r2 Cumulative Update 7 is released on Jan 9, 2013. This Update Resolves the following Issues:
        • Console performs poorly when User Roles are used to scope object access.
        • Availability data is not shown for the current day when daily aggregation is used.
        • Behavior is inconsistent between some views on web console and console.
        • Log files do not roll over when the Unicode log file is monitored.
        • Several security issues are fixed.
        • Logical disk performance statistics are not collected for some volume types on Solaris computers.
        • Some Network Adapters on HP-UX computers may not be discovered.
        • Network adapter performance statistics are not collected for HP-UX network adapters.
        • The Solaris 8 and 9 agent may not restart after an ungraceful shutdown.

        More Information on Cumulative Update 7 can be found here and can be download from here. Roel Knippen wrote a blogpost on how to install Cumulative Update 7. This can be found here

      • Cumulative Update 6: System Center Operation Managener 2007 r2 Cumulative Update 6 is released on May 14, 2012. This Update Resolves the following Issues:
        • RMS promotion fails if NetworkName and PrincipalNames are not in sync for agents.
        • UI is limited to only 100 MB for the Memory Usage field in the wizard.
        • Additional OIDs in auth certificate are not processed correctly.
        • AEM creates duplicate computer objects in OpsMgr based on Agents NetBIOS name.
        • Cannot open reporting pane on OpsMgr 2007 R2 remote console.
        • Cannot view schedule for scheduled report
        • ManagementServerConfigTool with the option “promoterms” fails because it stops polling the SDK Service.
        • OpsMgr reports are failing on Windows 7 with the error: “Cannot initialize report.”
        • ACS events have “n/a” as their category in the ACS database.
        • Watch agentless monitoring listener to detect failure to respond.
        • SCOM SDK memory leak on cryptography keys and cryptography contexts.
        • After you click Edit Schedule, a message box appears, and you cannot save the change value
        • Audit events can be lost when the AdtServer process crashes.
        • The installation process for the IBM AIX 6.1 agent incorrectly checks for AIX 5.3 packages.
        • After a system restart, the OpsMgr agent for Solaris may start to run before local file systems are mounted.
        • On Red Hat Linux version 4 and SUSE Linux version 9, LVM disks are not discovered and cannot be monitored.
        • The OpsMgr agent for AIX does not report the arguments for monitored processes.
        • When Microsoft security update MS12-006 is installed on an OpsMgr management server, that management server can no longer communicate with the OpsMgr agent on any Linux or UNIX server.
        • On HP-UX, OpsMgr cannot discover and monitor a logical volume that is composed of more than 127 physical volumes.
        • Support for IBM AIX 7.1 (POWER).
        • Support for Oracle Solaris 11 (x86 and SPARC).

        More Information on Cumulative Update 6 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update 6. This can be found here

      • Cumulative Update 5: System Center Operation Managener 2007 r2 Cumulative Update 5 is released on July 5, 2011. This Update Resolves the following Issues:
        • Restart of non-Operations Manager services when the agent is updated.
        • Updated ACS reports.
        • TCP Port Probe incorrectly reports negative ping latency
        • MissingEvent Manual Reset Monitor does not work as expected.
        • Drillthrough fails because of rsParameterTypeMismatch in the EnterpriseManagementChartControl.
        • ACS – Event log message is truncated or corrupted in SCDW.
        • UI hang caused by SDK locking.
        • ACS Filter fails for certain wildcard queries.
        • Edit Schedule button is disabled with SQL 2008 R2.
        • Web console times out when you open the left navigation tree.
        • Scheduled Reports view for Windows Server 2003 and for Microsoft SQL Server 2005 Reporting Services SP3 CU9 returns “System.IndexOutOfRangeException: Index was outside the bounds of the array.”
        • Signed MPs cannot be imported when new attributes are added to existing classes.
        • Performance data for LVM managed partitions is not available
        • Process monitor does not keep name if run by using symbolic link.
        • AIX with large number of processes crashes with bad alloc.
        • Support for Red Hat 6

        More Information on Cumulative Update 5 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update 5. This can be found here

      • Cumulative Update 4: System Center Operation Managener 2007 r2 Cumulative Update 4 is released on January 31, 2011. This Update Resolves the following Issues:
        • The Performance and Resource Optimization (PRO) Tips feature does not function correctly after you install Cumulative Update 3 for SCOM 2007 R2.
        • The Alert view does not work correctly when the source of an alert contains both monitors and rules
        • The event description is not collected by the Azure management pack. To resolve this issue, build the Windows Azure application by using Windows Azure SDK 1.3.
        • The monitoring host process may stop responding on a computer that is running on Windows Server 2003 Service Pack 2 (SP2).
        • The performance of the Diagram view is slow if a user role is in the scope of many groups
        • In the web console properties for an alert, the hyperlinks on the Knowledge tab are not active.

        More Information on Cumulative Update 4 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update 4. This can be found here

      • Cumulative Update 3: System Center Operation Managener 2007 r2 Cumulative Update 3 is released on October 1, 2010. This Update Resolves the following Issues:
        • Feature addition: Azure Application Monitoring
        • Feature addition: Parameter Extraction in Web Application Synthetic Transactions
        • Some ACS reports do not work as expected in Windows Server 2008
        • SCOM 2007 SP1 Reports do not run after a shared Data Warehouse is upgraded to SCOM 2007 R2
        • The SDK Services stops working due to an unhandled exception, and the operations console becomes unresponsive
        • Multi-selection in the alert view is not maintained during a view refresh
        • The operations console stops working when creating an override on the cluster resource group monitor
        • When Agentless Exception Monitoring (AEM) is set up to use SharePoint, reports from Watson are blocked
        • The Operations Manger Console stops working when a high number of instances of State Views or Alert Views are left open for extended durations
        • Upgrading MPs that include new properties may not recreate views correctly
        • The total transaction response performance counter in URL monitoring is not accurate
        • MPs with empty knowledge elements cannot be imported in Operations Manager 2007 R2
        • Monitoringhost.exe does not work reliably on Windows 2003 SP2 X64 Domain Controllers
        • Alerts using the “Specific Time Period” criteria are not included during automatic alert view refresh
        • ACS forwarders with 15 character names in workgroups are unable to communicate with the ACS collector
        • Language packs authored for a previous version of an MP cannot be imported once an updated MP is released
        • Language Pack import fails if the MP contains strings which are not contained in the English Management Pack
        • Generic performance reports consume a large amount of temporary database space and can fail for Windows Server 2003 Computer Groups
        • When using a remote console the notification wizard does not work in certain situations
        • The SDK service may stop working due to an arithmetic overflow error in very rare circumstances
        • The notification scheduler does not compensate correctly for different time zones

      More Information on Cumulative Update 3 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update 3. This can be found here

      • Cumulative Update 2: System Center Operation Managener 2007 r2 Cumulative Update 2 is released on June 29, 2010. This Update Resolves the following Issues:
        • The Network Devices State view does not display the device name.
        • The discovery process fails when a double-byte character is inserted into a string that is searched
        • The availability reports that are exported as TIF files or as PDF files are truncated.
        • The property bags of WMIEventProvider module do not support the including or excluding of specific properties
        • The color of the chart lines does not match the legend in the Web console in the Performance view.
        • When SQL Reporting Services is enabled in SCOM by using the United States Federal Information Processing Standards (FIPS) security, the datawarehouse encounters an InvalidOperationException error
        • The monitoring host process does not start the workflows immediately when tasks are received
        • The Operations Manager console crashes when you open multiple customized views in a new window.
        • The Allow Anonymous discovery property in the Internet Information Services (IIS) Management Pack is incorrect in the console.
        • When you run updates, a restart dialog box is shown before the files for the update are delivered.
        • The agent update packages are not deployed to the servers that have the Terminal Services Gateway (TS Gateway) role installed or that have the Remote Desktop Gateway (RD Gateway) role service installed.
        • Audit Collection Services stops collecting data if the Event Log service uses the automatic backup feature

        More Information on Cumulative Update 2 can be found here and can be download from here. Kevin Holman wrote a greath blogpost on how to install Cumulative Update 2. This can be found here

      • Cumulative Update 1: System Center Operation Managener 2007 r2 Cumulative Update 1 is released on January 30, 2010. This Update Resolves the following Issues:
        • The Product Knowledge tab is displayed as the Company Knowledge tab after you import a language pack for System Center Operations Manager 2007 R2.
        • An agent cannot be removed successfully from a Windows Cluster service node
        • The Heathservice.exe process on a Windows Cluster service passive node may have excessive CPU utilization.
        • The Healthservice.exe process may crash when it uses the OLE DB module.
        • The workflows that use the OLE DB data source may unload themselves if the underlying provider returns a null string or an empty string.
        • An instance of the MonitoringHost.exe process may cause a memory leak in nonpaged pool memory.
        • The notification subscriptions do not work if they are configured to parse a CustomField field or an AlertOwner field.
        • The Operations console loses the status as the current object that is in focus when a search filter is applied.
        • The SRSUpgradeTool.exe process returns an error that states “Failed while updating registry entry for reporting code MSI component” when you try to upgrade SQL Reporting Services 2005 to SQL Reporting Services 2008.
        • The Operations Manager UI may crash when the Connector column and the Forwarding Status column are added to an Alert view.
        • The agents may re-process old Windows event log entries and then incorrectly generate alerts for these events that are not new.
        • Health state reliability fixes and improvements.
        • The Operations Manager Audit Collection Service (ADTServer.exe) does not start on an ACS Collector if the operating system is upgraded to Windows Server 2008 R2.
        • In a performance report that is exported, the list of object instances is not displayed

        More Information on Cumulative Update 1 can be found here and can be download from here. Cumulative Update 1 is included in Cumulative Update 2 Kevin Holman wrote a greath blogpost on how to install Cumulative Update 2. This can be found here