Chatta subito con l'assistenza
Chat con il supporto

Foglight Agent Manager 7.3.0 - Foglight Agent Manager Guide

Configuring the embedded Agent Manager Installing external Agent Managers 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

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.

To configure Windows Server 2008 R2 registry settings:
1
If necessary, add the required domain\user to the Administrators group.
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.
 
* 
IMPORTANT: There may be multiple instances of each key, especially for 64-bit versions of Windows Server 2008 R2 and Windows 7. Each instance must be updated.
a
Run regedit.
b
Search for all instances of the keys named:
{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)
There may be multiple instances of each key, especially for 64-bit versions of Windows Server 2008 R2 and Windows 7. Each instance must be updated.
c
For each key, right-click the key and navigate to the owner permissions (Permissions > Advanced > Owner).
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.
The security screen appears.
g
Select the Local Administrators group and grant full permissions.
 
* 
NOTE: An error indicating insufficient permissions may appear. To resolve, a user with the administrative account intended to use for profiling can change the ownership of the keys to that administrative account, and then set the permissions to Full on the appropriate registry keys.
3
Close regedit.

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

To disable Windows UAC:
•
Follow the instructions provided on the following website:
http://technet.microsoft.com/en-us/library/cc709691%28WS.10%29.aspx#BKMK_S3

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.

To disable ForceGuest for remote connections:
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
Click OK.
8
Restart the computer.

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:

•
NTLMv2 security is used for Windows authentication
•
Operating system collection fails
•
The agent log includes the following message:
WMIConnection - WMIConnection.An internal error occurred.
...
org.jinterop.dcom.common.JIException: An internal error occurred.
[0x8001FFFF]
...
Caused by: rpc.BindException: Unable to bind. (LOCAL_LIMIT_EXCEEDED)

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

To turn off 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.

Access to DCOM objects and registry is denied

When the agent attempts to access the Windows® registry and enter the Windows Management Instrumentation (WMI) component, the attempt can fail if the agent user does not have the required permissions.

The following symptoms indicate a permissions issue:

•
The database agent fails even when the user credentials are valid.
•
The agent log includes the following message:
The user account <username> has invalid login credentials.
•
The agent log includes the error WMIConnection.Access is denied and error code 0x00000005.
•
The agent OS verification fails on Windows Vista or Windows 7 installed with a non-English character set.
To enable agent verification:
1
Ensure that the following two registry keys exist on the monitored host, in HKEY_CLASSES_ROOT\CLSID\:
 
* 
IMPORTANT: The difference between these two keys is the bold character.
•
76A6415B-CB41-11d1-8B02-00600806D9B6
•
76a64158-cb41-11d1-8b02-00600806d9b6
 
* 
IMPORTANT: There may be multiple instances of each key, especially for 64-bit versions of Windows Server 2008 R2 and Windows 7. Each instance must be updated.
If one or both of these keys does not exist on the monitored host, export them from an machine (that is, running the same Windows OS) and import them to the monitored host.
2
Set permissions for the registry keys from Step 1.
 
* 
IMPORTANT: An error indicating insufficient permissions may appear. To resolve, a user with the administrative account intended to use for profiling can change the ownership of the keys to that administrative account, and then set the permissions to Full on the appropriate registry keys.
a
Log in to the target host with an account that has Administrator privileges.
b
Start regedit, and from the Edit menu, use Find to search for the following key: 76A6415B‑CB41‑11d1‑8B02‑00600806D9B6.
c
Right-click the Class ID, and click Permissions.
d
In the Permissions dialog box, click Advanced.
e
In the Advanced Security Settings dialog box, open the Owner tab.
f
On the Owner tab, in the Change owner to area, select the account with which you are currently logged in.
g
Click OK.
The Advanced Security Settings dialog box closes.
h
In the Permissions dialog box, select the Administrators group.
i
In the Permissions for Administrators area, in the Allow column, select the Full Control check box.
j
Click OK. The Permissions dialog box closes.
k
Repeat Step a through Step j for the second key: 76a64158‑cb41‑11d1‑8b02‑00600806d9b6
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione