As far as I can see in adsgdis.log, groups are processed:

INFO: Successfully updated the Group membership tables for Group 'XXXX

INFO: DDR was written for Group 'XXXXX'

• Edited by misten66 23 hours 50 minutes ago

I asked it because you mentioned "newly imported computer". Alright, could you post adsgdis.log or upload it to onedrive ?

Link to adsgdis.log:

https://onedrive.live.com/redir?resid=2152EAD065119AC3!311&authkey=!AGeeemPJKm8doBE&ithint=folder%2c

Thank you. Could you also tell us the name of computer ?

Name of computers: LK-D02402 - LK-D02406

From the log file :-

INFO: DDR was written for system 'LK-D02402' - F:\Microsoft Configuration Manager\inboxes\auth\ddm.box\adhljrq6.DDR at 7/31/2015 9:55:2.

INFO: DDR was written for system 'LK-D02406' - F:\Microsoft Configuration Manager\inboxes\auth\ddm.box\adhj1vjh.DDR at 7/31/2015 9:55:2.

I see no errors in the log file.

Do you have a back log of discovery records?

I have no other back logs then adsgdis.lo_ (added to OneDrive).

https://onedrive.live.com/redir?resid=2152EAD065119AC3!311&authkey=!AGeeemPJKm8doBE&ithint=folder%2c

• Edited by misten66 20 hours 52 minutes ago

Populating a new imported computer with AD Groups has stopped working in SCCM 2012 R2 SP1 (Site version: 5.00.8239.1000).

The object never gets updated with AD Groups. If you check the imported computer, you can see that Agent Name is "manual Machine Entry" and it never Changes to "SMS_AD_SECURITY_GROUP_DISCOVERY"

• Edited by misten66 Friday, July 31, 2015 7:00 AM

It is happening with all computers within a group.

• Edited by misten66 23 hours 52 minutes ago

I'm sorry I should have been more clear, within your inboxes F:\Microsoft Configuration Manager\inboxes\ are you see a lot of DDRs in any of the folders?

For example F:\Microsoft Configuration Manager\inboxes\auth\ddm.box

Have you confirmed that there are not 2 computes with the same name in CM12 All system collection?

There are no duplicate computer names in All Systems collection but there are lot of DDR files in \inboxes\auth\ddm.box and inboxes\auth\ddm.box\userddrsonly.

• Edited by misten66 15 hours 0 minutes ago

How many is a lot? Is the number slow decreasing?

500 000 files and it is not decreasing.

Now that you know what the problem is, what does your ddm.log say?

I changed the Polling Schedule to start in the future so that it would not trigger a new polling schedule and I can see in ddm.log that records are processed and number of DDR files is decreasing. I think it will take a while to process all files.
What about stopping SMS_EXECUTIVE and delete all DDR files in the inbox and restart SMS_EXECUTIVE to get a fresh start with an clean inbox.
I can also see that some of the computer that is imported are populated with AD groups and I can also notice that Agent Name changed to "SMS_AD_SECURITY_GROUP_AGENT" from "Manual Machine Entry" and other properties are populated.
I think that the cause of the problem is an polling schedule that was set to run too often.
When I check Site Status and Component Status all are in Status OK.

• Edited by misten66 12 hours 30 minutes ago

I don't recommend deleting all the DDR. What I would do is let them process. I would keep an eye on your inbox. At the same time I would recommend that you review all of your setting with respect tot AD discovery, Heartbeat discovery, HW inventory and SW inventory.

I will review my settings and keep an eye on the inbox. The records are now processed in a steady pace. Thanks for you help.

• Marked as answer by misten66 11 hours 23 minutes ago
• Edited by misten66 11 hours 10 minutes ago