This article describes how to verify WMI settings on a system being monitored.
WARNING: This procedure requires the modification or creation of a registry key. Changing the registry can have adverse effects on your computer and may result in an unbootable system. Consider backing up your registry before making these changes.
- As remote WMI connections use RPC, the RPC Service must be enabled and started on the remote system.
- Log in to the remote system.
- Open the Windows Services list on that system.
- Verify that the Remote Procedure Call (RPC) service is enabled and started.
- As WMI also uses DCOM to communicate with the remote system, it must be enabled and configured correctly on the remote system.
- Log in to the target server with an administrator account.
- Verify that the user account you want to use to monitor resources over WMI has local access and remote access.
- Verify that the user account you want to use to Monitor resources over WMI has local launch, remote launch, local activation, and remote activation.
- Verify WMI Security to ensure that the account used by the ipMonitor credential can access the CIMV2 namespace. The user account you want to use to access this computer should be granted the following permissions:
- Enable Account
- Remote Enable
Note: If you are monitoring a target in a workgroup, you need to disable remote User Account Control (UAC). This is not recommended, but it is necessary when monitoring a workgroup computer. Disabling remote user account control does not disable local user account control functionality. Refer to Disable Remote User Account Control for Workgroups.
- If the target computer has Windows Firewall enabled, it must have a Remote WMI exception to allow remote WMI traffic through (Connecting to WMI Remotely with VBScript (© 2017 Microsoft, available at https://msdn.microsoft.com/, obtained on February 15, 2017)) . To add this exception:
- At a command prompt, enter
netsh firewall set service RemoteAdmin enable