The 3rd rule that is just name is the one causing the issue. You would need to modify it to include serial number and allow null values:
After you make that change you would need to remove all records in the sys_object_source table where the target sys id is the ID of the CI you are having issues with.
Here are the out of the box IRE rules for computer.
The way the IRE works is that it will try the match on the first rule then if it doesn't find a match go to the second rule, etc.
Let's walk through an example for you:
| Record | Name | Serial Number |
| 1 | abc | 123 |
| 2 | abc | 234 |
| 3 | abc | 345 |
| 4 | abc | 456 |
| 5 | abc | 567 |
- The IRE will look for record 1, find no match based on the serial number lookup rule, serial number rule, name rule, or the network adapter lookup rule and create a CI with name = abc and serial number = 123.
- The IRE will look for record 2, find no match based on the serial number lookup rule, find no record based on the serial number rule (123 does not equal 234), but will then find a match based on the name rule (abc equals abc). This means the IRE will identify that record as being the same and update it. The CI will now have name = abd and serial number = 234.
- Records 3, 4, and 5 will also follow the same pattern as 2
This means that you will have to either modify the IRE rules so that you don't match on name alone or modify the JAMF mapping to name in the IntegrationHub ETL to make sure the name is unique.
If you modify the IRE rules you will also need to clear out the records in sys_object_source as the IRE will use the id lookup on sys_object_source to shortcut the IRE.
The 3rd rule that is just name is the one causing the issue. You would need to modify it to include serial number and allow null values:
After you make that change you would need to remove all records in the sys_object_source table where the target sys id is the ID of the CI you are having issues with.
