- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hello @Evee ,
You can maintain CMDB Accuracy and Prevent Duplicate CIs:
Use strong, unique identifiers (serial number, asset tag, correlation ID).
Ensure all data sources use the Identification & Reconciliation Engine (IRE).
Improve discovery quality by fixing patterns and credential issues.
Configure identification rules carefully so IRE updates existing CIs instead of creating new ones. (for prevention)
Standardize naming and attribute formats across all integrations. (for prevention)
Refer this :
Best practices for CMDB Data Management
Handle Duplicate CIs in your CMDB
If my response helped mark as helpful and accept the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @Evee
Check Get Well Playbook : KB0829103 Handle Duplicate CIs in your CMDB
Maintain a healthy CMDB: https://mynow.servicenow.com/now/best-practices/assets/maintain-a-healthy-cmdb
https://www.youtube.com/watch?v=yYRubj_zsko&t=91s
https://www.youtube.com/watch?v=XXaYqJF0zUY&t=2s
Maintain a healthy CMDB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hello @Evee ,
You can maintain CMDB Accuracy and Prevent Duplicate CIs:
Use strong, unique identifiers (serial number, asset tag, correlation ID).
Ensure all data sources use the Identification & Reconciliation Engine (IRE).
Improve discovery quality by fixing patterns and credential issues.
Configure identification rules carefully so IRE updates existing CIs instead of creating new ones. (for prevention)
Standardize naming and attribute formats across all integrations. (for prevention)
Refer this :
Best practices for CMDB Data Management
Handle Duplicate CIs in your CMDB
If my response helped mark as helpful and accept the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @Evee
Check Get Well Playbook : KB0829103 Handle Duplicate CIs in your CMDB
Maintain a healthy CMDB: https://mynow.servicenow.com/now/best-practices/assets/maintain-a-healthy-cmdb
https://www.youtube.com/watch?v=yYRubj_zsko&t=91s
https://www.youtube.com/watch?v=XXaYqJF0zUY&t=2s