SCOM: Retrieve Worflow Details

September 11, 2014

Many times in SCOM you will see Alerts concerning processes that failed to start. Such as “Operations Manager failed to start a process or script” and within the alert you get the workflow name i.e. “Microsoft.SQLServer.2008.ReportingServicesDiscoveryRule.Server”

Here’s a little powershell script that will give you more details upon this workflow. It will tell you wheter it concerns a discovery, monitor  or rule” and the class on which it is targeted. This info will help you in defining overrides for these alerts in the Authoring pane.



 [String] $Workflow
$Discovery = Get-SCOMDiscovery -Name $Workflow
$Rule = Get-SCOMRule -Name $Workflow
$Monitor = Get-SCOMMonitor -Name $Workflow

If ($Discovery -ne $NULL)
$Class = get-scomclass -Id $Discovery.DiscoveryClassCollection.TypeId.Id
Write-host (“Discovery : {0} – Class: {1}” -f $Discovery.DisplayName,$Class.DisplayName)
Elseif ($Rule -ne $NULL)
write-host “R”
$Class = get-scomclass -Id $Rule.Target.Id
Write-host (“Rule : {0} – Class: {1}” -f $Rule.DisplayName,$Class.DisplayName)
Elseif ($Monitor -ne $NULL)
$Class = get-scomclass -Id $Monitor.Target.Id
Write-host (“Monitor : {0} – Class: {1}” -f $Monitor.DisplayName,$Class.DisplayName)
Write-host “Workflow not found”


Screencast – Automated Event Remediation using system center 2012 RC

March 30, 2012


Today we explore the other possibilities for sharing knowledge with the community. So I proudly present : our first screencast!

Subject : Automated Event Remediation using System Center 2012 RC Solution.

A compliancy breach is captured by SCOM , the alert creates an incident in the Service manager CMDB and this triggers an automated remediation workflow executed by Orchestrator.

Enjoy the weekend.

Link :