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
- Open the command prompt an a machine with suspected WMI problems. Make sure you have administrator privileges
- Run the command
- If the repository is OK the response should be
WMI repository is consistent
- After this, run WMI Diagnosis Utility from Microsoft on one of the machines having WMI trouble. Download here: https://www.microsoft.com/en-us/download/details.aspx?id=7684
- 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:
- 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