Problem

Insight Discovery tool cannot scan or reach Windows OS hosts.

The following appears in the discovery.logs

Failed to connect durring to: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Diagnosis

Environment

• Any Insight Discovery version

Diagnostic Steps

• A scan is initiated either:

  • Manually running the available command: Discovery.exe

  • Scheduled scan by setting a scan Interval
• Discovery attempts to login to each hosts using the saved credentials but it will be unsuccessful for some Windows OS hosts

Cause

There could be multiples causes:

1. The credentials given to the Discovery tool must be sufficient to allow Discovery to perform the local scan
2. If it is a scheduled scan, SYSTEM needs DCOM Permissions
3. There is a WMI connectivity issue between the target and Discovery hosts

Resolution

Verify the credentials given to the Discovery tool

You need to verify the user and password given to the Discovery tool are valid for to connect to the Windows host

Grant DCOM Permissions to SYSTEM user

1. On the Host where the Discovery tool is installed, Win+R / Run : wmimgmt.msc
2. Open the WMI Control (Local) Properties > Security Tab
3. Expand Root, and select CIMV2
4. Click Security
   1. If not there - add the SYSTEM User, and make sure this user has:
      1. Execute Methods
      2. Provider Write
      3. Enable Account
         
         

Test WMI connectivity with wbemtest.exe tool

WBEMTEST is available on any Windows system and it is a graphical utility that you can use to test connectivity to remote systems.

1. On the host where the Discovery tool is installed, go to Start and type "WBEMTEST.exe" into the search or run box.
2. Click Connect... and enter:
   1. The server name or IP of the the target host on Namespace: \\<targetIpAddressHere>\root\cimv2
   2. And user credentials (same ones as you use on Discovery Credentials tab) including any Windows domain, for example "domain\username".
   3. Click Connect
      
   4. If connection fails, please reach out your System Administrator to troubleshoot VMI connectivity issues between the target host and Discovery host. Ensure you grant DCOM Permissions to SYSTEM user if it is a scheduled scan
   5. If connection succeed, run a query
      • On the same tool screen, click on Query

      • Run the following query: 
        

        SELECT * FROM Win32_Processor

        

      • If succeed, Discovery should be able to scan the target Windows host successfully