This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 63%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGC%3C/text%3E%3C/svg%3E)
HI, I would like to pass the following:
1) Alert Name
2) Server Name
3) Ticket # which is stored in a custom field
To my SCOM Recovery so it can perform an autoremediation. How can I obtain these values?
Thank you
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 31%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
That's not possible because the recovery is triggered at the same time as the alert is triggered, not after it; so the alert doesn't exist yet when the recovery starts and therefore it can't access the alert properties, at least not in the form of a SCOM workflow variable.
One workaround would be to use a Get-SCOMAlert cmdlet in the recovery with some mechanism to make sure it gets the details of the proper alert, but that would make it much heavier.
hi CyzAz,
thank for your replying.
that explains it why I was not able to obtain the details from the recovery :(
Oh that would be extremely difficult to obtain the current alert of the alert which we are working on :(
As well, accoring to what you have mentioned, "the recovery is triggered at the same time as the alert is triggered, not after it" Then Get-SCOMalert won't be able to obtain anything as well
.
I am waiting for further classifications.
Thanks
Well, Get-SCOMAlert could run in some kind of loop until the alert is created. But that's definitely not a great solution...
I agree its not a great solution. My only way around this , would be to use SCORCH?
You mean a SCORCH runbook triggered by the SCOM Alert?
That would work indeed, but I'm not a huge fan of SCORCH... I would rather use a SCOM command-type notification channel : https://adatum.no/operationsmanager/using-webhook-in-scom-subscription-poc (start reading at "SCOM Command Channel and subscription")
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 66%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Hi,
Agree with the expert CyrAz's solution, as well as the great article provided. If possible, we may use -ExecutionPolicy Bypass as the parameter to avoid any prompts. If CryAz's reponse answered the question, please accept answer, so that other people that are facing the same situation may benifit from this thread.
Alex
If the response is helpful, please click "Accept Answer" and upvote it.
Hi,
How's everything going? Have we figured out this problem with the command channel suggested by CryAz? Or is there any other assistance that we can provide?
Regards,
Alex
If the response is helpful, please click "Accept Answer" and upvote it.
Hi,
No, I have not figured out the solution using the command channel yet.
thank you for asking and your help
regards George