Hi, New SCOM build, and the Discovery Wizard runs forever and cannot discovery any servers. Servers are discovered fine using the Advanced Discovery (where server names are inputted manually). SQl broker is enabled. Have cleared the Health Service Store, rebooted RMS etc. Any ideas what to try next? Nothing is obvious in the event logs. Thx, John Bradshaw

Hi John, The three common causes I've seen regarding this issue are: Make sure the SQL Broker service is enabled (which you've confirmed) Confirm the OpsMgr SPN's have been configured correctly in Active Directory (which is detailed in the OpsMgr Install Guide) Ensure the firewall on each server where you want to install the agent isn't blocking the ports required for OpsMgr AD Discovery (I don't know them off the top of my head, I suggest checking the OpsMgr Install Guide) Good luck! Cheers, Brian

Thx Brian, I have asked the AD guys to ahve a look. Cheers, JB

Additionally, I would like to share the following with you for your reference: How does Computer Discovery Work in OpsMgr 2007? http://blogs.technet.com/b/momteam/archive/2007/12/10/how-does-computer-discovery-work-in-opsmgr-2007.aspx Having trouble discovering computers using the OpsMgr 2007 Discovery Wizard? http://blogs.technet.com/b/momteam/archive/2006/10/24/having-trouble-discovering-computers-using-the-opsmgr-2007-discovery-wizard.aspx Meanwhile, please check the Event Log on the server; if there are any related errors, please also let us know the details. Thanks. Nicholas Li - MSFT Please 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.

Nice diagram of how discovery works at the first link. thx Nicholas JB

Hi Brian, U were correct, points 2 and 3 were cactus for this new server. Anyway, I had the server relocated and placed back the VLAN etc details from the old server which I know worked well. Suddenly the server sprang to life. BUT.....there's always a but......I think SQL is now just about stuffed. Too many changes for the poor thing to cope with. "Cannot insert discovery into databse and so on...blah, blah" Question: Can I un-install SQL2008 and OpsMgrR2 from Windows 2008R2 and be "relatively" clean? i.e. If I do the un-install of both and then re-install will the re-install be pretty clean or does Windows somehow keep settings from the old SQL install?? (Sorry to be a pain about this, but getting a Windows box built here is a rather drawn out process) thx for your help, John Bradshaw

Hi John Yes, you can do that. Don't forget to clean out the registry with the SCOM entries (HKLM\Software\Microsoft\Microsoft Operations Manager. Be sure to uninstall in reverse order: SCOM first, than SQL. Also a reboot after the removal of SCOM will work here since the OpsMgr DB won't be locked anymore. Also do not forget to remove the related folders of SQL and SCOM from that server. Understanding your answers, the SPNs are in place now? So when installing SCOM R2 again, be sure to use the same accounts and name of the SCOM Management Group. You should be fine then. Hope this helps. Sorry for the late answer but the last weeks of this year are really crazy. Many things going on. Cheers, Marnix And: A marry X-mas and a Happy New Year!Best regards, Marnix Wolf (Thoughts on OpsMgr)

Hi guys, Sorry to have to re-open this, but just back from a short break. I have built another SCOM R2 server, just with the basics...No CU3 yet, etc. Only have vanilla 2008R2, SQL2008R2 and SCOMR2. Set up the databases with the DBcreate wizard and up to that point all is OK. Logs show no pertinent errors. I get the same error just on 3 boxes (I have 500+ to monitor) which is the following, but I think that might be a red herring: The OpsMgr Connector negotiated the use of mutual authentication with x.x.x.x:17386, but Active Directory is not available and no certificate is installed. A connection cannot be established. EventID 21010 At the end of the failed discovery it says "There were no computers discovered that met your criteria. Pls verfify the following conditions: - The account you specified has Administrator privileges on the computers you are trying to discover The computers you specified are listed in Active Directory The computers you specified have the necessary ports open A previous R2 SCOM build on Server 2003 was able to Autodiscover windows servers. This 2008R2 server cannot. So, I am guessing that it is an AD/Group Policy issue that may be occurring still??? This install was done under a Domain Admin account for SQL and OpsMgr. Browsing manually, the discovery works fine. What should I try next?? (I note that Active Directory Domain Services is stopped (as well as Intersite Messaging and Kerberos Key Distribution Center) (Pls note: I still have another current install (but with the same symptoms) running in the same AD space. Thx, John Bradshaw

Hi guys, Sorry to have to re-open this, but just back from a short break. I have built another SCOM R2 server, just with the basics...No CU3 yet, etc. Only have vanilla 2008R2, SQL2008R2 and SCOMR2. Set up the databases with the DBcreate wizard and up to that point all is OK. Logs show no pertinent errors. I get the same error just on 3 boxes (I have 500+ to monitor) which is the following, but I think that might be a red herring: The OpsMgr Connector negotiated the use of mutual authentication with x.x.x.x:17386, but Active Directory is not available and no certificate is installed. A connection cannot be established. EventID 21010 At the end of the failed discovery it says "There were no computers discovered that met your criteria. Pls verfify the following conditions: - The account you specified has Administrator privileges on the computers you are trying to discover The computers you specified are listed in Active Directory The computers you specified have teh necessary ports open A previous R2 SCOM build on Server 2003 was able to Autodiscover windows servers. This 2008R2 server cannot. So, I am guessing that it is an AD/Group Policy issue that may be occurring still??? This install was done under a Domain Admin account for SQL and OpsMgr. Browsing manually, the discovery works fine. What should I try next?? (Pls note: I still have a current install (but with the same symptoms) running in the same AD space. Thx, John Bradshaw

Hi guys, Sorry to have to re-open this, but just back from a short break. I have built another SCOM R2 server, just with the basics...No CU3 yet, etc. Only have vanilla 2008R2, SQL2008R2 and SCOMR2. Set up the databases with the DBcreate wizard and up to that point all is OK. Logs show no pertinent errors. I get the same error just on 3 boxes (I have 500+ to monitor) which is the following, but I think that might be a red herring: The OpsMgr Connector negotiated the use of mutual authentication with x.x.x.x:17386, but Active Directory is not available and no certificate is installed. A connection cannot be established. EventID 21010 A previous R2 SCOM build on Server 2003 was able to Autodiscover windows servers. This 2008R2 server cannot. So, I am guessing that it is an AD/Group Policy issue that may be occurring still??? This install was done under a Domain Admin account for SQL and OpsMgr. Browsing manually, the discovery works fine. What should I try next?? (Pls note: I still have a current install (but with the same symptoms) running in the same AD space. Thx, John Bradshaw

Hi guys, It turned out to be an SPN problem Thx, JB