hi Experts... I know there are tons of discussion about this but lots of them are about duplicate GUIDs. In my case, there are lots of duplicate Computer Name but they're not the same GUID, in fact, one has GUID, the other one has no GUID and pretty much you can tell it's the old entry which you can tell when you check the property of that object that the window is grey as opposed to white. Anyway... the issue here is that why Config Manager does not delete the old entry? and it does not even mark it as obsolete therefore the obsolete maintenance task won't delete the entry. Anyone has any idea of how to fix this issue? Cheers, Xm

It could be the AD system and AD system group discovery that is causing the two computer accounts. Are you running both of those discovery method?Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

No, just the AD system. however, even though they're both running, should it not cause duplication? surely the system should be smart enough to know right. Apart from AD system, the heartbeat is running too which I assume it's supposed to be. However, how do we fix this? Thanks.

Hi, The dupliate entries are as Kent writes normally created by the AD System Discovery and especially when using delta-discovery, are the duplicate objects obsolete? if not you should have a look at this blog post. http://blogs.technet.com/b/configmgrteam/archive/2011/08/17/known-issue-and-workaround-duplicate-records-when-you-use-unknown-computer-support-with-active-directory-delta-discovery.aspx Regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec

that's what I'd love to see happening i.e. the duplicate to be marked as obsolete. Unfortunately it does not mark is as obsolete therefore no deletion from the database. looking a the blog post: the only difference between his case and mine is that he mentioned the Duplicate client being "Client Not Installed" and "Client Not Assigned". In my case, the Client is Not Installed (which is the same) but Client is "Assigned", which adds more to the confusion now. Should I delete all the Unknown Computers as well?

Hi, I would try the solution described in the blog post as it is most likely the issue you are seeing, are you using AD System Discovery with Delta-discovery enabled? regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec

hi, Not to be semantic, but it's a workaround rather than a solution. So I guess we just have to take it as a known issue and there is no fix yet from MS? yes Delta-discovery is enabled. I'd most likely go for Method#1 i.e. Delete it manually, trying to get method#2 working properly would probably take much more time than the manual fix. Simpler is better :-).

oh.. on the other hand, will it pay if I just turn off the Delta-Discovery?

Hi, You are correct, a work-around would be a better choice of words.. If you install your computers using SCCM OSD the client will register itself and System Discovery is not that crucial anymore. I normally configure AD System Discovery to run once a week, say Saturday/Sunday as it is used to discovery newly installed clients, which there shouldn't be any or clients that have been away from the network AND have a broken SCCM client that will not register itself. AD System Group Discovery on the other hand you want to run more often, but AD System Group Discovery doesn't create any new client objects it only adds attribute to already exisiting, so the poblem should if not be avoided it should be seen much much more seldom. I hope that helps Regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec

hi, what about Delta Discovery? should I turn it off? Looks like though that that's the one what's causing this duplicate dilemma