Navigate to: Setup > Discovery Status > Discovery Probe Results

The Discovery Probe Results Dashboard is a good starting point for use in analyzing probe results and addressing failures.

The Probe Results bar chart represents all probes that have been run during the previous 4 weeks.  Clicking on a section of the bar chart drills down into the data to display the probe results records that are represented.  For instance, if you would like to view all WMI probes that failed you can click on that section of the chart to drill down to the detailed records.

The Windows Errors gauge provides a breakdown of all WMI probes that failed organized by type.  Clicking on the probe name or count will drill down to the data records that represent those errors.  For instance, if you want to view the machines associated with windows probe failures due to firewall issues, click on Firewall or the error count to view the detailed records.

If you would like to view all probe failures at once, navigate to the Failures Only menu item to view this data.

Note: Double-click the Discovery Probe Results menu to reload the dashboard if you navigate away from the page.

Navigate to: Setup > Discovery Probe Results > Failures Only to view a listing of all individual scan probes that failed on a device.

This data view displays the results from each probe that is run on a device.  There are numerous probes that will run on each device, so there may be multiple records for a single device in this report.  However, if there are access errors (credentials, firewalls), you may only see one probe for a device since all subsequent probes will be canceled if a device cannot be reached.

The two primary reasons for discovery probe failures are:

1. Credentials - Scan cannot access machine because the credentials entered into Asset Vision® are invalid or missing. For Windows devices, user account should be a member of the local administrators groups and have remote WMI privileges.  All credentials errors will include the word "credentials".
2. Firewalls - Firewall settings on device prevent scanning.  For Windows devices, remote WMI connections may need to be enabled via the DMCONFIG tool and also enabled at the firewall level.  Both settings can be managed via Group Policy or manually.  Please see the deployment requirements for more information.  All firewall errors will include the words "WMI RPC Server is not running"

Other errors may occur, and you can reference the Details column for additional information.

The user can identify WMI Script Probe errors by creating a new filter line in the data view and matching Probe Type on WMI Script Probe.