Just want to understand, why does I see a duplicate machine object in my console? Same machine name but with 2 object in the console. One with client status No and another is Yes. Correct me if im wrong, this means that it is one of the obsolete object? In what situation that an object machine can have been duplicated? I noticed that if I reimage the machine, then will encounter this situation, that have 2 duplicate object. But not sure what causes it...

Bring up the properties of each resource and see which discovery agent added it. You can also add the "obsolete" column. 
Duplicates should not occur when reimaging a domain joined machine. Any chance that AD system discovery added the second one?

This query will give you a collection of all duplicate items.

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

Also, just because two resources have the same name does not mean that they are duplicates. The resource marked as No client (the first in the screenshot above) doesn't necessarily correspond to a real system even. It was simply imported or discovered and happens to have the same name as another resource. Bottom line is that the Name of a resource is not a unique identifier. Following Torsten's advice of examining the properties of the resource will tell you how the resource was created (in the agent name field).

I've checked the duplicate object properties and seems that one was discovered by heartbeat and another by SMS AD System Discovery. Not sure why as I would think that it would combine into 1 single object even though discovered by any other method....

Heartbeat discovery doesn't discover any new resource, only AD System Discovery does.

And while you reimage may be machines SMS certificates get deleted and new certificates created. So you will have duplicate machine object in the console.

Check if you get different SMS GUID before and after re-image?

-Ashu

• Edited by Ashribad Rout Wednesday, February 18, 2015 9:07 PM

Actually, that's not true. All discoveries are ultimately equal. If the site receives a heartbeat DDR for a system that does not match a current resource, it will create a resource based on that heartbeat DDR. This happens if you delete a resource from the console (either mistakenly or not) and the client agent is still active or becomes active again.

Generally, ConfigMgr can merge duplicate resources based on different criteria, but in this case, that obviously did not happen. The one with the AD System Discovery agent is probably also marked as not having a client agent installed. If so, I would simply delete it.

Ok. So meaning the object will not get any deployments until I delete the duplicate record right...

It depends on how you set your collections up. Say both objects are named DEVICE01. 

If you do a direct membership and add the AD system discovered object (Client = No), then no, that device will never get any deployments because it doesn't actually correspond to a real machine on your network. 

If you add a query membership rule for all records with a name of DEVICE01, then both records will get added to your collection, and your real device will get the deployments. 

Daniel is correct.  

You may look at the properties of both objects to determine:

Discovery method, AD system, manual entry, heartbeat, MP registration, etc.

Also compare MAC addresses and see if they are the same and discovery dates as the one with the no client, probably is older.

If there is other information in both of them, like IP, etc, but I bet with the computer object with out the client only has rudimentary discovery data.  

Once you feel that the object without the client is duplicate, you could delete it.  If it isn't, then the next discovery will pick it back up. 

You also should create a collection with duplicate records, if you haven't already.

There is also a canned report, if you have a reporting point enabled, for duplicate MAC addresses which is somewhat helpful.