Windows Monitoring - FAQ

Windows Monitoring - FAQ

This Knowledge Base article provides answers to frequently asked questions about Windows Server monitoring using WMI mode. The articles are organized by the monitoring lifecycle to help you quickly identify the relevant troubleshooting guide.

Prerequisites

  1. Verify WMI Connectivity 

    1. Use this article to validate basic WMI connectivity between the Applications Manager server and the target Windows server using WBEMTEST and WMI namespaces.

  2. Configuring Non-Admin User Account for WMI Monitoring

    1. Refer to this article for steps to configure a non-administrator user account with the required permissions for Windows monitoring using WMI mode in Applications Manager.

  3. Setting WMI Access Through Active Directory and Group Policy Object for Non-Admin User

    1. Use this article to configure WMI access permissions for non-admin domain users using Active Directory and Group Policy Objects (GPO).

  4. Script, Namespace, and WMI Class Used

    1. This article provides the list of VBS scripts, WMI namespaces, WMI classes, and WQL queries used by the Windows Server Monitor in WMI mode.

Monitor Addition Issues

  1. "Authentication Failed or Access denied"

    1. Refer to this article when Applications Manager reports authentication failure or access denied errors while adding Windows servers using WMI mode.

  2. "The RPC server is unavailable"

    1. Use this article to troubleshoot RPC communication issues, firewall restrictions, DCOM configuration problems, and WMI connectivity failures during monitor addition.

  3. WMI Error Troubleshooting

    1. Refer to this article for troubleshooting steps corresponding to commonly reported WMI error codes such as Invalid Class, Invalid Namespace, RPC failure, and other WMI query errors that may prevent monitor addition.

  4. Reconstruct / Rebuild WMI Class

    1. Refer to this article to rebuild or reconstruct corrupted WMI classes and re-register WMI components when monitor addition fails due to invalid class or namespace errors.

Data Collection Issues

  1. Unable to retrieve data - WMI Mode

    1. Use this article to troubleshoot Windows monitor data collection failures caused by WMI issues, permission restrictions, missing metrics, or script execution problems.

  2. Script execution is timing out

    1. Use this article to troubleshoot slow Windows monitor data collection, WMI query delays, and script timeout issues during monitoring.

  3. Enable performance counters through registry

    1. Use this article when WMI performance counter classes such as Win32_PerfRawData_* return an invalid class or no data through WBEMTEST.

  4. WMI error troubleshooting

    1. Refer to this article for troubleshooting steps corresponding to commonly reported WMI error codes such as Invalid Class, Invalid Namespace, RPC failure, and other WMI query errors encountered during data collection.

  5. Reconstruct / Rebuild WMI classes

    1. Refer to this article to rebuild or reconstruct corrupted WMI classes and re-register WMI components when WMI queries fail with invalid class or namespace errors, preventing data collection.