Earlier chapters have provided relevant fundamentals in operations management, elaborating on ways to join key Microsoft technologies to form a solution. We've introduced many new terminologies and concepts along the way. Building on that in this chapter, we look further into components of the various consoles that Microsoft Operations Manager has to offer.
The configuration and administration of MOM 2005 is accomplished by the use of four consoles and in the management and tuning of alerts. In this chapter, we cover the following topics:
While there may be slight overlap, it's important to understand the differences in order to prescribe the correct formula. No doubt as a MOM Administrator, you'll need to be very familiar with all of them.
MOM 2005 introduced two consoles, Administrator and Operator, to handle most of the day-to-day functions either from an administrative perspective or an operator-centric perspective. For that reason, in this chapter, we spend a great deal of time on these two consoles. The operator is considered the customer of MOM and has the ability to view alerts, events, graphs, or performance data. The operator can also use MOM as a rudimentary ticketing system to assign classifications to alerts as they come in to show their current state such as resolved, acknowledged, or escalated to an SME. MOM users are a diverse group, ranging from the true operator (reacting to alerts) to the manager who simply uses the Reporting Console to view at-a-glance summaries of critical infrastructure.
Depending on your organization, the operator may never have to see the inside of an Administrator Console, change an event rule, or deploy an agent. This is most likely not the case, however. In fact, most MOM Administrators probably function as both the administrator and the operator. (After all, you are using MOM to monitor MOM, right?)