locked
Exchange 2010 discovery RRS feed

  • Question

  • Hi, my scenario is as follows: OpsMgr 2007 R2 CU2 with Exchange MP 14.2.71.0. The Exchange servers are all 2010 SP1 with no rollup patches. The correlation engine is installed on the RMS. The Exchange servers all have the OpsMgr agent installed and agent proxying is enabled however they are not discovered by OpsMgr as Exchange servers. No Exchange info is present. Any help would be appreciated.

    Thanks

    Wednesday, July 20, 2011 8:12 AM

Answers

  • Hi Blake

    Hope all is well - For Exchange 2010, the discoveries for server roles are enabled by default (very different from Exchange 2007):

    http://technet.microsoft.com/en-us/library/ee758038(EXCHG.140).aspx

    "After you import the Exchange 2010 Management Pack, System Center Operations Manager 2007 runs a discovery process to locate the Exchange servers and other objects in your Exchange environment. Operations Manager 2007 must discover these Exchange servers and other objects to effectively monitor your Exchange environment. By default, System Center Operations Manager 2007 discovers all the Exchange servers and other objects in your environment. No additional configuration should be necessary in most customer environments."

    I have just installed on SCOM 2012 beta and my Mailbox, CAS servers and Hub transport servers have been discovered without any configuration changes. And if you look under authoring, management pack objects, object discoveries you'll see that the discoveries are enabled by default.

    I'd suggest looking in the Operations Manager event log on the RMS for events.

    Have fun

    Graham 


    New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    • Marked as answer by Yog Li Friday, August 5, 2011 8:53 AM
    Wednesday, July 20, 2011 7:29 PM

