Error in Discovery wizard in SCOM 2007
Error in Discovery wizard in SCOM 2007 Error: "There were no discovered objects that met your criteria, or the account you specified does not have administrator rights on the computer you are trying to discover. Verify the computer your are trying to discover is listed in active directory, and that the administrator account you have specified on the previous page is a domain account thats in a local administrator group on the computers you are trying to discover." Actually the account i used is a domain admin and already added this id as a local admin too. still the same issue. kindly help me on this issue.
March 15th, 2011 11:58am

Hi Make sure that the computer hasn't already been discovered and is being monitored. If the server already has an agent installed from that management group then it won't be returned by the discovery wizard. Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
March 15th, 2011 12:29pm

If Graham's answer doesn't work, check here : http://thoughtsonopsmgr.blogspot.com/2009/01/scom-discovery-wizard-doesnt-work.html Christopher Keyaert - My OpsMgr/SCOM blog : http://www.vnext.be
March 15th, 2011 12:39pm

Hi Christopher, I checked as per advice, while i am changing dedicated AD account id the following error message appears. Kindly help me. Note: In the "permission" field the required AD account details mentioned as "User".Whehter it make difference. please help me. **************************************************************************************************************************** TITLE: Microsoft SQL Server Management Studio ------------------------------ Set owner failed for Database 'OperationsManager'. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Set+owner+Database&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: An exception occurred in SMO. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&LinkId=20476 ------------------------------ The proposed new database owner GLOBAL\OMAction is mapped as user GLOBAL\OMAction in this database. Parameter name: GLOBAL\OMAction ------------------------------ BUTTONS: OK ------------------------------ ****************************************************************************************************************************
Free Windows Admin Tool Kit Click here and download it now
March 15th, 2011 4:32pm

So you confirms that your SQL Broker is disabled ?Christopher Keyaert - My OpsMgr/SCOM blog : http://www.vnext.be
March 15th, 2011 11:00pm

Hi, Based on my research, I would like to suggest the following: 1. Please try clearing the HealthService queue on the RMS: 1) Stop System Center Management service. 2) Go to C:\Program Files\System Center Operations Manger 2007\, and rename the “Health Service State” folder. 3) Restart System Center Management service. 2. Check the firewall settings and ensure the required ports are not blocked: 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 Using a Firewall with Operations Manager 2007 http://technet.microsoft.com/en-us/library/cc540431.aspx Meanwhile, I would like to share the following with you for your reference: 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 If the issue persists, please check the Event Log on the server; if there are any related errors, please also let us know the details. Hope this helps. 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.
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 12:13pm

No, SQL broker is enabled, but the concern account is mentioned as user under "permission" tab. Is there any way to remove that id from user.
March 16th, 2011 1:01pm

Hi, Please also try the methods in the following posts: 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 OpsMgr R2 discovery issue http://thoughtsonopsmgr.blogspot.com/2009/09/opsmgr-r2-discovery-issue.html Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Hope this helps. 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
Free Windows Admin Tool Kit Click here and download it now
March 22nd, 2011 1:25pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics