Intune SG import identifier (strange behaviour for import of one device)

[Florian Spisla]

I am currently checking the duplicates in the CMDB and run the de-duplication tasks, after I figured out, why there was a duplicate. A lot of them occur because people do not adhere to the Asset Mgmt processes...

But now I stumbled upon something I cannot figure out.

According to the remediation task, two devices have the same serial number. When I look at one of the devices' history, something strange started to happen a while ago.

So basically the computer CI was created a while ago with an import from SCCM. SCCM import was then turned off and replaced by Intune SG import.

Then suddenly about 5 months ago, the CI is changing a lot of entries, e.g. serial number, Model ID, etc. so it seems as the CI is all of a sudden a completely different notebook.

And then about 4 weeks ago, I see 8 entries every morning for the import. The first 4 replace the existing information in the attributes Description, Serial number, Name and Model ID. Only a few seconds later these attributes are then replaced again by the original (correct) information.

So, the information that is imported first is that of another notebook we manage in Intune. This other notebook has its own CI which was created based on a manually entered Asset. This other notebook does not get updated by the Intune SG import.

Any idea why 2 devices from Intune are somehow connected to the first CI? How can I find out, why this CI is updated twice within seconds and the second CI is ignored, even though the SN is the same as in Intune?

What is the identifier that is used here to match devices from Intune and the corresponding CI?

[AJ-TechTrek]

Hi @Florian Spisla ,

Same issue i faced while i am implementation the Intune for a customer, so I did the below things.

1. I checked for Identifications and Reconciliation rules for that Class.

2. I worked on Deduplication task of those CI and Merged into in a single Parent CI.

3. I checked the Correlation ID which is passing through the Intune and Vefiy the data in ETL Hub

4. Updated the Intune connector from ServiceNow Store.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[Florian Spisla · Accepted solution]

Okay, I did find the issue here myself. On one of the CIs there was not the Serialnumber attribute of the CI itself filled in, but additional serial numbers for Chassis, System and BIOS existed as well.

At some point it seems, that my colleagues decided to reuse a hostname and so the existing CI got a name Main-Serialnumber and this was added to the existing additional ones. But the original additional serialnumbers were not deleted.