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

Create A Unit Monitor based on a EventID

Standard

In this blog post I am going to take you true the steps that I took to create a Unit Monitor.

A Unit Monitor measures aspects of an application. The monitor can be checking a performance counter tot determine the performance of an application, running a a script to perform a Synthetic transaction, or watch for an event that indicates an error or warning.

I’m going to create a unit monitor using the SMS-Passcode event log based on Unhealthy Event 150 (SMS-Passcode: Modem has been blacklisted and will not restart automatically anymore) and the Healthy Event 202 (SMS-Passcode: Modem Initialization successful (COM 3))

  1. Start the "System Center Operations Manager Console"
  2. In the "System Center Operations Manager Console", click the "Authoring"

    SelectAuthoring

  3. On the "Authoring" pane, expand "Authoring", expand "Management Pack Objects", and the select "Monitors"

    SelectMonitors

  4. In the "System Center Operations Manager console", in the "Tasks" pane click "Create a Monitor"

    CreateMonitor

  5. Select the "Unit Monitor"

    UnitMonitor

  6. On the "Create a unit Monitor" wizard, on the "Monitor Type" page in the section "Select the type of monitor to create", expand "Windows Events", "Simple Event Detection" and select "Windows Event Reset". On the section "Management Pack" on the page "Select a Monitor Type" click "New"

    NewManagementPack

  7. On the "Create a Management Pack" wizard, on the "General Properties" page in the section "Management Pack General Properties", give the management pack a "Name" and click "Next"
  8. On the "Create a Management Pack" wizard, on the "Knowledge" page click "Create"
  9. On the "Create a Unit Monitor" wizard, on the "Monitor Type" page click "Next"

    MonitorType

  10. On the "Create a Unit Monitor" wizard, on the "General" page, in the "General Properties" section, give the monitor a "Name" and on the "Monitor Target" line click "Select
  11. In the "Select Items to Target" wizard, select "Window Computer" and click "OK"

    WindowComputer

  12. On the "Create a Unit Monitor" wizard, on the "General" page, in the "General Properties" section, under "Parent monitor" select "Availability", uncheck "Monitor is enabled" and click "Next"

    GeneralMonitorProperties

  13. On the "Create a Unit Monitor" wizard, on the "Event Log (Unhealthy Event(" page, in the "Specify the event log to read the events from" section, click ""
  14. On the "Select Event Log" wizard in the section "Browse or enter computer name", select the computer you want to read the event log from
  15. On the "Select Event Log" wizard in the section "Available event logs", select "SMS Trans" and click "OK

    SelectEventLog

  16. On the "Create a Unit Monitor" wizard, on the "Event Log (Unhealthy Event(" page, click "Next"
  17. On the "Create a Unit Monitor" wizard, on the "Event Expression (Unhealthy Event)" page in the "Filter one or more events" section, behind the "Event ID" enter "150" and behind the "Event Source" enter "SMS Dispatcher and click "Next"

    EventExpressionUnhealthy

  18. On the "Create a Unit Monitor" wizard, on the "Event Log (Healthy Event(" page, in the "Specify the event log to read the events from" section, click ""
  19. On the "Select Event Log" wizard in the section "Browse or enter computer name", select the computer you want to read the event log from
  20. On the "Select Event Log" wizard in the section "Available event logs", select "SMS Trans" and click "OK

    SelectEventLog

  21. On the "Create a Unit Monitor" wizard, on the "Event Log (Healthy Event(" page, click "Next"
  22. On the "Create a Unit Monitor" wizard, on the "Event Expression (Healthy Event)" page in the "Filter one or more events" section, behind the "Event ID" enter "202" and behind the "Event Source" enter "SMS Dispatcher and click "Next"

    EventExpressionHealthy

  23. On the "Create a Unit Monitor" wizard, on the "Configure Health" page on the section "Map monitor conditions to health states" change the "First Event Raised" to "Critical" and click "Next"

    ConfigureHealth

  24. On the "Create a Unit Monitor" wizard, on the "Configure Alerts" page on the section "Alert Settings" and select "Generate alerts for this Monitor" and click "Create"

    ConfigureAlerts

Now that we have created the monitor it’s time to enable the Monitor.

  1. Start the "System Center Operations Manager Console"
  2. In the "System Center Operations Manager Console", click the "Authoring"
  3. On the "Authoring" pane, expand "Authoring", expand "Management Pack Objects", and the select "Monitors"
  4. On the "Monitors" pane, in the "Look for" input box type "sms"

    LookForSMSPasscode

  5. Select the "SMS PASSCODE Transmission" monitor, and from the "Tasks" pane click "Overrides", "Override the Monitor" and click "For al specific object of class: System Center Managed Computer (Server OS)"

    OverrideForSpecificObjectOfClass

  6. On the "Select Object" wizard, search for the computer that you have have SMS-Passcode installed on and click "OK"
  7. On the "Override Properties" wizard, in the "Override-controlled parameters" section, select "Enable" and change the "Override Value" to "True". Then click "OK".

    OverrideProperties

When the event 150 is raised You will get a warning in the Event-log on the client and in System Center Operations Manager an Alert is generated

AlertProperties

When the issue is resolved and event-id 202 is logged in the Event-Log in the the client. The generated Alert in System Center Operations Manager is Automaticaly closed.