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

The following issues are fixed in this Update

  • Operational Insight through Operations Manager
  • Support for “SUSE Linux Enterprise Server systems

You can download the Update Rollup 9 form here
The downloaded files consist of an update for the “System Center Operations Manager Console” and the “System Center Operations Manager Server. 

Microsoft Update Catalog

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 Operations Manager Console
  5. Run the SQL scripts
  6. Import Management Pack’s
  7. 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

    Backup Database

  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 "KB3023167-AMD64-Server.msp"

    ManagementServerUpdate

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

    ManagementServerUpdate1

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

    ManagementServerUpdate2

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

    UpdateConsole1

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

    UpdateConsole2

 

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

6. 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
  5. Click "Install"

    ImportManagmentPacks

  6. Click "Close"

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 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" view you should see something like this:

    Ready

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

        Health Service Unloaded System Rule(s)

        Standard

        In my System Center Operations Manager 2007 r2 I ran into the following error.

        HealthServiceUnloadedSystemRules

        I used the following steps to fix the error

        • Restart the healthservice on the agent. I used the command line to stop the service: "net stop HealthService" and to start the service: "net start HealthService". This could solve the issue above. In my case it didn’t
        • Option 1: Clear the HealthService queue and config (manually). Stop the health true "net stop healthservice" and browse to the following directory "C:\Program Files\System Center Operations Manager 2007\Health Service State" and delete al folders and files in that directory. Start the HealthService "net start HealthService"
        • Option 2: Clear the HealthService queue and config (from the console). Start the "Operations Manager Console" and browse to "Monitoring, Operations Manager, Agent and select Agent Health State", Select the server wich is generating the alert. From the Actions pane Click "Flush Health Service State And Cache"

          FlushHealth

        • Option 3: Repair the agent. Start the "Operations Manager Console" and browse to "Administration, Device Management, Agent Managed", Select the troubled agent and from the actions pane select "repair"

          RepairAgent

        • Option 4: Reinstall the agent

        More information on this issue can be found on the blog of Kevin Holeman

        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

        Agentless Monitoring Part 2

        Standard

        In Part 1 of agentless monitoring I explained how to configure Agentless Monitoring. In this Part I will explain Agentless Exception Monitoring(AEM).

        Agentless Exception Monitoring is an extension of Dr. Watson. Dr Watson is responsible for capturing application errors and the forward the to Microsoft if needed. When you are a home user this could be a viable option. When you are working in a organisation , the data that is collected by Dr Watson is could contain insight information of the organization that you don’t want to share with Microsoft.

        When you implement Agentless exception Monitoring, Dr Watson collects the application errors and stores them in on the AEM infrastructure that is hosted by your organization.

        AEM Relies on two configuration options to Function:

        1. Run the configuration Wizard from the System Center Operations Console
        2. Create a Group Policy to configure the Clients

        Run the configuration Wizard from the System Center operations Console

        1. Start the System Center Operations Manager Console 2007 r2
        2. Select the "Administration" workspace
        3. Expand "Device Managed" and select "Management Servers"
        4. Right click the RMS and select"Configure Client Monitoring"

          ConfigureClientMonitoring

        5. On the "Introduction" page, click "Next"
        6. On the "CEIP Forwarding" page, click "Yes, use the selected management server to collect and forward CEIP data to Microsoft", Clear the "Use Secure Socket Layer (SSL) protocol" and click "Next"

          CustomerExperienceImprovementProgram

        7. On the "Error Collection" page, Fill in the "File Share Path", Check of the "Collect error from Windows Vista-based or later clients" is checked and clear the "Use Secure Sockets (SSL) protocol" check box. In the Organization Name type the name you want to Use

          ErrorCollection

        8. On the "Error Forwarding" page, Click "Next"
        9. On the "Create File Share" page, Click "Other user account(will not be saved)" and fill in a domain administrator account
        10. On the "Create File Share: Task Status" page, click "Next"
        11. On the "Client Configuration Settings" page, Select a location where you want to store the administrative template and click "Finish"

        Create a Group Policy to Configure the clients

        1. Start the Group Policy Management Console
        2. Browse to the Organizational Unit where you want to create the Group Policy
        3. Right click the Organizational Unit and click "Create a GPO in this domain, and link it here…"
        4. Give the New GPO a name and click "OK"
        5. Edit the GPO
        6. Navigate to "Computer Configuration, Policies, Administrative Templates"
        7. Right click "Administrative Templates" and click "Add/Remove Templates"
        8. On the "Add/Remove Templates" dialogue click "Add" and select the created template from above click "Open". Click "Close"
        9. Navigate to "Computer Configuration, Policies, Administrative templates, Classic Administrative Templates(ADM), Microsoft Application, System Center Operations Manager (Scom)"
        10. Select "Scom Client Monitoring CIEP Settings", Open "Configure CEIP (Customer Experience Improvement Program)" click "Enable" and configure the CEIP Settings "http://rms.ms-opsmgr.eu:51907/" Click "Apply", click "OK"
        11. Select "Scom Monitoring", Open "Configure Error Reporting for Windows Vista and later operating Systems" , click "enable" and verify that the correct settings are configured and click "Apply" and click "OK"
        12. Select "Scom Monitoring", Open "Configure Error Notification", click "Enable" and verify that "ShowUI" in unchecked and "DoNotDebugErrors" is checked. CLick "Apply" and "OK"
        13. Navigate to "Computer Configuration, Policies, Administrative templates, Classic Administrative Templates(ADM), Microsoft Application, System Center Operations Manager (Scom), Scom Monitoring"
        14. Select "Advanced Error Reporting settings", open "Application reporting settings (all or None)", "Enable" check if all options are selected and Click "Apply" and "OK"
        15. Select "Advanced Error Reporting settings", open "Report Operating System Errors", "Enable" check if all options are selected and Click "Apply" and "OK"
        16. Select "Advanced Error Reporting settings", open "Report unplanned shut-down events, "Enable" check if all options are selected and Click "Apply" and "OK"
        17. Navigate to "Computer Configuration, Policies, Administrative templates, Classic Administrative Templates(ADM), Microsoft Application, System Center Operations Manager (Scom)"
        18. Select "SCOM Client monitoring for Office 10.0 Applications" open "Configure Error Notification, "Enable and make sure that the Option "ShowUI" is not selected. Click "Apply and "OK"
        19. Close the Group Policy Management Console

        Now the configuration is done. Time to do some testing and see if it’s working. You can add a registry key to a client computer to add the feature to generate a crash.

        1. Start the registry editor on your windows test system
        2. browse to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters"
        3. Create a new DWORD Value. Name the new key "CrashOnCtrlScroll", and set value 1
        4. Restart the computer

        When you computer is up and running again, you should be enable to generate a blue screen by holding down the right Ctrl key and click Scroll Lock twice.

        When you open the System Center Operations Manager Console and you select Agent less acceptation Monitoring. You could select a view to see the alerts generated

        MonitoringAgentless

        Big thank’s to Pete Zerger and Anders Bengtsson who wrote a great article on Agent less Exception Monitoring. This can be found at System Center Central

        Agentless Monitoring Part 1

        Standard

        In this blog post I will explain how to configure agentless monitoring in System Center Operation Manager 2007 r2. There are two types off Agentless Monitoring:

        • Agentless Monitoring
        • Agentless Exception Monitoring

        In this Part I will explain how to configure Agentless-Monitoring.

        AgentLess Monitoring

        Agentless management of computers is different from Agentless Exception Monitoring. Agent Exception Monitoring is used tot aggregate, vies and report on error reports that are sent by the Windows Error Reporting Service

        The discovery wizard can find and Setup systems for agentless management. It is almost the same as deploying a agent to a client. The difference is that you need configure a proxy for each agentless-managed system.

        Configure a Proxy for agentless-managed computers

        1. Start the System Center Operations Manager 2007 R2 Operating Console
        2. Click the tab "Administration"
        3. Select "Agent Managed"
        4. Open the "Agent Properties" and click the "Security" tab

          ProxyAgent

        5. On te "Security" tab, select "Allow this agent to act as proxy and discover managed objects on other computers" and click "OK"

          ProxyAgentEnabled

        When you enabled enable a agent to serve as proxy. You will see the following event logged on your System Center Operations Manager 2007 R2 Server and on the server that you configured as agent Proxy

        EventViewerNewConfiguration

        When you remove the agent Proxy the agentless systems are no longer managed.

        Discover windows Computers to manage them as Agentless-managed Computers

        1. Start the System Center Operations Manager 2007 R2 Operating Console
        2. Click the tab "Administration"
        3. Start the "Discovery Wizard"
        4. On the "Discovery Type" page, select "Windows Computers" and click "Next"
        5. On the "Auto or Advanced" page, select "Advanced discovery"
        6. On the "Auto or Advanced" page, in the "Computer and Device Classes" list, select "Server and Clients"
        7. On the "Auto or Advanced" page, in the "Management Server" list, select the Management Server you want to use to discover the computer and click "Next"
        8. On the "Discovery Method" page, select "Browse for, or type-in computers name",browse for the computer you want to discover and click "Next"
        9. On the "Administrator Account" page, select "User selected Management Server Action Account" and click "Discover"
        10. On the "Select Objects to Manage" page, select the discovered Server. Click "Change" and select the Proxy Agent you want to Use. In the "Management Mode" select "Agentless" and click "Next"

          AgentlessConfigurationDiscovery

        11. On the "Summary" page, click finished
        12. In the System Center Operations Manager Console, click Administration and select "Agentless Managed" and check if the windows computer is monitored

          AgentlessMonitored

        More Information on agentless Monitoring can be found here.

        Maintenance Mode Explained

        Standard

        Maintenance mode is a option in System Center Operation Manager 2007 r2 and System Center Operation Manager 2012. You can use the maintenance mode option when you are planning a software update or when you planning a hardware upgrade.

        When you place a Agent in maintenance mode the workflows that are targeted against the Agent will be susppended during the Maintenance mode. This wil prevent the generation of alerts and notfications. When a Agent is in maintenance mode the following will be suppressed at the agent:

        • Alerts
        • Notifications
        • Rules
        • Monitors
        • Automatic Respones
        • State Changes
        • New Alerts

        When you place a Agent in Maintenance mode the following event is generated in the operations Manager Eventlog

        EventProperties1216HealthService

        Placing a Agent into Maintenance Mode

        1. Open the Operations Manager Console
        2. Under the "Monitoring" expand "Microsoft Windows Server" and select "Windows Server State"

          SystemCenterOperationsManagerConsole

        3. This wil list al the servers that are monitored by System Center Operations Manager
        4. Select a "Agent" and in the "Actions" screen Click "Start Maintenance Mode"

          Actions

        5. In the Maintenance mode settings screen. Select "Selected Objects and all their contained objects" This will put the complete server in Maintenance mode. In the "Category" select the catagory of wich this maintenance mode is placed. Then you select the "Time interval" for the maintenance mode using the option under "Duration" Remember this is required. Press "OK"

          MaintenanceModeSettings

        What happens in the background when placcing a Agent in Maintenance Mode?

        1. When you place an agent into Maintenance Mode a call is made to the SDK service to trigger the Maintenance Mode for the agent and the workflow running on that agent are unloaded.
        2. A Configuration update is calculated and sent to the agent. When you check the event log on the agent that is put in Maintenance Mode you see the event 1210 is created on the agent

          EventProperties1210HealthService

        3. On a schedule the RMS checks of the maintenance mode is expiring.
        4. When the maintenance mode is expired, a updated is sent to the agent and the workflows are loaded on the agent

        Scheduling Maintenance Mode

        Default can System Center Operations Manager 2007 r2 not allow scheduling maintenance mode. But when you install System Center Operations Manager 2007 r2 Admin Resource Kit you can schedule Maintenace Mode. You can download the Operations Manager R2 Admin Resource Kit from here You can also use the community tool: SCOM Remote Maintenace Mode Scheduler writen by Tim McFadden

        For System Center Operations Manager 2012 the Admin Resource Kit is not yet available

        More information on Maintenance mode can be found: