Hi, Is there a way to eliminate multiple entry in the SCCM ConfigMgr console? Is it possible? It seems like that the Console cannot resolve duplicate entries. thanks!

Have you checked the properties of each record? Can you please go through the below link ? Is that your issue? http://anoopmannur.wordpress.com/2011/04/08/configmgr-sccm-duplicate-record-issue/ Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

What is "duplicate"? Any chance that there's only one "active=yes, obsolete=no" whereas the others are "active=no, obsolete=yes"?Torsten Meringer | http://www.mssccmfaq.de

I think it is quite similar to that? Is it recommendable to have just one discovery method to avoid the problem?

Maybe duplicate is not the right term, i would say multiple entry. I've checked one computer with two entry under all systems collection, one has client=yes and the other one client=no.

Did you try to create collection mentioned in the below mentioned blog? or you can use the below mentioned method? http://ccmexec.com/2011/03/merging-obsolete-records-in-configuration-manager-2007/Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I tried creating the collection based on the the blog you mentioned but it did not return duplicate entries. My reference is the computer name. http://ccmexec.com/2011/03/merging-obsolete-records-in-configuration-manager-2007/, I think this one resolves obsolete records, I haven't try this one. Can't try yet in production, I can try this in our Lab but the problem does not appear in it. :). Maybe because it has fewer workstations.

Can you do some more analysis on this issue? Like, Select one of the system which has two records in the console and compare the properties of each system record - AGENT NAME and AGENT TIME. This may help to get some clue of the issue? Also, check the records if the one of the record is having OBSOLETE value as YES? Obsolete Indicates whether this client record is obsolete. A record that is marked obsolete typically was superseded by a newer record for the same client. The newer record becomes the client's current record, and the older record becomes obsolete.Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi An00p, Here's my initial comparison, CompA - client=No Approved=N/A Assigned=Yes Blocked=Blank Client Type=Blank Obsolete=Blank Active=Blank CompB - client=Yes Approved=Yes Assigned=Yes Blocked=No Client Type=Advanced Obsolete=No Active=Yes Most of the properties of CompA are <null>. I think the client column makes the difference between the two.

How about AGENT NAME and AGENT TIME. This may help to get some clue of the issue?Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Is there a way to eliminate multiple entry in the SCCM ConfigMgr console? Is it possible? It seems like that the Console cannot resolve duplicate entries. [...] CompA - client=No Approved=N/A Assigned=Yes Blocked=Blank Client Type=Blank Obsolete=Blank Active=Blank CompB - client=Yes Approved=Yes Assigned=Yes Blocked=No Client Type=Advanced Obsolete=No Active=Yes There are no duplicatesTorsten Meringer | http://www.mssccmfaq.de

Hi Torsten, I just used CompA and CompB to represent the computer names but actually they have the same computer name.