Rick

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

    $Output = C:WindowssysnativeWindowsPowerShellv1.0powershell.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?

  • 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…[Read more]

  • Rick became a registered member 3 months, 2 weeks ago