SCOM 2016 Command based subscriptions not firing; help troubleshooting

ITMAN 0 Reputation points

I have a command based subscription which isn't firing at all. I know it's not firing because the batch file generates a log when it does. I've checked event viewer but cannot find the root cause. Any suggestions on how to debug/troubleshoot this? I've tried tracing in the past but honestly the trace files generated are not easy to read.

Microsoft System Center
Microsoft System Center
A suite of Microsoft systems management products that offer solutions for managing datacenter resources, private clouds, and client devices.
816 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. XinGuo-MSFT 13,856 Reputation points


    When System Center Operations Manager 2016 command-based subscriptions are not firing as expected, it can be frustrating, but there are several steps you can take to troubleshoot the issue. Command-based subscriptions in SCOM allow you to run custom scripts or commands in response to specific alerts. Here's a troubleshooting guide to help you identify and resolve the problem:

    Test the Command: Manually run the command or script specified in the subscription to ensure that it functions as expected. This will help you identify if the issue lies within the command itself.

    Check Security Context: Ensure that the account under which SCOM services are running has the necessary permissions to execute the command. Permissions to access the necessary resources (e.g., network shares, databases) should also be verified.