(Re-)Create Data Warehouse Action Accounts

Standard

In my System Center Operations Manager 2012 Service Pack 1 Update Rollup 9 environment. I was seeing al lot off the following Event’s in the event viewer:

  • Event-ID 8000
    EventID 8000
  • Event-ID 2115
    Event ID 2115
  • Event-ID 31522
    Event ID 31522

After some investigation it looked like there where no “Data Warehouse Action Account” and “Data Warehouse Report Deployment Account” available in the accounts tab in the System Center Operations Console.  I took the following steps to recreate the Data Warehouse accounts and associate them whit the right Run as Profile. This is a small environment, I will be using the same active Directory account for “Data Warehouse Action Account” and “Data Warehouse Report Deployment Account

  1. Start “System Center Operations Manager Console
  2. In the “System Center Operations Manager Console” click “Administration
  3. In the “Administration” workspace, Right click “Accounts” and click “Create Run As Account
    Create Run As Account
  4. In the “Create Run As Account Wizard” on the “Introduction” page, click “Next
  5. On the “General Properties”page, do the following:”
    • Select “Windows” in the Run As Account type list
    • Type a display name in the “Display Name” text box named “Data Warehouse Action Account
    • Type a description in the “Description box” named “Data Warehouse Action Account
    • Click “Next

    Create Run As Account - General Properties

  6. On the “Credentials” page, type a “user name“, and its “password“, and then select the “Active Directory Domain” for the account that you want to make a member of this Run As account. Click “NextCreate Run As Account - Credentials
  7. On the “Distribution Security” page, select the “More secure” option. Click “Create
    Create Run As Account - Distribution Security

Repeat the above steps to create the “Data Warehouse Report Deployment Account“. Now we need to modify the “distribution settings” of the “Run As Account“,

  1. Start the “System Center Operations Manager Console
  2. In the “System Center Operations Manager Console” click “Administration
  3. In the “Administration page” expand “Run As Configuration” and select “ProfilesRun As Configuration Profiles
  4. In the results pane, double-click the “Data Warehouse Action Account” to open its properties. Run As Configuration Profiles
  • On the “Run As Profile Wizard“, on the “Introduction” page click “Next
  • On the “General Properties” page, click “Next
  • On the “Run As Accounts” page, click “Add
    Run As Configuration Profiles
  • On the “Add a Run As Account” page, in the Run As Account pull down box select the “Data Warehouse Action Account” and in the “This Run As Account will be used to manage the following objects” section select “A selected class, group or object”, On the select button click “ClassRun As Configuration Profiles
  • On the “Class Search” page, in the filter section type “Data Set” and click “Search”. In the “Available Items” select “Data Set” and click “OKRun As Configuration Profiles 5
  • Repeat the step 7 till 8 only when you use the “Class Search” use the following values: “Collection Server”, “Operations Manager APM DATA Transfer Service”, “Data Warehouse Synchronization Server”. When finished the result should look something like this:Run As Configuration Profiles
  • On the “Run As Profile Wizard”, click “Save
  • On the “Wizard completed successfully” click “Close
  • Now we need to repeat the above steps for the “Data Warehouse Report Deployment Account
  • Double click the “Data Warehouse Report Deployment Account
  • On the “Introduction” page, click “Next
  • On the “General Properties” page, click “Next
  • On the “Run As Accounts” page, click “AddRun As Configuration Profiles
  • On the “Add a Run As Account” page, in the Run As Account pull down box select the “Data Warehouse Report Deployment Account” and in the “This Run As Account will be used to manage the following objects” section select “A selected class, group or object”, On the select button click “ClassRun As Configuration Profiles
  • On the “Class Search” page, in the filter section type “Data Warehouse Synchronization Server” and click “Search”. In the “Available Items” select “Data Warehouse Synchronization Server” and click “OKRun As Configuration Profiles
  • Repeat the step 17 till 18 only when you use the “Class Search” use the following values: “Collection Server”. When finished the result should look something like this:Run As Configuration Profiles
  • On the “Run As Profile Wizard”, click “Save
  • On the “Wizard completed successfully” click “Close

Now that the accounts and the Profiles are connected restart the server and the event 8000, event 2115 and event 31522 should disappear.

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

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

Operations Manager Failed to start a process

Standard