Implementing Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 02:46 AM
Beginning to implement Discovery - what are some of your experiences for successful implementations? and also, even more important, what are some lessons learned from unsuccessful implementations?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 04:30 AM
Please find link below will assist your ask
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 10:24 AM
Hi,
Before effectively implementing Discovery in our organization, we faced significant challenges with bad data and duplicate CI records. Many of these duplicates were manually created or imported via import sets. To address this, we first stopped manual CI creation and adjusted the import set process to prevent duplicate entries. Additionally, we modified our IRE (Identification and Reconciliation Engine) rules, which helped stop the creation of duplicate CIs. However, we were left with 8,000 duplicate CI records that needed to be cleaned up. Through CI remediation tasks, we have successfully resolved about 4,000 duplicates and continue working on the remaining ones.
For a successful implementation, we took a structured, phased approach:
- Preparation Phase: We set up all necessary credentials and installed additional MID servers on our network.
- Optimization Phase: We restructured our Discovery schedules based on locations to improve efficiency.
- Execution & Continuous Improvement: We extracted CI records, scanned devices, and followed up with the Server and Network teams to address any failures. Additionally, we disabled Discovery scans for desktops and Mac devices, as we were using LANDESK to update the CMDB.
- Governance & Accuracy: We established a CMDB Governance Team to maintain data integrity. Currently, in Phase 3, we are focusing on discovering and mapping Business Applications.
Key Lessons Learned:
- Data Hygiene is Critical: Addressing duplicate CIs before implementing Discovery prevented further complications.
- Governance Matters: Establishing a CMDB Governance Team early helped maintain data integrity and streamlined decision-making.
- Incremental Implementation Works Best: A phased approach ensured better control over each stage of implementation.
- Continuous Monitoring is Essential: Regular follow-ups with IT teams helped resolve scan failures quickly.
- Tool Alignment is Necessary: Disabling Discovery for devices already managed by LANDESK prevented redundant data collection.
Today, our data accuracy stands at 94%, with Discovery serving as our single source of truth. While challenges remain, our structured approach has significantly improved our CMDB accuracy and reliability.
For more information, please check out https://www.servicenow.com/community/cmdb-articles/discovery-welcome-guide/ta-p/2553493
If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.
Thank you for your consideration.
Selva Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 10:27 AM
Great Explanation @Selva Arun ! 👏
