Struggling with an odd one here... We have SCCM 2012 computer identity coming in.
The Transform Map is actually built to coalesce on ServiceNow sys_id, with a lot of supporting logic/script.
There are a number of cases now, where we find basic computer information such as serial number, chassis type, model, and name flip flopping back and forth and back and forth again.
A view of the CI record: It shows Sources (2) where two SCCM entries with unique Correlation IDs (Resource IDs) are reported
And a further look into the audit history of this CI to illustrate these basic fields that keep flip flop changing back and forth:
CI Audit history list:
Is this a simple case of multiple Correlation IDs coming from SCCM, perhaps due to re imaging of the machine, or other types of typical work?
Suggested logic to prevent this?
Thanks for all ideas
