Category Archives : Troubleshooting RSS feed for this section

Windows Defender – Suspicious command launched from remote location

Background To inventory Windows operating systems, vScope uses WMI or WinRM (depending on your preferences). This is called a Discovery. Both WMI and WinRM run scripts from the vScope server to fetch ...

Why are MECM (SCCM) machines missing in vScope?

To be able to match a machine with itself from various data sources, vScope needs a unique identifier. Machines from MECM only show up in the All Machines table and gets a properties page if vScope ca...

Weird symbols when opening CSV export in Microsoft Excel

vScope’s CSV exports are encoded in UTF-8. If you see wierd symbols when opening it in Excel, it’s probably caused by the settings in Excel. Follow these steps to open the export correctly...

WMI – Warning message “job aborted due to overdue”

The warning message “Job aborted due to overdue” means that vScope’s discovery probe for WMI has timed out on the target machine, TroubleshootingThere might be some issues on the tar...

Common discovery errors

Is your error not listed below or want a further explanation? Contact support@infrasightlabs.com and they’ll help you out. Common WMI errors Common MS SQL errors Common HTTP errors Add ports to ...