SCCM Computer Identity changing serial numbers, names, back and forth?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-09-2018 12:57 PM
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
- Labels:
-
Integrations
-
Scripting and Coding
- 3,462 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2019 08:15 PM
Hi,
We have the same issue and did your issue gets fixed. If yes, please let me know the steps to be taken..

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-05-2019 01:44 PM
We're seeing the same issue. Haven't been able to figure out any kind of pattern as to why it only happens on certain machines. Seems to be related to the configuration item getting the wrong correlation ID from SCCM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2020 04:34 AM
Hi Cameron,
Did you get a solution to this, we are seeing the same issue.
Thanks
Sam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-10-2020 09:46 AM
Hi,
We are also facing the same issue. Did anyone figured out the fix for this ?