- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @SandeepKSingh
Below Article will help :
https://www.servicenow.com/community/itom-forum/discovery-not-identifying-windows-devices-that-it-us...
and Mean just check if mid server is up, credentials are correct and Shazzam is checking for the correct port-probe.
If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!
Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI
ï”— YouTube: https://www.youtube.com/@learnservicenowwithravi
ï”— LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Check and confirm you have connectivity between MID Server and target device and credentials are correct. Check the probes and sensors xml payload to see which phase of discovery is failing. If you are receiving details of the device and is failing with Identification phase, check below articles,
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0715696
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0725605
If this helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I check everything is fine.. don’t know what’s the issue..
mid is up , credentials are there.. etc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Can you share the discovery logs from quick discovery ?
XML payload would show which phase it is failing and why CI is not created that can be useful in troubleshooting.
If this helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Port probe was missing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Glad to know it is working now.
As mentioned, discovery logs and ECC queue would provide more details of the discovery job and finer information that can be used for troubleshooting. You can go to XML payload of a step that is failing to identify the cause and resolve the issue.
As per community guidelines, you can accept more than one answer as accepted solution. If my response helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan