Many of the servers we monitor have services set to Automatic, but that is only because at server startup they launch, do their job, then stop. This normal behavior.

However, GotoManage consistently bugs me that some Windows Automatic Services are not running – I know already!!! :P

It would be nice to implement some sort of global filter. Once we get an alert that “Service XYZABC is not running” and it isn’t supposed to be, we can adjust the Windows Automatic Services alert adding a filter to stop alerting on exactly “XYZABC” from here on in — be nice to have it cover all companies too. Once I’ve discovered it on ClientA, I don’t want to have to go through B, C, D, …Z and configure them too.

I DO want to know when the other services are not running; this alert is pretty important, but it hounds me every 4hrs for nothing!

(repost — I replied in another forum, but this is probably a more appropriate forum)

In desparation (and no response) I figured out my own script. I am very early in testing, but this appears to do it:

select DisplayName, StartMode, Started, Name
from /network/device/WMI/win32_service
where StartMode='Auto'
AND Started=''
AND Name!='TBS'

..continue to add AND Name!=‘xxxxx’ for each service you wish to not scan for.

Now I have to sort out just how to ensure it only applies to class=servers. I don’t really want to know about workstations :)

I think I have it:

select SystemName, DisplayName, StartMode, Started, Name
from /network/device/WMI/win32_service
where nvl(../../system/class,../../system/computedclass)='server'
AND StartMode='Auto'
AND Started=''
AND DisplayName!='TPM Base Services'
AND DisplayName!='Microsoft .NET Framework NGEN v4.0.30319_X64'
AND DisplayName!='Microsoft .NET Framework NGEN v4.0.30319_X86'
AND DisplayName!='Software Protection'

This query looks at all servers, whether computed or manually set for all automatic services that are NOT running, but not the subset below. Might be able to nvl() the list below, but for now it suits the purpose.

Agreed this is needed.