Duplicate records for the same computer

Question

I have recently deployed SCCM 2007 SP1 with R2 for a customer.  We are currently in the process of deploying imaging and are having an issue with duplicate computers showing up.  The duplicates appear to be for the same computer.  I have read everything I can on duplicate computers showing up, but none of it has helped.  Basically, we have our base image, which is just a basic install of XP SP2 with all updates.  We lay down the image on a clean computer using an OSD task sequence, and when the machine shows up in the all systems collection, there are two records for it.  The current one is called SCCMTEST01.
The first record shows the following:
Name: SCCMTEST01
Resource Type: System
Domain: OURDOMAIN
Site: 001
Client: Yes
Approved: Approved
Assigned: Yes
Blocked: No
Client Type: Advanced
Obsolete: No
Active: Yes
Properties:
Agent Name[0]: MP_ClientRegistration
Agent Name[1]: Heartbeat Discovery
The second record shows the following:
Name: SCCMTEST01
Resource Type: System
Domain: OURDOMAIN
Site: 001
Client: No
Approved: N/A
Assigned: Yes
Blocked: No
Client Type:
Obsolete:
Active:
Properties:
Agent Name[0]: SMS_AD_SYSTEM_DISCOVERY_AGENT
Agent Name[1]: SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT
The first one appears to be the active one, since it includes more information and the client is listed as installed.  Does anyone have any suggestions on what might be misconfigured?
thanks,
Justin

Answer 1

I'm experiencing the same behaviour as described above. Not using any other OS distribution methods than scripted installation from RIS, will obviously make explanations based on OS Deployment behaviour not applicable in my case.
The thing is that an object being discovered by Heartbeat, MP_Registration, SMS_AD_SYSTEM and SMS_AD_SYSTEN_GROUP... until suddenly, SMS_AD_SYSTEM_GROUP discovery agent starts generating a new object and updates that object from the moment on. Heartbeat from the client still updates the original object. This is done for about five object a day (among 2600 alltogether), and it's not the same computers that do this (apart from some, troublesome clients...).
When finding this duplicate object, I have kept the one generated by SMS_AD_SYSTEM... and then reinitiated a Heartbeat Discovery on that object. Doing this will make Heartbeat to update the new object (now the original is gone), and everything seem to work for a while, although I have to manually approve that object again.
I cannot work out what makes SMS_AD_SYSTEM... generate a new object.
Does anyone have an idea?
/Jakob