836 views

Description

Mostly commonly encountered errors with WMI Service while discovering Windows Host and basic cross-checks to troubleshoot.

Errors Similar to -: "Connection failed to WMI service. Error: Permission denied".

Release or Environment

Madrid3 and later Versions

Cause

With new Windows Discovery method was implemented which uses PowerShell and the admin$ share folder on remote targets and customer who wants to revert back to legacy method and encounter similar issues. Kindly refer below article as well if you encounter issues even after this basic troubleshooting as well.

Resolution

 

  1. Login to the MID Server with the Credentials used for discovering the <TargetMachine> and Click START and then select 'RUN' and enter WBEMTEST.EXE

 

 

 

  1. From the WBEMTEST utility, choose the CONNECT button and enter “\\<TargetIP>\root\cimv2” in the Namespace box.
  2. Click the CONNECT button to connect to the namespace. [Do not enter any credentials in the window]

 

 

  1.  At the parent screen, click the QUERY button and then enter “SELECT * FROM WIN32_PROCESSOR” in the Enter Query box.

 

  1. If the Issue still persists with "WMI Access denied” error", then follow the below steps to Enable Remote WMI Access for a Domain User Account.

 

  1. Considering that this user account is already a member of the “Domain Users” group, you will have to allow remote WMI access by Click START and then select 'RUN' and enter 'Compmgmt.msc' or by launching "Server Manger" with Run as 'Administrator.

 

  1. You need to add the user account to the local group named “Performance Log Users”:

  1. Then allow a user to have access via WMI Control Properties:

 

    • Open the WMI Control console: Click Start, choose Run and type wmimgmt.msc, then click OK.
    • In the console tree, right-click WMI Control and then click Properties.
    • Click the Security tab.

 

 

  1. Select the “\Root\CIMV2” namespace to choose which user or group will have access, and then click on Security.

 

 

  1. In the Security dialog box, click Add.

 

  1. In the Select Users, Computers, or Groups dialog box, enter the name of the object (user or group) that you want to add, click OK and then choose Advanced.

 

 

  1. In the Advanced Security dialog box under Permissions, edit the permissions and check all 'Allow' boxes. Select Apply to “This namespace and subnamespaces”:

 

 

  1. Click OK all the way to close all the windows and perform a quick discovery to test the changes.

Additional Information

Useful Links:

  1. Windows Discovery on Madrid Patch 3 and later - known issues and workarounds
  2. Resolving an issue of denied access to a Windows Server
  3. Firewall blocking Discovery access to the Windows Server

Article Information

Last Updated:2020-02-13 23:41:33
Published:2020-02-07