Chat now with support
Chat with Support

Foglight Agent Manager 5.9.1 - Foglight Agent Manager Guide

Configuring the embedded Agent Manager Installing external Agent Managers
Understanding how the Agent Manager communicates with the Management Server Deploying the Agent Manager cartridge Downloading the Agent Manager installer Installing the Agent Manager Starting or stopping the Agent Manager process Frequently asked questions
Configuring the Agent Manager Advanced system configuration and troubleshooting
Configuring Windows Management Instrumentation (WMI) Configuring Windows Remote Management (WinRM) UNIX- and Linux-specific configuration
Monitoring the Agent Manager performance Deploying the Agent Manager to large-scale environments

Known WMI issues in Windows Server 2008

Microsoft® has identified a number of known issues with WMI services in Windows® Server 2008. The following issues may occur:

In SQL Server 2008, the perfmon counters do not appear under WMI because they do not exist.
Using the same OS credentials as the agent uses, run perfmon /wmi on the monitored host.
In SQL Server 2008 on Windows Server 2008, if the perfmon counters are missing from WMI, install the following hotfix:

Tuning WMI connections

The following parameters can be used to fine tune the Windows Management Instrumentation (WMI) connections made by Foglight agents. You can set these parameters for Foglight Agent Manager either in the baseline.jvmargs.config file as vmparameter options, or specify them directly as jvm options when starting up Foglight Agent Manager via command line. The values used for these parameters vary from environment to environment and so should be used as reference only.

Modifying registry key ownership on Windows Server 2008 R2

Configuring the agent to connect to the remote Windows® Management Instrumentation (WMI) and WinShell components on Windows Server 2008 R2 systems requires certain modifications to the registry keys. In some situations, these registry keys may be owned by TrustedInstaller instead of the Administrators group, which prevents modifications from being made even by Administrator accounts.

On the Permissions dialog box, click Advanced.
On the Advanced Security Settings dialog box, open the Owner tab.
In the Change owner to list, select the Administrators group.

Configuring registry settings for Windows Server 2008 R2 and Windows 7

In order to allow the agent to connect to the remote Windows® Management Instrumentation (WMI) components on Windows Server 2008 R2 or Windows 7 systems, special registry settings are required.

On the desktop, right-click My Computer and navigate to Groups (My Computer > Manage > Configuration > Groups).
Double-click the Administrators group.
Add the required domain\user to the Administrators group.
Click Apply, and then click OK to close the dialog box.
Edit the Wbem Scripting Locator registry key.
Run regedit.
{72C24DD5-D70A-438B-8A42-98424B88AFB8} (Windows Script Host Shell Object)
{76A64158-CB41-11d1-8B02-00600806D9B6} (WBEM Scripting Locator)
{0D43FE01-F093-11CF-8940-00A0C9054228} (Windows Script FileSystem Object)
Click Other Users and Groups, and add the Local Administrators group.
Select the Replace Owner on subcontainers and objects check box.
Click Apply, and then click OK.
Close regedit.

If configuring the registry does not solve the connection issue, you may need to disable Windows User Account Control (UAC).

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating