none
Computer Discovery is in progress lasts forever

    问题

  • I have installed SCE 2010 on Windows Server 2008 R2 SP1 with remote SQL Server 2008 instance on the other server dedicated to SCE for it's databases and reporting. After installation I have performed initial configuration, everything went ok but now I have an issue with Computer Discovery. I have choosen Automatic computer discovery and Use selected Management Server Action Account but the status Discovery is in progress stays forever.

    I have checked on remote SQL instance and SQL Broker Service is enabled, also Management Account is a member of Domain Admins group. During initial configuration of SCE 2010 I have choosen creation of Domain-level group policy and Windows Firewall exceptions.

    What can I do to successfully perform Computer Discovery? Thanks in advance!



    • 已编辑 BoxiKG 2012年5月3日 12:02
    2012年5月3日 11:56

全部回复


  • Hi,

    Firstly, on the management server, please try the following and see how it works:

    1. Clear the HealthService queue:

    1) Stop System Center Management service.
    2) Go to C:\Program Files\System Center Essentials\, and rename the “Health Service State” folder.
    3) Restart System Center Management service.

    2. Restart the following services:

    System Center Management service
    System Center Management Configuration service
    System Center Data Access service

    Regarding the issue, please also check it referring to the following posts:

    Discovery Wizard is running for ever
    http://thoughtsonopsmgr.blogspot.com/2010/08/discovery-wizard-is-running-for-ever.html

    Agent discovery and push troubleshooting in OpsMgr 2007
    http://blogs.technet.com/b/kevinholman/archive/2007/12/12/agent-discovery-and-push-troubleshooting-in-opsmgr-2007.aspx

    Hope this helps.

    Thanks.


    Nicholas Li

    TechNet Community Support

    2012年5月4日 7:50
    版主
  • I have done both (Clear the HealthService queue and restart the following services) but Discovery is in progress again lasts and lasts. This morning I received an error that Discovery failed after yesterday's discovery. I am stuck completely and confused because when in March I have tried scenario when SCE and SQL are on the same PC (SQL Express 2008) I managed to discover PC's in domain within a few seconds. Now with remote SQL discovery fails every time.

    SCE 2010 installation, essentials reporting on remote SQL, initial configuration of SCE, . . . , everything went OK without any warnings or errors.



    • 已编辑 BoxiKG 2012年5月4日 8:51
    2012年5月4日 8:44
  • When I have choosen Advanced discovery and Use selected Management Server Action Account I managed to discover some computers whose names I had to manually type when searching AD, but this is not what I want, I want to discover all computers in my domain by using Automatic computer discovery and deploy agents to the ones which I select from Discovery Results.


    2012年5月4日 11:54
  • Sometimes even Advanced discovery does not work, even after choosing only one pc in AD. Something tells me as if I have some network issues.
    2012年5月9日 10:37
  • At last discovery of computers in domain has finished successfully, but it took almost an hour.

    Computer verification summary event.

    Verification successes - 444

    Verification failures - 413

    Verification time elapsed - 3422 seconds

    Obviously network is an issue.

    2012年5月10日 13:54
  • Hi,

    Thank you for your updates.

    Please also check the requirements of the Computer Discovery referring to the following articles:

    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

    Meanwhile, about the related firewall settings, I would like to share the following with you:

    Using a Firewall with Operations Manager 2007
    http://technet.microsoft.com/en-us/library/cc540431.aspx

    Thanks.


    Nicholas Li

    TechNet Community Support

    2012年5月11日 3:15
    版主
  • We upgraded our network devices and implemented vlans last month, network admins told me that all ports are open inside lan - further restrictions will be implemented in forthcoming weeks. If some ports had been blocked I would not have performed successfull computer discovery.

    Based upon verification time of almost an hour I strongly believe that we have some network issue. Also almost every warning and error in Operations Manager section of Event Viewer on SCE server mentions timeout. Do you agree with me?


    • 已编辑 BoxiKG 2012年5月11日 8:02
    2012年5月11日 8:01

  • Hi,

    At this time, please also check the following methods:

    OpsMgr 2007: Discovery Wizard never ends and no computers are discovered
    http://blogs.technet.com/b/operationsmgr/archive/2009/01/14/opsmgr-2007-discovery-wizard-never-ends-and-no-computers-are-discovered.aspx

    KB938994 - The discovery process does not find computers that are present in your domain in Operations Manager 2007
    http://blogs.technet.com/b/cliveeastwood/archive/2007/10/26/kb938994-the-discovery-process-does-not-find-computers-that-are-present-in-your-domain-in-operations-manager-2007.aspx

    Hope this helps.


    Nicholas Li

    TechNet Community Support

    2012年5月15日 5:30
    版主
  • I started automatic discovery yesterday and that time it failed. I re-run automatic discovery an hour ago and it was successfull. In Operations Manager log I have noticed that when discovery was unsuccessfull computer verification took more than an hour, when it was successfull it took around 55 minutes. According to previous unsuccessfull and successfull automatic discovery attempts it looks like SCE 2010 has threshold of an hour for discovery - when it is reached SCE 2010 reports an error that discovery failed. 

    Honestly 55 minutes or so is too much for discovery, it should take a few minutes in worst case. I can uninstall reporting from SQL, uninstall agents and uninstall SCE 2010 itself and install all on one server with local SQL Server Express 2008 but I would not do that unless I have to.

    If I had had some issues with rights, permissions, ports . . . I would not have been able to perform automatic discovery at all and I managed to do that twice but it took almost an hour at both occasions. For me NETWORK is an issue. 

    2012年5月15日 9:58
  • BoxiKG,

    quick question, if everything was working fine with a local install, why are you now using a different environment?

    in this article you can follow a checklist that should be able to help. I know it is for opsmgr 2007 but it should be the same procedure. Please let me know if this helps

    link > http://blogs.technet.com/b/momteam/archive/2006/10/24/having-trouble-discovering-computers-using-the-opsmgr-2007-discovery-wizard.aspx

    Thanks

    Jose

    2012年5月18日 0:04