Discovery not identifying Windows devices that it used to?

[Marcel H_]

I've been having some issues lately with Discovery not identifying Windows devices that it used to find, classify, identify and scan with no problems. Now when scanning a subnet of Windows servers, with known good credentials (I've tested by logging into the servers with the same account running the MID Server service) it will stop in the Identifying stage with a scan status of "Completed 2" and won't identify the CI.

When I check the logs, I get a lot of "Failed Exploring CI Pattern, Pattern name: Windows OS - Servers, To Check Pattern Log Press Here" errors. When checking the pattern log there really isn't anything useful in it:

I then run the Check Pattern debug against one of the same IP addresses, and it completes with no issues. I even did a fresh MID Server install to see if that was an issue, but get the same results.

Has anyone else ever run into issues like this where devices that have always been discovered suddenly can't?

[Tanaji Patil]

Check system logs if you find anything there. Sometimes some before insert/update BR restricts and then it fails identification phase. I believe this is causing your discovery failure.

Check if you get something in Discovery Patter Log (in left navigation).

Also click on discovery (in your screenshot) and click debug on the top right. See what you are getting there to debug further. I hope you mean the same by Check Pattern debug.

-Tanaji
Please mark response correct/helpful if applicable

[Marcel H_]

I’ve stepped through the pattern debug and everything completes successfully, but still has the same issues during an actual discovery scan. I’m going to dig into the system logs more to see if there is anything more descriptive in there that I can troubleshoot further.

[Ashutosh Munot1 · Accepted solution]

Hi,

Couple of other reason which i know are:

1) Duplicate relationships

https://hi.service-now.com/kb_view.do?sysparm_article=KB0725605

2) Some due to dependent CI.

https://hi.service-now.com/kb_view.do?sysparm_article=KB0715696

Check This knowledge article which helps.

https://community.servicenow.com/community?id=community_question&sys_id=0937a0281baa8c50ada243f6fe4b...

Thanks,
Ashutosh

[Marcel H_]

Thanks for the reply, I did uncover some duplicate relationships, and some that were missing altogether. Once I corrected those it's at least discovering the devices again, though I still get some credential errors (which I just need to find the group responsible for the server and get credentials).

I'm still getting some other errors that I I'm not sure about since they only occur during some scans, but not others:

Sensor error when processing Windows - Storage 2008 - WMI: No sensors defined

Sensor error when processing Windows - Storage 2008 - PS: No sensors defined

Sensor error when processing Windows - Storage 2012 - PS: No sensors defined

Sensor error when processing Windows - Storage 2012 - WMI: No sensors defined

Sensor error when processing Windows - Hardware Information: No sensors defined

Sensor error when processing Windows - Active Processes: No sensors defined

Sensor error when processing Windows - Powershell: No sensors defined

Sensor error when processing Windows - Active Connections: No sensors defined

Sensor error when processing Windows - Network: No sensors defined

I've checked the probe "Windows - Storage 2008" which includes the PS and WMI probes, and has the "Windows - Storage 2008" sensor defined, so not sure why it's failing on some scans but not all scans.