Hi Environment: SCCM 2007 SP1, Single Site, upgraded from SMS 2003. We are currentlyperforming a workstation refresh programme during which SCCMhas built up a large number of duplicate machine names showing in the admin console. I was under the impression that when a duplicate machine name appeared SCCM would mark the older record as Obsolete (it cetainly did this in SMS) - this is not happening. Because the older machines are not being marked Obsolete the maintenance task is not removing the old machine data from the SCCM database. The Discovery settings are as they were in SMS, i.e. AD System one per day and Heartbeat once per day. Any idea why this could be happening? Also I have been trying to create a Collection that includes all the machines that appear more than once without success. Any ideas how to do this? I am able to create a Report based on a SQL query to list the duplicates but would like a Collectionmaking it easier to highlight and delete them manually if required. Thanks

you can create a maintanance task and fulfil the requirment. for cretaing the collection first create the collection, on the properties of that collection go to memebership rules click the folwer icon.select system resource for the interger values give the value 0 for the collection specify the all system then you can identify all the clients which is not a client yer.once you got all that in to the collection you can remove all. sanka

Hi Sanka Thanks for the reply, however this does not work due to the fact the 'old' clients are still shown as having a client installed thus have a value of 1 then same as the new machine. This is not time related as some of the duplicate names have been showing for a month and more. Kandle

When the machines are double, one of them should be obsolete, i must ask, did you update your collection membership and refreshedthe collection?

Yes - this has been a problem that has been going on for quite a long time (over a month and maybe longer) and as well as numerous manual updates to collections, all collections are scheduled to update at least once per day.

Hi there, You're right, this functionality carried in to ConfigMgr and you should be seeing obsolete marked for these duplicates. "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." Can you expand on "workstation refresh programme", how are you achieving this? Also examine one of these zombie records and it's replacement record, see if anything becomes visible by looking at each records properties. See if any of these match up ... Hardware ID, MAC Address, System UUID, SMS Unique Identifier (should be unique) and Creation Date. Should give you an idea if they are definately from the same machine ... All I can think is that these machines have a new Hardware ID and thus are showing up as different clients and therefore the old ones are not immediately marked as obsolete but will eventually become noted as inactive and groomed if you have the task enabled. Worth checking, "Delete Inactive Client Discovery Data" task, is it enabled? By default believe it is not ...

Hi - thanks for the reply. Workstation refresh means old machine removed, new machine installed and new machine's given the same name as the old machine. This is how we have always repaced machines and under SMS the old machine got marked inactive fairly quickly (can't rememberexactly hoe long but we never had a build up of more than a few machines). Delete Inactive Discovery data is turned on and set to every 45 days.

I am having the same problem in my environment. Two records with the same machine name, but different Hardware ID's, but both are marked as Active. Any idea how to fix this issue. It messes up our reporting.

What about the ConfigMgr GUID? How have you deployed those clients? Imaging?

What about that?:select * from sms_g_system_SYSTEM as g INNER JOIN sms_gh_system_SYSTEM as h on g.ResourceId = h.ResourceId where g.Name <> h.Name I use it in my SMS2003 environment and it works just fine...Maybe you have to change sql views for configmgr sql db views...Another solution - make a query for last software scan on these duplicate computers and delete the one with an older date...Good luck :)MCP,MCTS | jan-marek.com

hi, so the solution to this is to delete the records manually? any idea how to stop this from happening? in my case the duplicate 1 has client, the other has no client. and it looks like those entries were caused by the discovery method of AD and heartbeat etc. And the problem is it does not mark the old one as obsolete hence they all remain there. comment will be appreciated. Cheers, Xm