Multiple Discovery Source in CMDB-Need Help Urgent!

[MDAQUIBK]

We have multiple discovery sources integrated in ServiceNow, including Azure, ServiceNow, AWS, and Tanium. Recently, we integrated Tanium for discovering computers and servers. For servers, we have multiple sources: Azure, AWS, ServiceNow, and Tanium.

Issue: We have already remediated around 50 servers with duplicate sources coming from ServiceNow, AWS, Azure, and Tanium. However, the issue persists where software installation records are still being updated on the duplicate CI (Tanium CI) instead of the main CI, which should be from ServiceNow, AWS, or Azure.

Desired Outcome: We want to mark the Tanium server CI as duplicate and ensure that software installation records from Tanium are updated on the main CI (the CI from AWS, Azure, or ServiceNow). In essence, we want to retain the main CI from AWS, Azure, and ServiceNow as the source for software installation records.

Clarification:

• Important Note: We are not deleting the duplicate Tanium CI. We are only marking the Tanium CI as duplicate (set to true).
• The server's name coming from Tanium is “ABC.network.lan,” whereas the server name from the other sources is simply “ABC.”

Question: Will deleting the duplicate CI (Tanium CI) help resolve this issue and ensure that software installation records are routed to the main CI? Please help how can we achieve this 

Please Help! Your feedback is valuable 

---

[Taylor_Nous]

Would love to connect! Shoot me a message if you have time today to connect. 

[MDAQUIBK]

Hi @Taylor_Nous ,

 How can we connect ? Do you have any web link where I can join ?