Hi All, Please help. We have MB1 and MB2 scc for Exchange. All DB on MB2 discovered and being monitored by SCOM while on MB1 DBs doesnt. No override made on these monitors. I notice on MB1 ESE to Mailbox Monitor is on Not Monitored state.  Thank you in Advance.

Hi, Check these: Before You Import the Exchange 2010 Management Pack http://technet.microsoft.com/en-us/library/ee758051(v=exchg.140).aspx OpsMgr 2007 R2 by Example: the Exchange 2010 MP http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/67924/Default.aspx Kevin Holman's blog: http://blogs.technet.com/b/kevinholman/archive/2011/04/07/exchange-2010-sp1-management-pack-ships-version-14-02-0071-0.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Dktoa, this is Exchange 2007 he's talking about. Shianx, first can you tell us your patch level and version of your SCOM environment. Also the version of the Exchange 2007 MP (there is one for 2007 SP1 and one for R2). Finally, when you look at the ops log on the server that isn't rolling health up or discovering things, are there any odd errors or warnings especially compared to the one that is "healthy"? If you see nothing, bounce the health service on that 2007 box, and watch the log and wait until all discoveries are done, global snapshots are done, etc. Wait until the agent settles back down and maybe logs that event that tells you it's just logging for the sake of logging. Go back to this view (which I don't really like, because this looks like you are looking at the "windows computer" object via the health explorer, but that's fine, go back and check the state. Go to the Exchange 2007 state views and compare it to the healthy box. If there is no change you may want to clear the cache on the unhealthy server and let it re-download all the mps and config. If that doesn't work, re-install the agent. Of course before doing any of this, ensure you have AV exclusions on your SCOM folder/files on the server hosting the agent. Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/

Hi Guys, Thank you for the response. Below are the version of MP imported. These are SCC Clusters MBC1 and MBC2 (sorry for typo error) and they are both healthy ..How will i rediscover MBC1 since these are agentless managed. Thank you so much.. 

That looks like the latest version, you didn't tell me what version of SCOM and patch level you are at. All your exchange servers should be running the agent as local admin (system account) and AGENT proxy needs to be enabled on all of your Exchange servers, no matter what version. Agent proxy enabled on a cluster will allow the cluster (agentless) name to be discovered and monitoring applied. I take it you have agent proxy enabled on all of these servers yes?Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/

Hi Blake, We have SCOM 2007 R2 running. Yes you are correct, i have agent proxy enabled on all Exchange Servers. and All the Exchange servers' agent running as System Account. Is this problem on discovery right? Is it okay to change the proxy agent on MBC1? and different from MBC2?