Computers from SG-Intune have lowercase names

[MarLoi]

Hello!

One of the Service Graph Connectors used in our instance is SG-Intune.
This year, we have noticed that most computer names in the [cmdb_ci_computer] table ingested by SG-Intune are in lowercase, even when the corresponding values in the deviceName field of the import table contain uppercase letters.

However, there are also some computers for which the correct capitalization is preserved.

We investigated the glide.discovery.hostname.case system property, but it is set to "Lower case" and was last updated by ServiceNow in 2011.

It doesn't explain why some computers have the correct capitalization, instead of lowercase.

Through the IntegrationHub ETL, we also looked into the associated RTE Entity Script Operation [sys_rte_eb_script_operation], Script Operation - u_devicename, which transforms the import value into the value of the computer name field.

However, this was last updated by ServiceNow in 2024.

Are there any other possible leads we could investigate that might explain this inconsistency?

For example, could there be another conversion, normalization, or processing step taking place between the import table and the cmdb_ci_computer record that we should look into?

Thanks in advance for your help!

#discovery #sgc #intune #ci #computer #cmdb #ingestion

[drbob]

Is anything else updating these CIs ?
If you change the hostname (make some characters upper case) are they reset by the next import ?

Does the audit log  (history) on the CI show the update and was it done by the user running the import ?

That will confirm it _is_ the import that is at fault not any other process (though it could still be some business rule that runs as a result of the import or other process rather then the import itself).

If it's confirmed to be the import process (whether the ETL or a business rule or something else) compare one of the ones that got set to lowercase against one that didn't - any significant differences (anything that in context you recognize someone might have written a business rule for, for example ...or something more obvious like it ended up in a different class). Any workflow or flow firing against it ?