question Re: SCCM Computer Identity changing serial numbers, names, back and forth? in Developer forum

SCCM Computer Identity changing serial numbers, names, back and forth?

Matt C — Wed, 09 May 2018 19:57:15 GMT

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

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Kumar38 — Wed, 10 Jul 2019 03:15:25 GMT

Hi,

We have the same issue and did your issue gets fixed. If yes, please let me know the steps to be taken..

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Cameron Boote — Tue, 05 Nov 2019 21:44:50 GMT

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.

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Vihitha — Fri, 10 Jan 2020 17:46:52 GMT

Hi,

We are also facing the same issue. Did anyone figured out the fix for this ?

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Ian Mildon — Fri, 10 Jan 2020 17:55:38 GMT

Same issue here and currently have a ticket in to HI. We're also seeing it in our Remediate Duplicate Tasks entries.

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Vihitha — Mon, 13 Jan 2020 15:22:05 GMT

Please update the solution if you find any.

Thank you

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Kumar38 — Mon, 20 Jan 2020 16:46:02 GMT

we made changes so that SCCM integration uses serial number as Primary Key instead of correlation ID . See if it works in your case

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

pbostian — Wed, 04 Mar 2020 14:28:02 GMT

we had EXACTLY the same issues... Had been making all the appropriate reconciliation rules, and not understanding why SCCM and Discovery were fighting. We have been updating the CMDB identifiers, but the system was still set to use the CI identifiers.... need to set the appropriate system property (glide.discovery.use_cmdb_identifiers) to TRUE. that fixed the issue for us. Months of frustration and confusion, and it was one simple sys_property.

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Sam Ogden — Thu, 18 Jun 2020 11:33:50 GMT

Hi Ian,

Did you get a solution back from your Hi ticket, we have the same issue

Thanks

Sam

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Sam Ogden — Thu, 18 Jun 2020 11:34:45 GMT

Hi Cameron,

Did you get a solution to this, we are seeing the same issue.

Thanks

Sam

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Ian Mildon — Mon, 22 Jun 2020 15:42:23 GMT

We actually ran into multiple issues affecting both SCCM and Discovery:

1. AIX servers being classified as IP Routers

Change the "Classification Priority" in the "discovery_port_probe" table so that SSH is triggered ahead of SNMP and this should fix your issue

2. Windows Servers being classified (flipping) between Windows Servers, Printers, IP Routers

https://hi.service-now.com/problem.do?sysparm_query=number=PRB1408983

Issue is 3 "bad" OID records, need to deactivate them

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Karlie — Thu, 18 Feb 2021 20:20:25 GMT

Sam,

We are having the same issue now. I know this is old but any luck on your side?

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Sam Ogden — Fri, 19 Feb 2021 10:55:41 GMT

Hi Karlie,

Unfortunately I've changed roles since then. I don't recall getting a fix for this before I left.

Thanks

Sam

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Ian Mildon — Fri, 19 Feb 2021 13:06:04 GMT

It's been a while since I've done anything on this but after a combination of deactivating the bad OID's, tweaking my classification rules and getting updated OID's, it doesn't appear to be an issue now.

Or if it is still an issue, no-one has noticed yet. Guess I need to go take another look now!

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Remo Stacy — Fri, 08 Dec 2023 21:03:25 GMT

In SCCM the Correlation ID (Resource ID in SCCM) can change if the computer is reimaged, or sometimes just if someone redeploys the local SCCM app to resolve some other issue (maybe it is not reporting).

In this SCCM history log from an affected computer, you can see that the laptop linked to the Correlation ID changed on 08/31/2023 from XXXXXX00L to XXXXXX93L when we reimaged the device.

After this date, the Correlation ID refers to a different device. Afterwards, our SNOW logs show it switches to the old computer and then to the new computer every night, when we synch.

Do you have any idea how to correct affected computers? We've tried editing the cmdb_serial_number.list and the computer records themselves, but they just switch back. Any idea how can we associate the new Correlation ID with XXXXXX00L ?

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Remo Stacy — Fri, 08 Dec 2023 21:05:08 GMT

In this SCCM history log from an affected computer, you can see that the laptop linked to the Correlation ID changed on 08/31/2023 from XXXXXX00L to XXXXXX93L when we reimaged the device.

After this date, the Correlation ID refers to a different device. Afterwards, our SNOW logs show it switches to the old computer and then to the new computer every night, when we synch.

Re: SCCM Computer Identity changing serial numbers, names, back and forth?

Remo Stacy — Thu, 04 Jan 2024 16:35:33 GMT

In the end, we were advised by ServiceNow support to stop using the legacy Integration - Microsoft SCCM 2016 - and switch to Service Graph Connectors. This solved the issue as reported, the Robust Transformer did a much better job at identifying whether to update a device or create a new one, but we had some extensive cleanup to complete afterwards.