SCCM Discovery not bringing distinguished name.

Question

Hello wonderful people on the internet.
Around two weeks from now, we started receiving complaints from IT operation saying that computers recently imaged are not appearing in the collections.
These collections query the AD OU, and it worked fine until now.
Upon investigation, I noticed that the computer on database didn't have the AD attributes, like Distinguished Name, AD Site, OS Name and version, etc.
Since these were imaged using PXE, with the client being installed in one of the Task Sequence's steps, the computer got in with Heartbeat Discovery.
The "Agent Name" property has only "MP_ClientRegistration".
My next target was AD System Discovery.
This discovery method was already enabled in our environment for a while, and the OU the computer is in, is included into the discovery.
It runs every 4 days, with delta discovery every 5 minutes.
I tried changing the settings, and running a full discovery, without success.
My next attempt was to include an AD Security Group, which the computers are member, into the AD Group Discovery, and ran a full discovery cycle.
While monitoring "adsgdis.log" I could see the DDR being created for a faulty machine:
INFO: DDR was written for system 'COMPUTERNAME1' - E:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\adhsain1.DDR at 1/18/2023 13:58:11.
I also tried running the "Discovery Data Collection Cycle", both locally and through the console.
Analyzing the logs, the communication seems to be occurring normally.
The computer is not duplicated, obsolete or decommissioned on the database.
The computer shows as active and online, with recent policy requests, hardware / software inventory, heartbeat DDR...
Is there anywhere else I can look?
At this point I don't know what else to try.
Appreciate your help.
Thanks!

Answer 1

Hi Cherry, thank you for your reply!

1, Can we add the clients to the corresponding collection manually?

Yes. The client is active, and we can perform actions with it. It just doesn't appear in the query because the distinguished name is null.

2, Whether the client join the domain successfully and appears in the corresponding Domain OU?

Yes, the client successfully joins the domain, and I can find it in the corresponding OU.

3, Are there any exceptions during client installation?

No, the client installation happens without errors during the imaging process.

Update:

Yesterday I have changed the options for the AD System Discovery, and ran a full discovery.

More specifically, unchecked these boxes:

During the discovery, I've monitored adsysdis.log, looked when the DDR was created for the faulty machine, and looked into it to see if the information was there.

And it was, distinguished name, AD site, OS name and version, all there, so I thought the problem was solved:

Fast forward to today, I checked to make sure the discovery process was over, and went to check if the info was there, without success:

At this moment, I've restored the system discovery config and I'm running another full discovery.

Appreciate your attention.

Thank you very much!

Answer 2

Hi @Francisco Nabas, 

Here is my analysis of your environment and some information for your reference. If I misunderstand something, please let me know, thank!

Please select a test client and check the following information.

computers recently imaged are not appearing in the collections.

1, Can we add the clients to the corresponding collection manually?

2, Whether the client join the domain successfully and appears in the corresponding Domain OU? Please help check Smsts.log in client. The screenshots for your reference:

For adsysdis.log, Is the server scanning the domain OU you selected? The screenshot for your reference:

3, Are there any exceptions during client installation? Please help check Smsts.log and ccmsetup.log in client. The screenshot for your reference:

4, Heartbeat discovery is used to help maintain the database record of Configuration Manager clients, in addition to maintaining the database record, this method can force discovery of a computer as a new resource record. It can also repopulate the database record of a computer that was deleted from the database. It also ensures that the discovery data records (DDRs) for devices are up to date.

When heartbeat discovery runs, it creates a DDR that has the client's current information. The client then copies this small file to a management point so that a primary site can process it. The file is about 1 KB in size and has the following information:

• ·         Network location
• ·         NetBIOS name
• ·         Version of the client agent
• ·         Operational status details

Actions for heartbeat discovery are logged on the client in the InventoryAgent.log file in the %Windir%\CCM\Logs folder.

Looking forward to your reply.

Best regards,
Cherry