Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > WMI queries and permissions that must exist for SAM component credentials to work

WMI queries and permissions that must exist for SAM component credentials to work

Table of contents

Updated June 15, 2017


This article provides information on which WMI queries or permissions must exist in the WMI hive for SAM component credentials to work, especially for services and processes.


All SAM versions


  1. Click Start and run WBEMTEST.
  2. Click Connect.
  3. Enter the IP address for Namespace \\<ip of target node>\root\cimm2\
    Note: For users with an AD account, enter the domain name\user name along with the corresponding password. For example, UN: Microsoft\JohnDoe.
  4. Click Connect > Query.
  5. Copy and paste the following queries one at a time:
    SELECT * FROM Win32_Service
    SELECT * FROM Win32_Process
    SELECT * FROM Win32_PerfRawData_PerfProc_Process

SAM must show results in the WMI hive to have any reasonable expectation to work.


Note: If you get an ACCESS DENIED message, it means the user name provided does not have rights to issue and query.

To figure out what permissions you need for WMI in order for SAM to pull data, try first using a Domain User account to ensure it works. Then compare the Domain Admin account to your Service Account. One at a time, give the Service Account the same roles, then take away roles one at a time until the credential breaks. Then you can identify which role is needed, e.g. Domain Admin, Administrator, Power User, Backup.

Last modified