Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > Verify the WMI settings on the system monitored by ipMonitor

Verify the WMI settings on the system monitored by ipMonitor

Table of contents

Updated October 10, 2018


This article describes how to verify WMI settings on a monitored system.


All ipMonitor versions


This procedure requires you to modify or create a registry key. SolarWinds strongly recommends that you back up your registry before making any edits to your system registry. You should only edit the registry if you are experienced and confident in doing so. Using a registry editor incorrectly can cause serious issues with your operating system, which could require you to reinstall your operating system to correct them. SolarWinds cannot guarantee resolutions to any damage resulting from making registry edits.

  1. Enable and start the RPC Service on the remote system.
    Remote Windows Management Instrumentation (WMI) connections use remote procedure calls (RPCs). 
    1. Log in to the remote system.
    2. Open the Windows Services list on that system.
    3. Verify that the Remote Procedure Call (RPC) service is enabled and started.
  2. Enable and configure DCOM to communicate with the remote system.
    WMI also uses the Distributed Component Object Model (DCOM) to communicate with the remote system. 
    1. Log in to the target server with an administrator account.
    2. Verify that the user account used to monitor resources over WMI has local access and remote access.
    3. Verify that the user account used to monitor resources over WMI has local launch, remote launch, local activation, and remote activation.
  3. 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

      If you are monitoring a target in a workgroup, you need to disable the 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 the local user account control functionality.​ 

  4. If the target computer has Windows Firewall enabled, it must have a Remote WMI exception to allow remote WMI traffic through. See Connecting to WMI Remotely with VBScript for details (© 2017 Microsoft, available at, obtained on February 15, 2017). 
    To add this exception:
    1. At a command prompt, enter:
      netsh firewall set service RemoteAdmin enable
    2. Enter:
Last modified