Just One More Project Every Day is a New Project

2Feb/120

SCOM 2007 R2: The Adventure

So I have been tasked at work to clean up our scom environment. I have been spending a lot of time trying to organize and understand how scom works. Wikipedia Defines scom as:

System Center Operations Manager is a cross-platform data center management system for operating systems and hypervisors. It uses a single interface that shows state, health and performance information of computer systems. It also provides alerts generated according to some availability, performance, configuration or security situation being identified. It works with Microsoft Windows Server and Unix-based hosts.

In short its a health management tool. It sends out email alerts based on what you define, to notify you of issues, or pending issues within your environment. It will allow you to migrate from a reactionary department to a proactive department.

This tool when configured right and make your job much easier, but when not configured right... well you end up with what i have.

Currently i receive between 200 and 500 email's a day on "critical" issues within my environment.
"Critical" Issues Like:
Alert: Computer Browser Service Stopped Resolution state: New
Alert: Miscellaneous SAM Errors Resolution state: New
Alert: DC is both a Global Catalog and the Infrastructure Update master Resolution

Now don't get me wrong, i do get emails about actual critical issues within my environment, but when i get emails on issues like the above, it makes it near impossible for me to react within a timely manner.

So. Im going to start posting tips and tricks i have found for managing scom on here. Hopefully some of this stuff will help someone down the line, or even myself when I need to come back and reference something.

Hope you enjoy the Adventure.