Hi,
It sounds like you’ve set up everything correctly, but there might be a few reasons why your event isn’t triggering an alert in SCOM. Here are some steps you can try to troubleshoot the issue:
- Event Log Service: Restart the Event Log service on the server. Sometimes, the service might not be picking up the new events correctly.
- Monitor Configuration: Double-check the configuration of your Unit Monitor. Ensure that the event ID, source, and log name match exactly what is being generated by
eventcreate
. - SCOM Agent: Make sure the SCOM agent is running on the server where the event is being generated. If the agent is not running or has issues, it won’t be able to report the event back to the SCOM management server.
- SCOM Cache: Clear the cache on the SCOM management server. Sometimes, stale cache can cause issues with alert generation. You can do this by running a PowerShell script to clear the SCOM cache.
- Permissions: Ensure that the account running the SCOM agent has the necessary permissions to read the event logs and report back to the SCOM management server.
- Health Service State: Check the health service state on the SCOM management server. If there are any issues with the health service, it might not be processing the events correctly.
If you’ve tried these steps and the issue persists, you might want to recreate the monitor or create a rule instead of a monitor. Rules can be simpler to configure and might help you identify if the issue is with the monitor configuration.
Let me know if you need more detailed steps on any of these points!