Backup Management Pack’s

Standard

Backup all System Center Operations Manager 2012 Management Pack’s. I took the following steps to complete this task.

Launch the System Center Operations Manager shell

OperationsManagerShell

Get-SCManagementPack | Export-SCManagementPack -Path D:\Backup\ManagementPack

OperationsManagerShellBackup

If you are using System Center Operations Manager 2007 r2 Use the following command line:

Get-ManagementPack | Export-ManagementPack -Path D:\Backup\ManagementPack

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

    Diagnostic and Recovery Time-Out

    Standard

    When I run a Diagnostic and Recovery task and the Diagnostic or Recovery task runs longer then 5 minutes the Diagnostic or Recovery task will fail.

    The Issue

    I have created a unit monitor based on a SNMP Probe Monitor using the following OID: .1.3.6.1.4.1.318.1.1.10.2.2.2.1.4.1. After that I created the following script based recovery task:

    • A Visual Basic script which calls a powershell script. You can download the Visual Basic script from here

    • A Powershell script which runs the time-out script. You can download the Visual Basic script from here

      <?xml version="1.0"?>

    • A Powershell function which is used to calculate the Current Time. You can download the Visual Basic script from here

      <?xml version="1.0"?>

    When you generate an alert. The Recovery task is started but after 5 minutes the Recovery Tasks stops running.

    The Fix

    • Start the "System Center Operations Manager Console" select "Administration" and click "Management Packs"
    • Select the management pack that you saved the recovery task to and in the tasks pane click "Export Management Pack"

      ExportManagementPack

    • Select a path or location where you want to export the management pack to and click "Ok"
    • Open the exported xml and search for the "Recovery ID" element. My part of the code looks like this:

      <?xml version="1.0"?>

    • The Time-out value equals 300 which is equal to 5 minutes. I replaced this Value to 3600 which equals 1 hour. The Code should look something like this:

      <?xml version="1.0"?>

    • Save the XML
    • Start the "System Center Operations Manager Console" select "Administration" and click "Management Packs"
    • CLick "Import Management Pack" and browse tot XML and import the Management Pack
    • Run the test again and the output should look something like this.

      result