Best way to identify all devices that fail to classify

[Gregory Gribben]

 I was wondering if there is an effective way to view devices that have failed to be discovered and classified. Looking at the discovery status of the scheduled jobs. The devices tab shows the majority of the devices failed with active couldn't classify. However, I have seen that the IP addresses do not seem to be deduplicated if the shazzam probe identified several open ports, such as Windows - Classfiy and VMWare - vCenter. My goal is to identity the devices that are not being discovered and address the issues that are preventing them from being discovered. 

[Gregory Gribben · Accepted solution]

After doing some digging, you can access the overall discovery device history here and then filter on couldn't classify. "https:// YOUR_INSTANCE .service-now.com/discovery_device_history_list.do?sysparm_query=GOTOlast_stateLIKEcouldn%27t%20classify%5EGROUPBYsource&sysparm_first_row=1&sysparm_view="

---

[doug_schulze]

Ive always just been a fan of building reports..

[Gregory Gribben]

The report is definitely a much cleaner way to view this thank you much for that. One question, regarding the filter you have specified on the Unclassified CI report. Are you able to explain the reasoning behind

Message contains Name Of

I attempted to use "Message contains name of" and I do not have any results returned.

I ended up filtering on Message contains Couldn't Classify"

[doug_schulze]

that was for devices that had snmp responsive but didnt meet any classifiers, such as a appliance of some sort that you may have wanted to create a new one for.