立即与支持人员聊天
与支持团队交流

Foglight Agent Manager 5.9.4 - 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

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.

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

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.

a
On the desktop, right-click My Computer and navigate to Groups (My Computer > Manage > Configuration > Groups).
b
Double-click the Administrators group.
c
Add the required domain\user to the Administrators group.
d
Click Apply, and then click OK to close the dialog box.
2
Edit the Wbem Scripting Locator registry key.
a
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)
d
Click Other Users and Groups, and add the Local Administrators group.
e
Select the Replace Owner on subcontainers and objects check box.
f
Click Apply, and then click OK.
3
Close regedit.

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

Resolving Access Denied errors when connecting to Windows XP Professional

When attempting to monitor a Windows® XP Professional machine, the remote agent sometimes fails to connect with an Access Denied error message. This error can be caused by the Windows ForceGuest setting, which is enabled by default on machines that are not part of a domain. To resolve the issue, ensure that remote connections are not being coerced to log on as the guest account by following the procedure below.

1
In the Start menu, type run.
2
In the Run dialog box that appears, type secpol.msc and click OK.
The Local Security Policy editor appears.
3
Choose Local Policies > Security Options.
4
Select the entry: Network access: Sharing and security model for local accounts.
5
If this entry’s security setting is Guest only, right-click the entry and click Properties.
6
In the dialog box that appears, on the Local Security Setting tab, select Classic - local users authenticate as themselves from the list.
7

For more information, see step 5 in the following VMWare KB article:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2013

OS collection fails with a Local_Limit_Exceeded error

OS collection fails with a Local_Limit_Exceeded error

The agent uses Windows® authentication to Negotiate the monitored instance. In some cases, the negotiation can fail if there is a mismatch between the authentication types used by the client and the server.

The following symptoms indicate an authentication issue:

To resolve these issues, you may need to disable the NTLMv2 authentication.

1
Run regedit to edit the registry.
2
Locate the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
3
Locate the value named LMCompatibilityLevel, and change the DWORD value to 2 (send NTLM authentication only).
4
Close regedit and restart the machine.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级