Disable Discovery of a SQL Server.

Standard

In my environment I have a couple of SQL severs that are being discovered by the System Center Management Pack for SQL Server where I don’t want to monitor the SQL Server application.

I took the following steps to complete this option:

  1. Create a Group with the client computers you don’t want to monitor
  2. Apply Overrides to Object Discoveries
  3. Run "Remove-SCOMDisabledClassInstance"

1. Create a Group with client Computers  you don’t want to monitor

  1. Start the "System Center Operations Manager Console"
  2. In the System Center Operations Manager console, click "Authoring"
  3. Right-click "Groups", and then click "Create a new Group" to start the Create Group Wizard.
  4. On the "General Properties" page, Enter a "Name", "Description" and select the management pack you want to use. Click "Next" General Properties Group
  5. On the "Explicit Members" page, click "Add/ Remove Objects" Add/ Remove Objects
  6. On the "Create Group Wizard – Object Selection" page, enter the computer name you don’t want to monitor in the "Filter by part or name(Optional)" box. In the "Available Items" box select the computer object and click "Add" and click "Ok"Create Group Wizard - Object Selection
  7. On the "Explicit Members" page, click "Next"
  8. On the "Dynamic Members" page, click "Next"
  9. On the "Sub Groups" page, click "Next"
  10. On the "Excluded Members" page, click "Create"

2. Apply Overrides to Object Discoveries

  1. Start the "System Center Operations Manager Console"
  2. In the System Center Operations Manager console, click "Authoring"
  3. On the "Authoring" page, expand "Management Packs" and select "Object Discovery"
  4. Click the "Scope" button on the Operations Manager toolbar
  5. On the "Scope Management Pack Objects" page, in the look for bar type "SQL " and select the target "SQL Server 2005 DB Engine", “SQL Server 2008 DB Engine”, “SQL Server 2012 DB Engine” and click "OKScope Management Pack Objects
  6. Click “Find Now
  7. Right click on "Discover SQL Server 2005 Database Engines (Windows Server)" and click "Overrides", "Override the Object Discovery", "For a group" Override the Object Discovery
  8. On the "Select Object" page, select the group that you created above
  9. On the "Override Properties" page, check "Enabled" and change the "Override Value" from “True", to "False" and select the "Management Pack" where you want to store the overrides. Click "Apply" and "OK" Override Properties
  10. Repeat the above steps for "Discover SQL Server 2008 Database Engines (Windows Server)" and the "Discover SQL Server 2012 Database Engines (Windows Server)"

3. Run "Remove-SCOMDisabledClassInstance"

  1. Start the "Operations Manager Shell"
  2. At the command prompt Type "Remove-SCOMDisabledClassInstance" and press "Enter"
  3. Answer the Question by pressing "Y" and press "Enter"

    Operations Manager Shell

Now the SQL Servers that were discovered will not be discovered and be removed from the computers state view in the SQL Management Pack

Change the Grooming Settings of the SCOM Databases

Standard

In this blog post i ’am going to take you true the steps that are needed for changing the retention time of the databases that are used in System Center Operations Manager.

System Center Operations Manager 2012 makes use off the following Databases:

  • Operational Database (named: OperationsManager)
  • Data Warehouse Database (named: OperationsManagerDW)
  • ACS DataBase

Operational Database (Named: OperationsManager).

The Operational Database is a SQL Server Database that contains all configuration data for the management group  and stores all monitoring data that is collected and processed for the management group. The Operational database retains short-term data, by default 7 day’s.

The Operations Database needs 50% free space at all time. This for growth, and for re-indexing operations to complete successful. When the free space in the Operations Database is going below 40 % System Center Operations Manager will generate a Alert.

I prefer not to increase the the default off 7 day’s and reduce the performance Data and the Event Data to 4 or 5 day’s. When setting up your System Center Operations Manager environment I will set the Database Grooming settings to two day’s to just to reduce the noise that is generated during the setup, configuring and the import off Management Pack’s

Step’s I took to change the Performance Data and the Event Data:

  1. Start the "System Center Operations Manager Console
  2. In the "Operations Manager Console" click "Administration"
  3. In the "Navigation" pane expand "Administration and click "Settings
  4. In the "Settings" pane, right click "Database Grooming" and the click "Properties"
  5. In the "Global Management Group Setting – Database Grooming" dialog box, select "Performance Data", and click "Edit"

    DatabaseRetention

  6. In the "Performance Data" dialog box, specify "Older than" days, and the click "Ok". I changed the value into 4

    PerformanceData4Days

  7. Repeat step 5 and 6 for the "Event Data"
  8. In the "Global Management Group Setting – Database Grooming" dialog box, click "Apply" and click "Ok"

Know that we have changed the database grooming for the OperationsManager database time check if the grooming is working correct.

