CI Names are overwritten - IRE wrongly setup?

[Mercedes Pons 1]

Hi, I would like some help with something I've been observing.

Some CIs are being updated by Midserver changing the Name and FQDN.  

In IRE I have setup CI Name as one of the identifiers.  I want to create a new CI if the name of the server changes (as it may serve to a different application).

Sys_ID is the same, and the Name keeps changing every time Discovery runs.

This only happens with a few of the CIs, it's not a problem for all of them.

What am I doing wrong?

Thank you

[Ashok Sasidhara]

For which all CI classes are you facing this issue? Is it only for server class? Also what are the different data sources populating the CI classes which are having this issue? 

[Mercedes Pons 1]

Hi Ashok, it's happening for servers (Windows and ESX this week) and I only have Discovery as a source.

[Ashok Sasidhara]

The issue seems to be due to having 'Correlation Id' as the first priority identifier. The OOB identifier entries for all hardware classes start with Serial number & Serial number type which is your 2nd priority identifier followed by the remaining entries in your screenshot. Correlation ID usually appears there due to certain integrations which don't go through IRE (E.g. Legacy SCCM integration).

You can create separate identifier entries specific to either all server classes or only for Windows server and ESX server classes initially to test. If you are using only discovery, may be the OOB identifier entries should be sufficient (i.e. all entries in your screenshot except the first one for Correlation ID).

A similar problem and solution is mentioned in the following URL also:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0869861