SCOM 2007 Alert States

Forum: Orchestrator
Viewing 2 posts - 1 through 2 (of 2 total)
  • #230272
    Profile photo of Rick
    Rick
    Participant

    I have an Orchestrator runbook monitoring for SCOM 2007 alerts that does the following:
    Monitor Alert > Change ResolutionState > Execute Runbook2

    When a new alert is generated in ‘Monitor Alert’ Orchestrator picks it up, changes the resolution state to a custom state, and then more magic happens in Runbook2.

    I need to work around the following scenario:

    1. SCOM generates a new alert
    2. Orchestrator picks up new alert (Monitor Alert)
    3. SCOM closes the alert (Alert Resolved by the System)
    4. Orchestrator changes ResolutionState
    5. Runbook2 executed

    In this scenario the ResolutionState has changed from ‘New’, to ‘Closed’, to ‘MyCustomState’ in the span of a few seconds. When Runbook2 executes it checks in multiple spots to see if the alert’s ResolutionState equals ‘Closed’, which is a state that will never be automatically returned to.

    Can I query the alert for something other than ResolutionState to see if the alert has been healed?

    #230273
    Profile photo of Rick
    Rick
    Participant

    Follow up. ¬†Why shouldn’t I do this:

    $Output = C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe -NonInteractive -Command {$Code}

    That takes me from a 32-bit v2 session to a 64-bit v4 (on my server) session. As hard as it was to find this solution where’s the catch?

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.