You've heard it before, but just in case...
This blog has been moved to http://blogs.technet.com/gerod_serafin/default.aspx. The old link should still work as well as the RSS feeds. My reasons for switching are:
Now for the update:
Better information facilitates rapid failure detection, reduces time to resolution, and reduces management cost and complexity. I've been asked a lot recently which monitoring tools to use with Exchange 2003. It seems that everyone wants me to tell them the alternatives to MOM 2005. If you want to do the research yourself, I ask you to look for the following things in the product:
If your product doesn't do all of the above, then I guess technically you still have an alternative. Unless you can do all of the above, then you are not really aware of what is going on in your environment. This is not your old Exchange server any more. Your Exchange environment does a lot more than it used to do. If you asked me for a way to keeping your valuable thing (i.e. sports car, house, phone system) in good shape, would you want me to give you an alternative to the best solution? Does monitoring your Exchange 2003 environment that keeps your business running any less important? Do you really want the solution to be a product that is actually a hodge-podge of other products bought from multiple companies by a hardware vendor and then forced together and re-branded as a new and improved suite? (Oh, and you will still have to configure it.) If so, good luck with your alternative(s). Just don't ask me how to configure it to do what MOM 2005 does, because it can't.
MOM 2005 does 1-10 and more, and a majority of this is straight out of the box. I used to say: "I don't care if you have MOM 2005 or not, but just get something to monitor your Exchange 2003 deployment." Now I realize that statement is false. I do care.
RePost : http://www.yeyan.cn/Programming/ExchangeServer2003MonitoringSolution.aspx