Hi Team,
I am seeing a mismatch in the OOTB CMDB Data Mismatch Report and would like to understand the best approach to resolve it.
CI Details
CI Name: bp-rtr-test03
Actual CI Record
OS: Windows Server 2019 Standard
Discovery Source: ServiceNow
Discovery Payload for this ci bp-rtr-test03
OS: Windows 2019 Standard
CMDB Data Mismatch Report:
For the same CI, the report shows:
1.Discovery Source: ServiceNow
OS Value: Windows 2019 Standard
2.Discovery source:Tanium
OS Value: Windows Server 2019 Standard
As a result, the CI is appearing in the data mismatch report.
Reconciliation Configuration:
Tanium Priority = 1
ServiceNow Priority = 1
Tanium owns the OS attribute for the Computer class.
ServiceNow does not own the OS attribute (OS is not present in the available slush bucket for ServiceNow on cmdb_ci).
Requirement
The business requirement is to have 0 records in the CMDB Data Mismatch Report while still using the OOTB report.
Questions
1.Since ServiceNow does not own the OS attribute, is this expected behavior?
2.What is the recommended approach to achieve zero mismatches?
3.How to Normalize the OS values between Discovery and Tanium? (Give me step by step instructions to do it)
4.Use identification/reconciliation rules differently?
5.Any OOTB-supported solution?
