To remotely monitor a Windows® machine, some Foglight® agents require access to the WMI services, and specifically to the WMIConnectionService. This section outlines potential issues that may be encountered by agents attempting to access WMI, and provides solutions or workarounds.
In order to access WMI, the user that the monitoring agent connects as must have sufficient credentials. Any user included in the Administrator group on the monitored machine already has the required access levels. For more information, see Minimum requirements for Windows Management Instrumentation.
There are several OS and environment-specific issues that may arise when using a Foglight agent to monitor a Windows machine remotely. This section provides solutions for the following issues:
Starting with the Foglight Agent Manager version 5.9.1, the WMI connection with unique local IPv6 Address and link-local IPv6 Address is supported on the Agent Manager running on Windows, Linux, and Solaris.
Since the agent connects remotely (that is, from an external source) the Windows® Firewall can interfere with operations. In such cases, it is recommended that you initially try disabling the firewall to determine if that allows the agent to connect. When the agent can connect with the firewall disabled, re-enable it and open the following ports:
In order for the agent to have access to query WMI to collect OS and database metrics, the agent must have permission to access both DCOM and WMI. By default, any user in the Local Administrators group on the monitored host has the required permissions. Therefore, the best practice is to use a Local Administrator account on the monitored host as the agent OS user.
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center