Foglight Agent Manager 7.3.0 - Foglight Agent Manager Guide

Granting access to dllhost.exe when Windows Firewall is enabled

When an agent connects to a monitored Windows host from a UNIX machine, and the Windows firewall is enabled, access to dllhost.exe must be allowed through the firewall.

To grant access to dllhost.exe:

Issue the following command on the command-line of the monitored Windows host:

netsh firewall add allowedprogram program=%windir%\system32\dllhost.exe name=Dllhost

Ensure that Windows UAC is disabled. See Disabling UAC for details.

Restart the monitored host.

Enabling agents to connect locally on Windows

When a WMI agent connects to the same machine it is running on (that is, localhost) using credentials that explicitly specify a user other than the currently logged on user, you must make certain registry changes to allow the required COM services to run.

To allow the agent to connect locally on Windows®:

Enable the Remote Registry Service.

Once the agent has successfully connected and the Agent Manager connection services have made the required changes, the Remote Registry Service can be disabled.

Ensure that the Server service is running.


	IMPORTANT: Normally, the Server service starts automatically. If it is stopped, or fails to start, it must be manually restarted before the Agent Manager can connect locally using credentials for a user other than the currently logged on user.

Releasing a locked MySQL process

The Agent Manager uses the wmiprvse.exe process to make use of WMI for remote Windows® monitoring. However, in some situations, this process can lock the MySQL process, mysqld.exe, preventing it from being uninstalled, deleted, moved, or updated.

To release a locked MySQL process:

•

Stop the wmiprvse.exe process.


	IMPORTANT: Stopping the wmiprvse.exe process does not affect the running state of the WMI service. The process starts again automatically when an application requires WMI.

Configuring Windows Remote Management (WinRM)

Windows Remote Management is the Microsoft® implementation of the Web Services Management Protocol (WSMAN) which is a Simple Object Access Protocol (SOAP) based protocol over HTTP/HTTPS and is used for system management. For more information, visit https://msdn.microsoft.com/en-us/library/aa384470%28v=vs.85%29.aspx.

WinRM has two authentication mechanisms that are used by the Agent Manager to establish connections:

•

Negotiate authentication is based on Kerberos authentication, involving tickets/keys obtained from a Key Distribution Center (KDC).

•

Basic authentication uses standard HTTP headers to communicate directly with the remote machine.

This section provides solutions for the following issues:

•

WinRM IPv6 connection support

•

About WinRM authentication and the Agent Manager

•

Configuring the target (monitored) system