locked
Active Directory System Discovery - Kind of working RRS feed

  • Question

  • We are seeing machines get discovered, but not all are coming into the console.

    Here is an example of a machine that is getting discovered from ADSYSDIS.log but never showing up in the console.

    Thoughts?  Other things I could check? I am thinking we may have a DNS issue in our environment, but AD System Discovery only uses AD to find a machine correct... it doesn't find and then ping before it pulls it in to my knowledge.

    Any help is appreciated.

    Wednesday, March 9, 2016 9:01 PM

Answers

  • Correct, system discovery does not ping a system; however, it does validate that the name can be resolved via DNS and also does not create DDRs for disabled objects.

    The screenshot you show above is for a DDR being successfully created. Once a DDR is created, I've never seen it fail to create a resource.

    Are you sure a resource for the object does not already exist?

    How exactly are you determining that a resource was not created?

    You can review ddm.log to see details of the site processing the DDR.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by cfreeman21 Thursday, March 10, 2016 3:53 PM
    Thursday, March 10, 2016 1:34 AM

All replies

  • Correct, system discovery does not ping a system; however, it does validate that the name can be resolved via DNS and also does not create DDRs for disabled objects.

    The screenshot you show above is for a DDR being successfully created. Once a DDR is created, I've never seen it fail to create a resource.

    Are you sure a resource for the object does not already exist?

    How exactly are you determining that a resource was not created?

    You can review ddm.log to see details of the site processing the DDR.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by cfreeman21 Thursday, March 10, 2016 3:53 PM
    Thursday, March 10, 2016 1:34 AM
  • Dear Sir,

    Concur with Jason.

    You need to check in ddm.log for ddr processing. If error occurred during processing, or too many data is coming, the .ddr may get backlogged.

    Best regards

    Frank


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, March 10, 2016 2:52 AM
  • Okay so I checked the ddm.log and it only shows:

    Processing file adsjd3w1.DDR

    ==>Resident site of <JIN>. Discovery property <AD Site Name> matches (SITE A)

    Still not in console.

    Thursday, March 10, 2016 2:24 PM
  • What about my other questions"

    Are you sure a resource for the object does not already exist?

    How exactly are you determining that a resource was not created?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, March 10, 2016 2:29 PM
  • I have checked under devices in the console and also ran the MAC Address report and the machine is not in with MAC address... Another way to check?
    Thursday, March 10, 2016 2:33 PM
  • AD doesn't know anything about MAC addresses so that's not part of AD Discovery. You need to look for the system's name.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, March 10, 2016 2:56 PM
  • I agree on MAC address not being in AD Discovery was just trying to see if the machine was in a different way then just name in the console... I am going to try to Install the client manually on the machine and see if it comes in but that still does not fix my issue.  Other thoughts?
    Thursday, March 10, 2016 3:04 PM
  • That doesn't change anything or answer the question though. How exactly are you trying to locate the system in the console?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, March 10, 2016 3:18 PM
  • I think this is due to a machine being cloned therefor a duplicate Machine GUID does that make since?
    Thursday, March 10, 2016 3:41 PM
  • Cloning should not affect this to my knowledge; however, cloning is a terrible, terrible practice that has never ever been supported.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, March 10, 2016 3:49 PM
  • Agree we do not clone here, but sometimes our remote sites take shortcuts :-(  Thanks for your help.
    Thursday, March 10, 2016 3:52 PM
  • Curious, did you ever figure this out?  I've got about a 1 yr old SCCM installation currently at version 1602, and I've got an issue that sounds similar to yours, but may or may not be the same.

    My system is generating the DDRs ok and ingesting them but for some (~15%) of my workstations the DDRs never get added into the database.  I've got a support case open, though they're trying to tell me to re-image or manually deploy the client to affected machines, which doesn't really resolve the root issue :/

    I may start a new thread on it but wanted to at least check and see if you found a solution.

    Saturday, June 11, 2016 12:04 AM