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 > How to run a CIM walk against a VMware ESX Server VM

How to run a CIM walk against a VMware ESX Server VM

Table of contents

Updated: October 23, 2017


This article describes how to run a Common Information Model (CIM) walk against a VMware ESX® Server virtual machine (VM).

When you install Server and Application Monitor (SAM), the installation includes the Hardware Health Tool. This tool allows you to run a CIM walk (gathering data using the CIM protocol) from VMware ESX Server VMs. The tool creates a Windows Management Instrumentation / Common Information Model (WMI/CIM) walk in a form of directory structure and CSV files with instance information.

The Hardware Health Tool includes the following syntax:

SolarWinds.APM.HardwareHealthTool Hostname/IP[:port] [-protocol Cim/wmi] [I-path path] [- namespace namespace(s)] [-user username]

You can access the tool from the following location:

Vol:\Program Files (x86)\SolarWinds\Orion\HardwareHealth\SolarWinds.HardwareHealthTool.exe


  • SAM 6.0 and later


  1. Log in to the Orion Polling Engine which is monitoring your ESX Server.
  2. Open a command prompt window.
  3. Change the directory to the SolarWinds Install folder.
    Volume:\Program Files (x86)\SolarWinds\Orion\HardwareHealth\
  4. Execute:
  5. Update the IP / path to the correct use for your scenario.
    For example:
    SolarWinds.HardwareHealthTool.exe –protocol cim –path C:\temp –user root
  6. Navigate to the patch in the c:\temp example.
  7. In the path, locate a folder called after the user name. For example: C:\temp\root
    In this folder are the files for each hardware component, as shown below.


Last modified