none
Is Duplicate computer object due to unknowncomputer support and delta discovey Resolved in SCCM 2012???? RRS feed

Answers

  • When you install an operating system by using unknown computer support, the following processes happen:

    1.A record that represents that computer is added to the Configuration Manager database so that the computer can receive the operating system deployment advertisement and run it.
    2.The computer successfully installs the operating system and joins the domain, which creates a computer object in Active Directory Domain Services.
    3.Configuration Manager Active Directory System Discovery finds the computer object in Active Directory Domain Services and creates a discovery data record (DDR) for Configuration Manager.
    4.The computer installs the Configuration Manager client, registers with the Configuration Manager site, and updates the record that was created by unknown computer support.

    If the DDR is created (number 3) after the computer installs (number 4), you won’t see a duplicate record because Configuration Manager has enough information to merge the Active Directory DDR with the computer record.  However, if the DDR is created before the computer installs and registers (in the order listed above), Configuration Manager cannot match and merge the two records, which results in the duplicate record.


    Juke Chou

    TechNet Community Support

    • Marked as answer by nabin777 Monday, February 24, 2014 3:36 PM
    Monday, February 24, 2014 6:31 AM
    Moderator

All replies

  • This is a timing issue. It still exists in SCCM 2012. The workaround is to disable Delta update for AD. Instead, please enable full discovery.

    Juke Chou

    TechNet Community Support

    Sunday, February 23, 2014 12:59 PM
    Moderator
  • Hi Juke

    Thanks for your reply , can u tell me how it really happens in background

    any technical explanation for this.

    Monday, February 24, 2014 5:07 AM
  • When you install an operating system by using unknown computer support, the following processes happen:

    1.A record that represents that computer is added to the Configuration Manager database so that the computer can receive the operating system deployment advertisement and run it.
    2.The computer successfully installs the operating system and joins the domain, which creates a computer object in Active Directory Domain Services.
    3.Configuration Manager Active Directory System Discovery finds the computer object in Active Directory Domain Services and creates a discovery data record (DDR) for Configuration Manager.
    4.The computer installs the Configuration Manager client, registers with the Configuration Manager site, and updates the record that was created by unknown computer support.

    If the DDR is created (number 3) after the computer installs (number 4), you won’t see a duplicate record because Configuration Manager has enough information to merge the Active Directory DDR with the computer record.  However, if the DDR is created before the computer installs and registers (in the order listed above), Configuration Manager cannot match and merge the two records, which results in the duplicate record.


    Juke Chou

    TechNet Community Support

    • Marked as answer by nabin777 Monday, February 24, 2014 3:36 PM
    Monday, February 24, 2014 6:31 AM
    Moderator
  • Reopening this thread.

    So....  I'm seeing this at a customer site.  Exactly what you stated - Unknown record created, SCCM TS joins system to domain, System reboots and completes TS, registers via Heartbeat, then AD Sys Disc comes behind and creates a duplicate record.

    Why, 5 years later, is this still an issue?


    nick

    Tuesday, November 19, 2019 6:38 PM