Network Management

WMI Polling method does not show CPU, Memory and Interface Data in NPM

This article provides brief information and steps to resolve the issue when you are unable to poll specific information from specific nodes using the WMI polling method.

First published date

10/23/2018 10:21 PM

Last published date

12/17/2025 4:31 PM

Overview

You can use or follow this article whenever there is specific information like CPU, Memory, Interface, etc that is missing or not updating in Web Console. This article only applies to WMI polled nodes.

Product section

Network Performance Monitor

Cause

Corrupted Performance counters and WMI classes

Resolution

  1. Verify the results by running Wbemtest against the affected server using steps the Testing WMI Connectivity with WBEMTest
  2. Re-register PerfMonCounters and WMI classes:
    • RDP to the target server.
    • Run services.msc and stop the Windows Management Instrumentation (WMI) service.
    • Open a command prompt as an administrator and enter the following commands to rebuild the performance counters and WMI counter:
      • cd %windir%\system32\
      • lodctr /R (may need to run twice if it fails to run the first time)  
        cd %windir%\sysWOW64\
      • lodctr /R (may need to run twice if it fails to run the first time)  
      • winmgmt /resyncperf
      • wmiadap.exe /f
    • Start the Windows Management Instrumentation (WMI) service from services.msc.
          

After rebuilding the performance counters, test the result using WBemtest to see if the affected node responds to the WMI query.