Hi
I have seen this in several SCOM 2012 R2 environments now and is wondering if any one else has too?
Monitoring of a Windows service in SCOM 2012 using a unit monitor, Windows Basic Service Monitor. The state change/alertingtakes from 2 up to 5 minutes to take place, while the automatic reset once the service is running again always happens en less than 1 minute. In OpsMgr 2007 R2 the state change to unhealthy always happens in less than 1 min. State changes for other monitors appears to work normally and alerts/events comes straight in. It must be a bug and I'm curious to hear from you what you see!
Thanks
Kind regs
Lars