Chatee ahora con Soporte
Chat con el soporte

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

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

Configuring registry settings for WinShell access through DCOM

Any WindowsShell connection made to a non-local host requires DCOM access to that machine, regardless of whether the user establishing the connection is a local or third-party user.

Therefore, agents that connect to Windows® machines using the Agent Manager’s WindowsShellService need to make the following specific registry changes to allow the connection.

To enable WindowsShellService access:
1
Ensure that the following two registry keys exist on the monitored host, in HKEY_CLASSES_ROOT\CLSID\:
•
72C24DD5-D70A-438B-8A42-98424B88AFB8
•
0D43FE01-F093-11CF-8940-00A0C9054228
 
* 
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 identical 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: 72C24DD5-D70A-438B-8A42-98424B88AFB8.
c
Right-click Class ID, and click Permissions.
d
In the Permissions dialog box that appears, 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, enable the Full Control check box.
j
Click OK.
The Permissions dialog box closes.
k
Repeat Step a through Step j for the second key:
0D43FE01-F093-11CF-8940-00A0C9054228.

Enabling agents to connect from UNIX machines

When an agent connects to a monitored Windows® host from a UNIX® machine, you must make certain registry changes in order to allow the required COM services to run.

To allow the agent to connect from a UNIX machine to a monitored Windows host:
1
Enable the Remote Registry Service.
Once the agent has successfully connected from a UNIX machine and the Agent Manager connection services have made the required changes, the Remote Registry Service can be disabled.
2
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 from a UNIX machine.

Disabling UAC

Disabling UAC

When an agent connects to a monitored Windows host from a UNIX machine, user access control (UAC) must also be disabled in order for WMI connections to succeed.

This requirement affects: Windows Vista, Windows Server 2008, and Windows 7.

To turn off UAC on Windows 7:
•
Navigate to Control Panel > User Accounts and Family Safety > User Accounts > Change User Account Control Settings, and change the setting to Never Notify.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación