Some alerts in SCOM are considered incidents, in ITIL terminology, and should be tracked in a\u00a0ticketing system. The easiest way to get a SCOM alert into appeared to be email. I did not want all alerts becoming tickets, just the ones I decided required tracking.<\/p>\n
On a cursory search it seemed easy enough run a powershell script from the SCOM console to send an email. However, any console task required that the powershell script be located on all of our servers that run the console. I wanted to be able to manage the script centrally. In my search for how to accomplish sending emails from scom, I came across Tao Yang’s script<\/a>. I ended up modifying his script in order to fit my needs.<\/p>\n Tao’s script was designed to be a replacement for SCOM email notifications. That was not how I wanted to implement it.<\/p>\n The first changes were to the parameters<\/p>\n The changes allowed parameters to be passed is as positional parameters. The $ScriptLocation parameter was added because Tao’s script used $myInvocation.MyCommand.Path to determine the location of the script. With the powershell command invoke-command this does not work. Therefore, the location of the script needs to be passed in as a parameter.<\/p>\n I also made modifications to deal with $myInvocation.MyCommand.Path. I replaced $MyInvocation with $PSScriptRoot, which is a powershell v3+ feature. I don’t plan on using $PSScriptRoot, but I left it in case I ended up using it.<\/p>\n In the authoring pain I created an “alert command line” console task. The application I call is “%SystemRoot%\\system32\\WindowsPowerShell\\v1.0\\powershell.exe” and the Parameters<\/p>\n Where you see “servername” insert your SCOM servername. The recipients email and name will also need to be defined.<\/p>\n\nparam(\n [Parameter(Mandatory=$True,Position=1)]\n [string]$alertID,\n [Parameter(Mandatory=$True,Position=2)]\n [string]$WebConsoleLink,\n [Parameter(Mandatory=$True,Position=3)]\n [string[]]$Recipients,\n [Parameter(Mandatory=$False,Position=4)]\n [string]$ScriptLocation\n )\n<\/pre>\n
\n#$MyInvocation has been superceeded in PS v3.\n#$thisScript = $myInvocation.MyCommand.Path\n\n#PSScriptRoot does not work when executed through invoke-command. If the $ScriptLocation is passed through as a variable we will not derive the\n# the location from $PSScriptRoot\nif (!($ScriptLocation)){\n$thisScript = $PSScriptRoot\n}\nelseif ($ScriptLocation){\n$thisScript = $ScriptLocation\n}\n\n$scriptRoot = Split-Path(Resolve-Path $thisScript)\n$errorLogFile = Join-Path $scriptRoot "error.log"\n<\/pre>\n\n\n-command Invoke-Command -ArgumentList "$ID$","http:\/\/servername\/WebConsoleUrl$?DisplayMode=Pivot''&''AlertID=$ID$","\\\\servername\\c$\\Scripts\\SCOMEnhancedEmailNotification.ps1",@('recipient;recipient@yourcompany.com') -ComputerName servername\u00a0 \u00a0-FilePath "\\\\servername\\c$\\Scripts\\SCOMEnhancedEmailNotification.ps1"\n\n<\/pre>\n