No or partial discovery results from WMI

You are here:---No or partial discovery results from WMI

When discovery via WMI takes too long time, vScope will abort the session as a safety routine. The result is that no or only partial data is recorded from the machine.

Possible cause 1 – Damaged WMI repository

Investigate the WMI respository  in these steps

  1. Open the command prompt an a machine with suspected WMI problems. Make sure you have administrator privileges
    • Run the command winmgmt /verifyrepository
    • If the repository is OK the response should be WMI repository is consistent
  2. After this, run WMI Diagnosis Utility from Microsoft on one of the machines having WMI trouble. Download here:
    • Run WMIDiag.exe and choose where files should be extracted
    • Open the command prompt with administrator privileges
    • Go to the folder where WMIDiag.exe files were extracted and run the script cscript WMIDiag.vbs. The script will analyze WMI in different ways and report. This may take several minutes
    • Three files are created, names something like this:
      • %TEMP%/WMIDIAG-V2.2_WIN8.1_.CLI.RTM.64_MACHINE_2017.01.25_09.32.46.LOG
      • %TEMP%/WMIDIAG-V2.2_WIN8.1_.CLI.RTM.64_MACHINE_2017.01.25_09.32.46-REPORT.TXT
      • %TEMP%/WMIDIAG-V2.2_WIN8.1_.CLI.RTM.64_MACHINE_2017.01.25_09.32.46-STATISTICS.CSV
    • Analyze the files for possible problems. We offer help though our support if needed.

Possible cause 2 – Long latency

If a machine takes too long to respond, it could be due to long latency in the discovery. This may happen if the discovered machine is on a slow network connection, e.g. when being on a remote site. the solution could be to let a vScope proxy handle the discovery of the remote site. Read more