Discovery Issue

[ServiceNowEmp]

I ping and WMI query a Windows server manually from the MID Server, but ServiceNow Discovery fails at Classification. How to troubleshoot?

[Ravi Gaurav · Accepted solution]

Hi @ServiceNowEmp 

• Verify MID Server Configuration:

  • Ensure the MID Server has the “Discovery” and “WMI” capabilities.

  • Check if the correct credentials (admin rights, DCOM, and firewall) are assigned in the Credential Affinity.

• Check IP Range and Schedule:

  • Confirm that the IP address of the server falls within an active discovery schedule’s range.

• Validate Probe and Sensor Flow:

  • Review ECC Queue for the probes (WMI Class Probe) and responses (WMI Class Sensor).

  • If probes are sent but no responses are processed, issue could be with sensor logic or the credential used.

• Run Discovery Debug:

  • Use the “Discovery Status” page → “Logs” tab → enable “Debug” mode to trace the pattern execution.

• Check Classifier and Pattern Configuration:

  • The failure at “Classification” often means the classifier pattern didn’t match.

  • Go to Discovery Patterns → Classifiers, check if your OS or CI type classifier is active and correct.

  • Run the Classifier Test tool to simulate matching.

• CMDB Identification Rule:

  • Misconfigured identification rules can cause discovery to fail or skip creation. Ensure the cmdb_ci_computer rule uses serial_number or name properly.

[Ravi Gaurav · Accepted solution]

Hi @ServiceNowEmp 

• Verify MID Server Configuration:

  • Ensure the MID Server has the “Discovery” and “WMI” capabilities.

  • Check if the correct credentials (admin rights, DCOM, and firewall) are assigned in the Credential Affinity.

• Check IP Range and Schedule:

  • Confirm that the IP address of the server falls within an active discovery schedule’s range.

• Validate Probe and Sensor Flow:

  • Review ECC Queue for the probes (WMI Class Probe) and responses (WMI Class Sensor).

  • If probes are sent but no responses are processed, issue could be with sensor logic or the credential used.

• Run Discovery Debug:

  • Use the “Discovery Status” page → “Logs” tab → enable “Debug” mode to trace the pattern execution.

• Check Classifier and Pattern Configuration:

  • The failure at “Classification” often means the classifier pattern didn’t match.

  • Go to Discovery Patterns → Classifiers, check if your OS or CI type classifier is active and correct.

  • Run the Classifier Test tool to simulate matching.

• CMDB Identification Rule:

  • Misconfigured identification rules can cause discovery to fail or skip creation. Ensure the cmdb_ci_computer rule uses serial_number or name properly.

[Ravi Gaurav · Accepted solution]

Hi @ServiceNowEmp 

check this "https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0535236"