vScope can use the WMI protocol to inventory Windows OS machines. This also includes Hyper-V machines and the VMM.
- When setting up a WMI service account for vScope, it is easiest to use permissions of a local administrator on the machine. Using the local Adminstrators group for example.
- If a domain user is to be used, we recommended using a group in Active Directory that is assigned access, and then adding the domain user to that group.
- In this guide we’re giving WMI access to an AD group, but the steps could technically be done for a domain or local user.
1. Create group in Active Directory
- Create a group called “WMI Access Users” in your Active Directory.
2. Ensure that the WMI service is running on the machine
- Open the command prompt and write “services.msc”
- Find the WMI service for your OS, right click and select properties.
- Set ‘Startup type’ to ‘Automatic’ and click “start”
- Close the window with “OK”
3. Add the AD group to the local default group Distributed COM Users
- Open lusrmgr.msc.
- Go to groups.
- Open “Distributed COM Users” and add the group “WMI Access Users”. Click apply.
4. Setting WMI permissions
- Write “wmimgmt.msc”in the command prompt
- Right click on “WMI Control” and select properties
- Click the ‘Security’-tab.
- Mark ‘Root’ in the tree structure and click on Security.
- Select “Advanced”.
- Click on “Add” and add the AD group by clicking on “Select a principal”.
- Under “Applies to:”, ensure it’s set to “This namespace and subnamespaces”.
- Check boxes for Execute Methods, Enable Account, Remote Enable och Read Security.
- When permissions are set as the image below. Click “OK”.
- Click “Apply”, and “OK” to close and save settings in all windows.
- Open “dcomcnfg”.
- Expand ‘Component Services’ –> ‘Computers’, and right-click on ‘My Computer’ and select ‘Properties’
- Select the “COM Security” tab and click “Edit Default…” for both “Access Permissions” and “Launch and Activation Permissions”.
- Access Permissions. Add “WMI Access Users” group and allow all permissions in the boxes below. Click OK.
- Launch and Activation Permission. Add “WMI Access Users” group and allow all permissions in the boxes below. Click OK.
- Click “Apply” and OK in all windows to close and save settings.
And that’s it. The AD group, and its users, will now have remote WMI access to the machine.
If WMI doesn’t work after the previous permission setup it may be because of local settings on the machine. Below are common configurations that may be needed.
Open firewalls for WMI traffic
Enter the following in the command prompt: “netsh advfirewall firewall set rule group=”windows management instrumentation (wmi)” new enable=yes”
Turn off UAC
If UAC is not turned off, vScope might have trouble accessing some information.
- Access “regedit”.
- Change the key “HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciessystemLocalAccountTokenFilterPolicy” to 1
- Close regedit
0 = Remote UAC access token filtering is enabled.
1 = Remote UAC is disabled.
Read more at: https://docs.microsoft.com/en-us/troubleshoot/windows-server/windows-security/user-account-control-and-remote-restriction
Enable RPC permissions on a single target machine:
- Run Microsoft Management Console on the target machine (Start|Run|mmc)
- Add “Group Policy Object Editor” snap-in (File|Add/Remove Snap-in…|Add…|Group Policy)
- Select the “Local Computer” Group Policy Object for which you want to enable RPC
- Navigate to: [Group Policy Object]|Computer Configuration|Administrative Templates|Network|Network Connections|Windows Firewall|Domain Profile ( for a Domain administered network – Standard Profile for a Workgroup network )
- Edit Setting: “Windows Firewall: Allow Remote Administration Exception”
- Set “Enabled”.
- Set “Allow unsolicited incoming messages from:” to “localsubnet” (without the quotes)
- Apply settings
- These settings will not generally take effect immediately. You can use Microsoft’s Group Policy Update Utility to force immediate updates.
WMI troubleshooting articles