Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Verify WMI connectivity for Orion Platform products

Verify WMI connectivity for Orion Platform products

Updated November 7, 2017

Overview

This article provides information to ensure that the WMI service is installed and running and that you can successfully connect to WMI on a monitored node.

 

Environment

Products running on Orion Platform version 2017.1 and later, such as:

  • NPM 12.1 and later
  • SAM 6.4 and later

Detail

 

Ensure that WMI is installed

  1. Log on to the computer.
  2. Verify that the %Windir%\System32\WBEM directory exists and that it contains WinMgmt.exe

 

If the folder or EXE file does not exist, install the WMI core manually from http://www.microsoft.com (© 2018 Microsoft, available at https://www.microsoft.com, obtained on November 15, 2018). Follow troubleshooting instructions from Microsoft if you encounter issues with installing WMI.

Verify WMI connectivity

  1. Log on to the computer.
  2. Run services.msc.
  3. Verify that the following services are running and the startup type is set to Automatic.
    • DCOM Server Process Launcher
    • Remote Procedure Call (RPC)
    • RPC Endpoint Mapper
    • Windows Management Instrumentation
  4. Verify that the following service is running and the startup type is set to Manual.
    • WMI Performance Adapter
  5. Ensure that DCOM and networking are enabled

Run WBEMTEST

  1. Log on to the computer.
  2. Use WMI Control (or Wbemperm.exe: Start > Run... > "wbemtest") to confirm that you have security permissions to access WMI.
  3. Ensure that the accounts that are used by your management application are able to access WMI and the namespaces that are used by application.
  4. Review the logs that are available in the %Windir%\System32\wbem\logs directory.
  5. If a later version of WMI, DCOM, or the operating system (even a service pack) is available, apply that upgrade.

 

 

 

Last modified

Tags

Classifications

Public