locked
Discovery AD System RRS feed

  • Question

  • I have Installed SCCM 2012, Enabled All the discovery methods, created boundary but still AD systems are not appeairng in device collections. Can any one please tell me if I missed something?

    Thanks

    Raofu

    Tuesday, September 11, 2012 3:31 PM

Answers

  • Looks like the server is experiencing catastrophic failure talking to the DC ... i would assume the problem is there, check the DC's event logs.

    • Proposed as answer by Garth JonesMVP Sunday, February 1, 2015 9:13 PM
    • Marked as answer by Garth JonesMVP Saturday, October 17, 2015 3:38 PM
    Wednesday, September 12, 2012 9:37 PM

All replies

  • Did you config in Ad System discovery a domain to search in and manually run the detection? Also did you create the systems management container and give configmgr server access.

    Justin | http://patchmypc.net | Please remember to mark as helpful/answer if this helped you


    Tuesday, September 11, 2012 3:56 PM
  • How did you configure your discoveries?

    Have you reviewed the discovery log files (adsysdis.log for AD System Discovery)?


    Jason | http://blog.configmgrftw.com

    Tuesday, September 11, 2012 6:25 PM
  • Jason and Justin, thanks for the reply.

    discovery methods are enabled from sccm console an scheduled. also right clicking on system discovery method i start as soon as posible.

    from the log i found error 'no AD container is selected', then in discovery methods i have shown AD computer OU. now AD clients are in sccm device collection. but still there is some error on adsysdis.log file. i have attached it here. this is might now causing client push installation error. i have also attached it here.

    Wednesday, September 12, 2012 7:20 AM
  • ccm.log has nothing to do with discovery so that can be safely ignored in that case. Please don't use screenshots when pasting logfiles snippets. They are not searchable and we don't see the entire error message because the Log Text column is too small.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, September 12, 2012 7:53 AM
  • Looks like the server is experiencing catastrophic failure talking to the DC ... i would assume the problem is there, check the DC's event logs.

    • Proposed as answer by Garth JonesMVP Sunday, February 1, 2015 9:13 PM
    • Marked as answer by Garth JonesMVP Saturday, October 17, 2015 3:38 PM
    Wednesday, September 12, 2012 9:37 PM