Grooming off the OperationsManager Database is done by the rule “Partition and Grooming” and runs  once a day at 0:00. The rule is targeted against to the “All management Servers Resource Pool” and is part of the System Center Internal Library. More information on the Partition and Grooming rule can be found here

To check if the Partition and Grooming rule is working you can run the following SQL query:

select * from InternalJobHistory order by InternalJobHistoryId

The Result should look something like this:

SQLQueryResult

Data Warehouse Database (named: OperationsManagerDW)

The data warehouse database is a SQL Server database that stores monitoring and alerting data for historical purposes. Data that is written to the Operations Manager database is also written to the data warehouse database, so reports always contain current data. The data warehouse retains long-term data.

Different data are kept in the data warehouse in unique “Datasets”. A dataset is a set of tables and stored procedures. System Center Operations Managed datasets are used to store historical data. The default dataset consist of the following sets out of the box:

  • Performance Data set
  • State data set
  • Event data set
  • APM data set
  • Alert data set
  • Client Monitoring data set

To get the data sets that are available in your System Center Operations Manager Environment:

select * from Dataset 

The result should look something like this:

selectfromDataset

The most common datasets that we will aggregate are the Performance data set, State data set and Client monitoring data set. We have raw, hourly and daily aggregations.

When you have a default installations of System Center Operations Manager 2012 the data is stored by type, and the ranges from 10 to 400 day’s depending on the data. You can see the grooming setting’s of the OperatinsManagerDW database using the following SQL command:

<pre class="lang:default decode:true " >USE OperationsManagerDW
SELECT AggregationIntervalDurationMinutes, BuildAggregationStoredProcedureName, GroomStoredProcedureName, MaxDataAgeDays, GroomingIntervalMinutes, MaxRowsToGroom FROM StandardDatasetAggregation</pre> 

The result should look something like this:

GroomingConfiguration

Let’s change the the “EventGroome” Stored procedure from “100”  age days to “50” day’s

Use OperationsManagerDW
Update StandardDatasetAggregation set MaxDataAgeDays = 40 where GroomStoredProcedureName = 'EventGroom' 

To check if the change is applied run the following sql-query:

USE OperationsManagerDW
SELECT AggregationIntervalDurationMinutes, BuildAggregationStoredProcedureName, GroomStoredProcedureName, MaxDataAgeDays, GroomingIntervalMinutes, MaxRowsToGroom FROM StandardDatasetAggregation where GroomStoredProcedureName = 'EventGroom'

CheckEventGroomStatus

If you want to change other stored procedures you can download the following Script

ACS Database

When installing ACS into your environment you during the installation process you can set the “Number of days an event is retained in database”. The default configuration is 14 days.

ACSRentetionDefault

You can change the Data Retention using the following SQL Query:

USE OperationsManagerAC
UPDATE dtConfig SET Value = number of days to retain data + 1 WHERE Id = 6

More information on grooming can be found here:

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

      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 Firewall ports

      Standard

      When installing System Center Operations Manager you want to keep the local firewall on your servers up and running. You can use the following commands to open the ports you need.

      For the command's below to work run the "command prompt as administrator".

      Run this on the SQL Server that is the Database server for your Management Servers:

      • netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = localsubnet profile = DOMAIN
      • netsh advfirewall firewall add rule name = SQLBrowserPort dir = in protocol = tcp action = allow localport = 1434 remoteip = localsubnet profile = DOMAIN
      • netsh advfirewall firewall add rule name = ServiceBroker dir = in protocol = tcp action = allow localport = 4022 remoteip = localsubnet profile = DOMAIN

      un this on the Server that is the The web server for Operations Manager:

      • netsh advfirewall firewall add rule name = HTTP dir = in protocol = tcp action = allow localport = 80 remoteip = localsubnet profile = DOMAIN
      • netsh advfirewall firewall add rule name = HTTPS dir = in protocol = tcp action = allow localport = 443 remoteip = localsubnet profile = DOMAIN

      Run this on each of the System Center Management Servers:

      • netsh advfirewall firewall add rule name = MgmtPort dir = in protocol = tcp action = allow localport = 5723 remoteip = localsubnet profile = DOMAIN
      • netsh advfirewall firewall add rule name = MgmtConsole dir = in protocol = tcp action = allow localport = 5724 remoteip = localsubnet profile = DOMAIN

      When you are using SNMP Network Monitoring run the following commands System Center Management Servers:

      • netsh advfirewall firewall set rule name="Operations Manager Ping Response (Echo Response – ICMPv4 IN)" new enable=yes
      • netsh advfirewall firewall set rule name="Operations Manager SNMP Response" new enable=yes
      • netsh advfirewall firewall set rule name="Operations Manager SNMP Trap Listener" new enable=yes

      More information on the "netsh advfirewall firewall" command, can be found here. If you want more information on the firewall ports take a look at the following technet article. This can be found here