All replies

  • Do check the MP guide.  There are a number of discoveries that are disabled by default - including most of the server role discoveries.  This approach lets you incrementally add load to your system one exchange subsystem at a time.
    Microsoft Corporation
    • Proposed as answer by Yog Li Friday, August 5, 2011 8:49 AM
    Wednesday, July 20, 2011 5:57 PM
  • I did follow the MP guide but it states the following:

    Each discovery in the management pack is discovered by default. No additional configuration should be necessary in most customer environments.

    Wednesday, July 20, 2011 6:20 PM
  • Dan is correct, read the guide, because you will have to enable discoveries for seed classes and specific roles you are hosting.  In our environment I did not enable all discoveries because there are several E2K10 roles we are not hosting.  This cuts down on config churn.
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/
    Wednesday, July 20, 2011 6:21 PM
  • Hi

    The Exchange 2010 discoveries are enabled by default - it is the Exchange 2007 discoveries that were turned off. I quite liked the way it was done in 2007 but I guess I was in the minority!

    It does take some time for the discoveries to run through as it is a weighty management pack. But given that you posted 10 hours ago, if you still don't see any of the servers then take a look in the OperationsManager event log on the RMS and let us know what errors you see.

    This is a good run through of configuration:

    http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/monitoring-exchange-2010-opsmgr-2007-r2-part1.html

    Cheers

    Graham


    New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Wednesday, July 20, 2011 6:22 PM
  • That is correct, I was getting confused with E2K7.. I have every version of Exchange running so I'm a little loopy from time to time (surprised I don't have 5.5 running still!).

    How many E2K10 boxes do you have?  I know when we first installed this MP we had about seven, but it took a while for everything to be discovered..


    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/
    Wednesday, July 20, 2011 6:39 PM
  • Dunno guys.  Looking at the MP there are a dozen or so discoveries that are disabled by default and that have names that sound like server role names to me.
    Microsoft Corporation
    Wednesday, July 20, 2011 6:44 PM
  • The Exchange environment is small, only 4 servers, so I'm sure they should have been discovered by now. I'll recheck the discoveries. Thanks.
    Wednesday, July 20, 2011 6:55 PM
  • Hi Blake

    Hope all is well - For Exchange 2010, the discoveries for server roles are enabled by default (very different from Exchange 2007):

    http://technet.microsoft.com/en-us/library/ee758038(EXCHG.140).aspx

    "After you import the Exchange 2010 Management Pack, System Center Operations Manager 2007 runs a discovery process to locate the Exchange servers and other objects in your Exchange environment. Operations Manager 2007 must discover these Exchange servers and other objects to effectively monitor your Exchange environment. By default, System Center Operations Manager 2007 discovers all the Exchange servers and other objects in your environment. No additional configuration should be necessary in most customer environments."

    I have just installed on SCOM 2012 beta and my Mailbox, CAS servers and Hub transport servers have been discovered without any configuration changes. And if you look under authoring, management pack objects, object discoveries you'll see that the discoveries are enabled by default.

    I'd suggest looking in the Operations Manager event log on the RMS for events.

    Have fun

    Graham 


    New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    • Marked as answer by Yog Li Friday, August 5, 2011 8:53 AM
    Wednesday, July 20, 2011 7:29 PM
  • If that is the case, then the documentation needs updating, because it states nothing is required for discoveries to work.  I just looked at the discoveries in prod and they are all enabled by default.  Running the latest Exchange 2010 MP as well.
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/
    Wednesday, July 20, 2011 7:34 PM
  • Quick update: all the Exchange related discoveries are listed as enabled by default. The RMS event log is squeaky clean, and still no Exchange servers discovered. I found this review of the MP on Pinpoint:

    Pros
    Haven't gotten it running to know
    Cons
    Is not finding any servers
    Additional Comments
    Best guess is it is looking for too specific a version number and the servers on this particular network are running exchange 2010 sp1.

    Is it possible to identify the criteria the MP uses to confirm if a server is running Exchange?

    Thursday, July 21, 2011 6:40 AM
  • Hi

    I understand that you installed on the RMS but can you double check that the Microsoft Exchange Correlation Service actually running on the RMS?

    Also - check the Operations Manager event log on the Exchange servers for any discovery errors.

    A final place to check is in on the exchange servers --> \program files\system center operations manager 2007\health service state\Management Packs and check if the exchange management packs have downloaded.

    Cheers

    Graham


    New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Thursday, July 21, 2011 6:45 AM
  • Hi,

    I've checked the Correlation service, its there and running.

    The Exchange server OpsMgr event log is clean.

    There is a file called Microsoft.Exchange.2010.xxx.yyy.xml with a size of 10919KB in the Management Packs directory on the Exchange server.

    I can also confirm that all other technologies ie. OS, SQL etc are correctly discovered.

    I'm pulling what little hair I have left out :)

    Thanks for all the suggestions.

    Thursday, July 21, 2011 7:58 AM
  • If you bounce the correlation engine on the RMS, what event logs do you see for it in the application log?
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/
    Thursday, July 21, 2011 8:10 AM
  • Service stopped successfully

    Service starting

    MSExchangeMonitoringCorrelation successfully connected to Operations Manager Root Management Server

    Thursday, July 21, 2011 8:18 AM
  • Well that's a good sign.  When you look for that event source in the application log do you see any previous issues?
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/
    Thursday, July 21, 2011 8:31 AM
  • Also - make sure you have enabled agent proxy on the exchange serves (administration, device management, agent managed --> double click the server and go to the security tabe and enable agent proxy). One of my CAS servers wasn't discovered and changing this setting fixed the problem.

    Cheers

    Graham


    New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Thursday, July 21, 2011 11:18 AM
  • Hi Graham,

    I can confirm that agent proxy is enabled on all the Exchange servers.

    Thursday, July 21, 2011 11:21 AM
  • Running out of options ...

    1) Double check that agent action account is local system and that someone hasn't changed it to be a domain user account

    2) Perhaps change one of the discoveries to run every 5 minutes against one server (say mailbox discovery) so that we can concentrate on one discovery that we know will execute frequently (rather than every 4 hours).

    3) Bounce the System Center Management service on this mailbox server

    4) Are there any alerts in the OpsMgr console for this mailbox server? Is the computer state healthy? Is the agent state healthy (under monitoring, operations manager, agent) ?

    5) Is the Exchange Management Console installed on these servers?

    Not sure what else to check.

    Good Luck

    Graham 


    New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    • Edited by Graham Davies Thursday, July 21, 2011 12:01 PM added 5)
    Thursday, July 21, 2011 12:00 PM
  • Had the same issue.  The MP was installed 2 days ago with the agents.  No errors in the OpsMgr logs on RMS or Exchange boxes.  Agent generally working fine on Exchange boxes (got some disk latency alerts and discovery for IIS MP worked fine).  This thread definitely helped me but here is what exactly worked:

    1. Bounced Microsoft Exchange Correlation Service on RMS 

    2. Enable Agent Proxy on ALL Exchange Server agents in the SCOM Administration console

    3. Bounce the System Management Service on ALL Exchange Servers

    After doing the above and waiting 15-20 min. all Exchange servers showed up under Exchange 2010 MP views and Exchange Distributed App discovered correctly as well. 

    • Proposed as answer by Xerokool.V1 Wednesday, January 29, 2014 4:05 PM
    Thursday, September 8, 2011 11:25 PM