CMDB deduplication related issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2024 08:26 AM
.
Dear Experts,
Our HAM asset management process recently identified potential duplicate CIs in the CMDB, even though these assets were scanned with ServiceNow apps and have unique asset numbers. Since imaging is the only trigger for CI changes, I'm inquiring about the CMDB's deduplication criteria. Does it solely rely on CI names, or are asset tags or serial numbers also considered? Understanding this will help identify the root cause of duplications, prevent future issues, and improve communication clarity about potential duplicates. Your expertise in clarifying the CMDB's deduplication approach, particularly regarding asset tags and serial numbers, would be greatly appreciated. Because CMDB team are deleting base solely on CI name.
Thank you,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2024 02:50 PM
Duplicates are created based on all the identification rules that are defined for the CI, please look at the duplicate task and it will indicate which rule it matched and which fields are used to create the duplicate.
In order to remediate the duplicate task, you can do it individually by using remediate button on the task or do group remediation using CMDB workspace https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/configuration-manageme...