sccm duplicate target_sys_id

tenagra · ‎11-15-2017

Hello everyone,

While testing the SCCM Integration 2012v2 for Jakarta, I've come across an issue I can't figure out. There was a PC that wasn't int the cmdb_ci_computer table as I would have expected, but I can see it as part of the import log. I traced this back duplicate target_sys_id records in the [imp_sccm2012v2_computer_id] transition table. In short, 2 different computer names (ts001-eqlt011b & TS001-EQLT120B) in SCCM, with 2 different ResrouceID have the same target_sys_id in this table (3bef4c8c4fee8f80a4d3650f0310c7e9). When looking at the history for CI, I can see where it is updating the CI back and forth with the two different names.

So 2 questions:

1) Does anyone have any clue on how this would happen and/or how I can go about figuring out how this happened?

2) What is the process for separating these so that we get the separate cmdb_ci_computer entries as one would expect?

Thank you all for the assistance.

Sincerely,

Nathan

Patrick Schult2 · ‎11-15-2017

Are you familiar with CI Identifiers and how the SCCM import uses them? I'd recommend deleting both sys_object_source AND clearing the Correlation ID value for this CI and let the next import locate the CI via serial number or name.

Once you delete the sys_object_source records, the next import will use the CI Identifiers functionality (SCCM > CI Identification > CI Identifiers) to locate the CI to update. In your case, you will have deleted the object source records, and the Correlation ID (SCCM resource ID) from the CI, so it would then fall to Serial Number, then Name, then some other stuff.

Untangling CIs in this kind of situation is rarely clean - see if this gets you back in shape.

View solution in original post

thomas_wright1 · ‎09-07-2018

Patrick,

Thanks for this info, it helped in tracking down why I have duplicate workstation CI. When I look at the sys_object_source table I see multiple entries for SCCM. One that has a unique ID and two that have the same ID. Looking at the target sys_id's, the two with the same ID have different sys_id's.

So if I wanted to clean up this mess, would I delete each entry from SCCM on that table and on the workstation table and let SCCM run to update the correct CI?

Thanks

Tom

Kumar38 · ‎07-15-2019

Hi,

How could we address the issue of SCCM resource id keeps changing , so that we dont create duplicates

kambleneeta20 · ‎06-10-2020

Hi ,

We are also facing the same issue, resource ID is getting change for the OLD/Retired CI , instead of creating a new CI. Have you find out any solution , how to avoid it ? Could you please suggest ?

Kumar38 · ‎06-21-2020

sorry for the late response . we modified our SCCM to use serial number as primary key

Damhoej · ‎09-13-2021

Can you tell how you modified SCCM?