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(150.4, 33%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBZ%3C/text%3E%3C/svg%3E)
Hi, I have noticed that every custom service monitor targeting custom SCOM group does not generate alert for stopped service at all. For instance, service present on particular server is currently stopped but no alert whatsoever:
Of course, server hosting ServerManagementGateway service is a member of Windows Admin Center Server SCOM group.
NOTE: custom service monitor targeting SCOM group containing all Domain Controllers (sending alerts if MDI sensor service is stopped) works fine - that group of course is automatically there with members automatically populated.
What can be done here to make custom service monitors work as they should?
HI Bojan,
please make sure you are using the SCOM Windows Service Monitoring template for that in order to avoid complications with the targeting:
Also ensure you are using the Name and not the DisplayNAme of the service.
Make sure agents and MS are healthy and try to clear the cache on those for troublshoting purposes.
I hope I could help you out with that*
Regards,
Stoyan
It works now but there is a problem, it seems like this template does not have an option to configure recovery task like Basic Service Monitor does:
I'd like to use simple PowerShell one-liner script to start service ...
I don't understand why Basic Service Monitor I set up for MDI Sensor Service targeting built-in SCOM group (containing all Domain Controllers) works, but this one does not (targeting custom SCOM group).
![](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(278.4, 17%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Afternoon, on the server, on the Recovery Tab of the service properties, do you have it configured to Restart the Service after the first and second failures?
Also, what is the configuration of this Custom SCOM Group? Are the server explicit or dynamic? Is a group nested?
I have found recovery task under monitor properties (not in Windows Service menu) - however it does not work, script was not executed once service was stopped. So now I have monitor successfully targeting dynamic SCOM group but recovery task does not work.
What is the script you are using?
On the Recovery Tab, check the box for: Enable actions for stops with errors.
"If your services are stopping because of an error, that is logged by windows then yes, you need to tick 'Enable Actions For Stops With Errors', otherwise it will not work.
If you do not have this ticked, then it will only restart services that have stopped for legitimate or unknown reasons."
PS script is a trivial one-liner:
Start-Service -Name Spooler
However, this works (Run Command recovery task type) but honestly, I always prefer PS scripts over command line tools:
Latest update: if I use Run a PowerShell script (Community) recovery task type instead of Run Script, recovery task works fine.
"Problem" now is that I get only one SCOM alert and closed one which is a bit awkward (service is automatically started by recovery task so "not enough time" to get alert with New resolution state I guess):