Having been on the TAP program for Exchange 2010 I have had some experience with the beta version of this management pack. MSFT released the Exchange 2010 management pack yesterday and you can get it here.
There are a few pre-requisites before installing this management pack. Basically they are hotfixes that need to be applied to either your SCOM 2007 SP1 or R2 environments. These are documented in the MP guide and information on how to obtain them are listed as well. Be sure you get these and apply them to your environment before installing this MP.
MSFT also has a list of recommended additional management packs that should be installed, but not necessary for all environments (I.E. Labs, etc).
One thing that you will notice that is different for this management pack is that it will install a service on one of your management servers. The RMS is recommended, but that decision is up to you. This new service is called the Correlation Engine (reminds me of what HP does with it’s EVA systems using something called WEBES).
So when you install this MP you will see two directories for data to be extracted in. After the install you simply import the MP (there are two mp files one for monitoring and one for reporting) and wait for discovery to be completed.
One thing to note, is that you must enable agent proxying on all Exchange 2010 agents in order for this MP to work (as well as have the service run as local system). It might be a good idea also to verify that those agents did receive the hotfixes necessary before importing the MP as well as proxy enabled (both of these things can easily be checked by creating state views to display this data).
In the guide there is a warning that if you have the Cluster Management pack installed, you will be told how to exclude Exchange 2010 clusters from this management pack. I looked through the guide and didn’t find those instructions. I contacted the MSFT party responsible for the MP and he said that note should have been removed prior to it releasing, so if you see this and get concerned, then don’t worry it wasn’t meant to be in the guide.
As always, read the guide carefully before installing this MP and ensure you understand how alerts bubble up, and how components are discovered. Overall the deployment was relatively simple and I am looking forward to seeing just how well this MP will manage our Exchange 2010 infrastructure.