Hi All!

I have created an SCCM collection which looks for duplicate machine entries. Below is my membership rule.

select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier,R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r   full join SMS_R_System as s1 on s1.ResourceId = r.ResourceId   full join SMS_R_System as s2 on s2.Name = s1.Name   where s1.Name = s2.Name and s1.ResourceId != s2.ResourceId

I am getting resources populated that the following maintenance tasks don't seem to be cleaning up.

• Delete Aged Discovery Data
• Delete Inactive Client Discovery Data
• Delete Obsolete Client Discover Data

I was curious if AD System discovery could be picking up and creating DDR's based off of stale (A) resource records in AD DNS? I have a hunch this could be happening and causing duplicate computer objects to appear. Can anyone confirm or deny this functionally? 

--Tony

Yes it will.. When you clean up DNS, or AD it will get removed form CM12, ~90 days later. (aka whatever you have set for your maintenance tasks)

what logs would I be looking at to determine what objects in SCCM are having the errors?

What error are you talking about?

what logs would I be looking at to determine what objects in SCCM are having the errors?