WMI Metrics Reference Tables

WMI Metrics Reference Tables

Windows Server Monitor - WMI Metrics Reference Tables

This document lists the WMI namespaces, classes, and WQL queries used by AppManager Windows Server Monitor scripts in WMI mode. These reference tables can be used for troubleshooting WMI-related issues, validating WMI queries using WBEMTEST, verifying namespace and class availability, and identifying the corresponding script associated with each monitored metric or configuration attribute.


Table 1: Performance Metrics (WMI Mode)

Metric CategoryVBS ScriptWMI NamespaceWMI ClassWQL Query
CPU Utilizationcpu.vbsRoot\CIMV2Win32_PerfRawData_Counters_ProcessorInformationSelect * from Win32_PerfRawData_Counters_ProcessorInformation where Name='_Total'
Processor Queue Lengthcpu.vbsRoot\CIMV2Win32_PerfRawData_PerfOS_SystemSelect * from Win32_PerfRawData_PerfOS_System
Memory Utilizationmemory.vbsRoot\CIMV2Win32_OperatingSystemSelect * from Win32_OperatingSystem
Disk Utilization (Local)disk.vbsRoot\CIMV2Win32_LogicalDiskSelect * from Win32_LogicalDisk where DriveType=3
Disk Utilization (Network Mapped)disk.vbsRoot\CIMV2Win32_MappedLogicalDiskSelect * from Win32_MappedLogicalDisk
Disk Utilization (Mount Points)disk.vbsRoot\CIMV2Win32_Volume, Win32_MountPointSELECT * FROM Win32_Volume WHERE DriveType=3 AND DriveLetter IS NULL
Disk I/O Statsdiskio.vbsRoot\CIMV2Win32_PerfRawData_PerfDisk_PhysicalDiskSelect * from Win32_PerfRawData_PerfDisk_PhysicalDisk Where Name!='_Total'
Paging Utilizationpaging.vbsRoot\CIMV2Win32_PerfFormattedData_PerfOS_MemorySelect * from Win32_PerfFormattedData_PerfOS_Memory
Servicesservices.vbsRoot\CIMV2Win32_ServiceSelect * from Win32_Service
Processesprocess.vbsRoot\CIMV2Win32_ProcessSelect * from Win32_Process
System Uptimeuptime.vbsRoot\CIMV2Win32_OperatingSystemSelect * from Win32_OperatingSystem
Network AdapterNetworkAdapter.vbsRoot\CIMV2Win32_NetworkAdapterSelect * FROM Win32_NetworkAdapter where PhysicalAdapter='True'
Event Logsevent.vbsRoot\CIMV2Win32_NTLogEventDynamic query with time filters
TCP Connection StatsTcpConnectionStats.vbsRoot\CIMV2Win32_PerfFormattedData_Tcpip_TCPv4select ConnectionsActive, ConnectionsEstablished, ConnectionFailures, ConnectionsPassive, ConnectionsReset from Win32_PerfFormattedData_Tcpip_TCPv4
Firewall Profilefirewall.vbsRoot\standardcimv2MSFT_NetFirewallProfileSelect * from MSFT_NetFirewallProfile
Scheduled TasksScheduledTasks.vbsRoot\CIMV2, Root\Microsoft\Windows\TaskSchedulerWin32_LocalTime, MSFT_ScheduledTaskSELECT * FROM Win32_LocalTime; Select TaskPath From MSFT_ScheduledTask

Table 2: Configuration Metrics (WMI Mode)

Configuration CategoryVBS ScriptWMI NamespaceWMI ClassWQL Query
System Information - Hostname, Manufacturer, Model, Domainconf-sys-info.vbsRoot\CIMV2Win32_ComputerSystemSelect * from Win32_ComputerSystem
System Information - BIOS Version, Serial Numberconf-sys-info.vbsRoot\CIMV2Win32_BIOSSelect Version,SerialNumber from Win32_BIOS
System Information - CPU Core Countconf-sys-info.vbsRoot\CIMV2Win32_ProcessorSelect NumberOfCores from Win32_Processor
OS Information - Name, Version, Build, Install Date, Registered User, Windows Directory, Product IDconf-os-info.vbsRoot\CIMV2Win32_OperatingSystemSelect * from Win32_OperatingSystem
Memory Configuration - Total Physical, Available Physical, Total Virtual, Available Virtualconf-mem-info.vbsRoot\CIMV2Win32_OperatingSystemSelect * from Win32_OperatingSystem
Processor Configuration - Name, Caption, Manufacturer, Speed, Cache Sizeconf-proc-info.vbsRoot\CIMV2Win32_ProcessorSelect * from Win32_Processor
Network Adapter Configuration - IP Address, MTU, Type, MAC Address, Manufacturer, Statusconf-net-info.vbsRoot\CIMV2Win32_NetworkAdapterConfiguration, Win32_NetworkAdapterSELECT * FROM Win32_NetworkAdapterConfiguration where IPEnabled=True
Printer Configuration - Name, Server, Type, Default, Status, Locationconf-prnt-info.vbsRoot\CIMV2Win32_PrinterSelect * From Win32_Printer
Notes
Note:
  • All queries listed above are executed through WMI mode in AppManager Windows Server Monitor.

  • Namespace availability and WMI class registration may vary based on Windows OS version and installed server roles/features.

  • Certain application-specific namespaces (for example: Task Scheduler, Firewall, Cluster services) may require additional WMI provider registration or elevated permissions.

  • If a query fails, validate the namespace, class, and WQL query using the WBEMTEST tool. By referring the steps under the section "Checking connectivity with WMI Tester" for instructions on using the wbemtest tool


                    New to ADSelfService Plus?

                      • Related Articles

                      • WMI Error Troubleshooting Guide

                        Overview This Knowledge Base provides troubleshooting guidance for commonly encountered Windows Management Instrumentation (WMI) errors that may occur while adding a Windows monitor or collecting metrics through WMI mode in Applications Manager. WMI ...
                      • Configuring non-admin user account for WMI monitoring

                        By default, Windows allows only members of the Administrators or Domain Admin groups to read WMI class information. However, you can configure a regular user to access WMI information by performing the following steps on the server that needs to be ...
                      • Setting WMI access through Active Directory and Group Policy Object for non-admin user

                        In our case, we run Active Directory on Windows 2008 R2 and we want to scan the target machine which is Windows 2012 R2 machine. Our domain is called “APMCLU” and we name our dedicated WMI user-account “wmiuser”. First – Setting done from Active ...
                      • Unable to Retrieve Data Through WMI Mode

                        Overview This article provides troubleshooting steps to identify and resolve data collection failures for Windows monitors configured in WMI mode. If one or more metrics are not being collected, the steps in this article will help determine whether ...
                      • WMI/RPC Communication Errors

                        Applicable WMI Error Codes 0x800706BE – The remote procedure call failed 0x80010002 – Call was canceled by the message filter Overview These errors occur when Applications Manager is unable to establish or maintain WMI/RPC communication with the ...