Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM Documentation > SAM 6.6.1 Administrator Guide > Troubleshooting SAM > Troubleshooting a WMI Node issue in SAM

Troubleshooting a WMI Node issue in SAM

Table of contents
No headers

Updated: 3-9-2017

The following conditions must be met before you can proceed troubleshooting WMI nodes:

  • The node has successfully been added via WMI.
  • WMI is working properly on the remote server.
  • The Hardware Monitoring Agent software is installed on the remote server and running.

When ready, use Wbemtest.exe to troubleshoot WMI:

  1. Open wbemtest.exe, usually located at C:\Windows\System32\wbem\wbemtest.exe.
  2. Connect from the problematic node (either the SAM server or the additional poller server) to the remote server using wbemtest.exe.
  3. Click Connect. In the Namespace field enter:
    • For IBM and HP enter: \\RemoteServerIpAddress\root
    • For Dell enter: \\RemoteServerIpAddress\root\cimv2
  4. Enter administrator credentials and click Connect.
  5. Once connected, click Query from the main screen. The Query dialog appears.
  6. Enter: select * from __Namespace
  7. Replace Namespace with the following:
    • For HP nodes, replace Namespace with HPQ
    • For Dell nodes, replace Namespace with Dell
    • For IBM nodes, replace Namespace with IBMSD
  8. If the proper Namespace is found, connect to this Namespace.
    • \\RemoteServerIpAddress\root\IBMSD for IBM.
    • \\RemoteServerIpAddress\root\HPQ for HP.
    • \\RemoteServerIpAddress\root\cimv2\Dell for Dell.
  9. Run a Query for specific information: Select Manufacturer, Model, SerialNumber from CIM_Chassis
  10. If the test was not successful, re-install the platform or Hardware Monitoring Agent software on the remote server with the latest release.
Last modified