How to stop ‘SG-SCCM Computer Identity’ from updating serial number.

[Anton15]

Hi

Is it possible to stop the robust transform ‘SG-SCCM Computer Identity’ changing the value of an existing serial number in the computer table?

Thanks

[CMDB Whisperer]

Since serial number is the highest priority identifier, it generally should not update an existing serial number for a CI.  Some reasons why this could be happening:

1. Some other data source is not going through the IRE and is coalescing on the name or possibly correlation ID, and then setting the serial number.  If this is the case, you should consider refactoring that data source to go through IRE by migrating it to IntegrationHub ETL instead of traditional transform map.
2. You have changed the priority of the out of box identifier entries such that another attribute is taking priority over serial number.  If this is the case, you should strongly consider reverting that so that serial number takes priority.
3. Since there are actually two different serial number identifier entries, it is possible that they are in conflict with one another.  I have seen this happen before.  In my case, what I traced this to was the fact that the Discovery pattern was prioritizing the serial number table in a different order than it should have, putting Baseboard Serial Number ahead of BIOS Serial Number, whereas SCCM was using BIOS Serial Number.  As a result, when Discovery and SCCM were hitting the same record it was causing the serial number to flip.  This only happened on a few machines and it was difficult to track down and fix but in the end I believe I opted to make a change to the discovery pattern and/or the reconciliation rules.

If you do want to take a look at the available methods of modifying the Service Graph transform, you should do so only using IntegrationHub ETL application.  I wouldn't suggest modifying the Robust Transform directly.