WMI classification probe timeout

[Jason Wang]

Have any of you run into issue that scheduled discovery job returns Windows - Classify probe with empty result. However, if you manually run discovery against these IP, then it will return information just fine.

[manikorada]

Jason,

Try to break your schedules and see if it fixes the issue

[Jason Wang · Accepted solution]

We resolved the discovery issues by pinpointing it to the max execution threads on the MID server being too high (125). Be reducing it to the near the recommended value (25) we were able to complete discovery on a subnet by subnet basis without any errors. We tested this thoroughly in DEV and TEST using a new MID server instances, and then our PROD1/2 instances. We did increase the CPUs and RAM on the VM instance to push the limit up to 40, but just let it go there. We found that discovering brand new CIs was extraordinarily taxing on the system, and that once we're done with this initial discovery in TEST, we won't have to do it again.

[Community Alums]

@Jason Wang 

In that case how do we achieve faster discovery ? It is recommended to increase thread count to complete duration in shorter duration. If we can not increase thread count, It will be difficult to complete discovery in time.

[Runjay Patel]

Check out this video, it will clear all your doubts and help you to understand Discovery queries in details.

Link: https://www.youtube.com/watch?v=30JbWVsusyE&t=10s&ab_channel=ServiceNowHelpdesk

It help you to understand below points.

• Discovery Overview
• Discovery prerequisite
• Understanding Discovery Phases in details
• Discovery credentials and IP Affinity
• Mid Server Management with Cluster and Load Balancer
• Schedule jobs
• Set up discovery from scratch to end
• Live implementation with real world data.
• Troubleshooting on various aspects
• Many more other issue related to mid server, CIs
• Cloud discovery
• Service Mapping

Please mark reply as Helpful/Correct, if applicable. Thanks!!