Good day, This is not the first time that we have encountered this situation, whereby an aggregate rollup monitor is not properly respecting its Health Rollup Policy. Critical - Entity Health – C: (Entity) Critical - Availability – C: (Entity) Healthy - Logical Disk Availability – C: (Windows Server 2003 Logical Disk) Healthy - Logical Disk Free Space – C: (Windows Server 2003 Logical Disk) Not Monitored - Configuration – C: (Entity) Etc. All attempts to Reset Health on the ailing aggregate rollup monitor have thus far failed. Any ideas on what could be going on? Thanks, Larry

Yes an annoying bug in SCOM. Workaround: Put the disk (or computer) in maintenance for about 10 minutes (make sure it becomes "not monitored"). When it comes out of maintenance all is well again.Rob Korving http://jama00.wordpress.com/

As Rob says - this is a known issue. Maintenance mode usually does the trick. If it doesn't then try: - set an override (enable = false) on the lowest level aggregare monitor that is red (unhealthy). This would disable the roll up so it should go Not Monitored. - once the roll up state is "Not Monitored", remove the override View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Rob, Thanks for the workaround. I have submitted the issue as a bug on Microsoft Connect. For those of you that are affected, please vote on the issue at: https://connect.microsoft.com/OpsMgr/feedback/details/637162/misbehaving-aggregate-rollup-monitor Thanks, Larry

done. now if ms only listened to the feedback...Rob Korving http://jama00.wordpress.com/