none
duplicate computers in sccm

    Вопрос

  • Hi all!

     

    I have some computers which are presented twice in the sccm. For example in the collection view I can see the same computer with the sccm client installed and without the client . 

    What could be the problem?

     

     

    Thanks in advance!

     

     

    Zoltán 

    21 октября 2008 г. 12:53

Ответы

  • Well, you can *always* delete a record, even if it is a client and not obsolete :-) And it won't *break* anything.

     

    However, generally, if you have duplicates, as Matthew says, one will be listed as obsolete. And as I mentioned earlier, that usually comes from reinstalling the client without reusing the same SMS Unique ID (GUID). We would create a new record as the new DDR contained a new GUID. We would then 'obsolete' the previous record.

     

    We actually have a site maintenance task that will delete obsolete systems if you enable it. Check Delete Obsolete Client Discovery Data (not enabled by default).

    20 ноября 2008 г. 21:35
    Владелец

Все ответы

  •  

    If you scroll over is the Obsolete Flag set to Yes?

     

    Have you upgraded this client?

    Have you modified the GUID on the machine at any time?

    Have you redeployed the OS to the machine, what the client installed in the image?

     

    21 октября 2008 г. 13:09
    Модератор
  • Did you reinstall the client without deleting it from the All Systems collection, or without reusing the original smscfg.ini file?

     

    21 октября 2008 г. 22:40
    Владелец
  • Is it safe to delete the item that shows the client is not installed?  Does this "fix" the issue?  Will the duplicate client listing return?

     

    19 ноября 2008 г. 19:23
  •  

    As long as the duplicate is also Obsolete then yes it is safe.  It shouldn't come back.
    19 ноября 2008 г. 19:39
    Модератор
  • Well, you can *always* delete a record, even if it is a client and not obsolete :-) And it won't *break* anything.

     

    However, generally, if you have duplicates, as Matthew says, one will be listed as obsolete. And as I mentioned earlier, that usually comes from reinstalling the client without reusing the same SMS Unique ID (GUID). We would create a new record as the new DDR contained a new GUID. We would then 'obsolete' the previous record.

     

    We actually have a site maintenance task that will delete obsolete systems if you enable it. Check Delete Obsolete Client Discovery Data (not enabled by default).

    20 ноября 2008 г. 21:35
    Владелец
  • I found in our SCCM 2007 implementation some records that "active" & not "obsolete" and share the same computername. How can this occur and how to solve it? (so only the SMSID and the ResourceID are unique and both clients seem to be "active").


    from SMS_FULLCollectionMembership table a dump:
                                    Record 1                                       Record 2
    AMTFullVersion          NULL                                             NULL
    AMTStatus                 NULL                                             NULL
    ClientType                 1                                                  1
    CollectionID               S000000E                                      S000000E
    Domain                     CODE1                                          CODE1
    IsActive                     True                                             True
    IsAlwaysInternet         False                                            False
    IsApproved                True                                              True
    IsAssigned                 True                                              True
    IsBlocked                   False                                             False
    IsClient                      True                                              True
    IsDecommissioned      False                                              False
    IsDirect                      False                                              False
    IsInternetEnabled        False                                              False
    IsObsolete                  False                                              False
    Name                         USDFLDSSR1NB3JN                         USDFLDSSR1NB3JN
    ResourceID                 385264                                           223969
    ResourceType              5                                                   5
    SiteCode                     S21                                                S21
    SMSID                        GUID:0182F0EA-DE49-4540-8BB2-377FDA3F2C93     GUID:0002778C-6C30-43A5-8FBF-05CEC9F22E1D           
    SuppressAutoProvision FALSE                                             FALSE


    How to prevent or clean this automatically?

    Cheers,

    Frank.
    Kind Regards, Frank van Rijt
    5 июня 2009 г. 15:11
  • Hi,

     

    We do have similar issue. The old entry doesnt respond to Heardbeat discovery but rest of the discovery works fine for this object. The duplicate (or the new one), responds to Heartbeat but doesnt show any of other agent activity. Both the object share similar name but have different GUIDs.

    Can this be prevented? What do you think is causing this issue?


    Regrads.
    29 сентября 2011 г. 13:50
  • Torsten, there is NO possibility of this happening (for this reason) if we are NOT at R3, correct?

    Thanks.

    5 октября 2011 г. 20:56