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
Configuring the Agent Manager
Installing the Agent Manager using the installer interface
Installing the Agent Manager from the command line
Using the Agent Manager silent installer
Installing the Agent Manager as a Windows service
Starting or stopping the Agent Manager process
Frequently asked questions
How do I upgrade the Agent Manager?
How do I uninstall the Agent Manager?
Where can I find the Agent Manager installation log files?
Why does the message "Created system preferences directory in java.home" appear after I finish installing the Agent Manager on AIX?
Are the passwords that are stored in the configuration file, fglam.config.xml, encrypted?
How can I see what parameters are available for the silent installers?
Why are two URLs displayed for localhost when I search for HA peers?
I tested the connection between the Agent Manager and a Management Server, but the Management Server URL failed the connectivity test. Why did this happen?
When I try to install the Agent Manager using the installer interface on Solaris x86 VMware, it fails and a warning message related to fonts appears. Why does this occur?
Why does an AIX compatibility warning appear when I run the Agent Manager installer?
Operating system patches
Launching the Agent Manager installation interface
Configuring the Agent Manager to run in FIPS-compliant mode
Configuring the Agent Manager from the command line
Configuring the Agent Manager to use SSL certificates
Configuring an Agent Manager instance as a Concentrator
Advanced system configuration and troubleshooting
Configuring the concentrator
Configuring downstream Instances
Creating a secure connection with downstream instances
Excluding SSL ciphers from upstream or downstream Connections
Excluding Specific SSL Protocols from Downstream Connections
Configuring the Agent Manager to accept connections from the Management Server
Configuring the Agent Manager to execute commands on remote hosts
Configuring multiple Agent Manager instances
Controlling the polling rate
Configuring the Agent Manager to work in HA mode
Assigning Agent Managers to HA partitions
Adding cartridges to the HA deployment whitelist
About agent fail-over
About non-HA deployments
Negotiating Agent Manager resources at runtime
Configuring credentials
Configuring anti-virus exclusion settings
Troubleshooting
Configuring Windows Management Instrumentation (WMI)
Monitoring the Agent Manager performance
WMI IPv6 connection support
Windows Firewall interference
Minimum requirements for Windows Management Instrumentation
Configuring Windows Remote Management (WinRM)
Promoting remote users to administrators on local machines through the Domain Controller
Granting required permissions to individual remote users
WMI access violation and OS connectivity verification failure
WMI and Quota Violation error
Known WMI issues in Windows Server 2008
Tuning WMI connections
Modifying registry key ownership on Windows Server 2008 R2
Configuring registry settings for Windows Server 2008 R2 and Windows 7
Resolving Access Denied errors when connecting to Windows XP Professional
OS collection fails with a Local_Limit_Exceeded error
Access to DCOM objects and registry is denied
Configuring registry settings for WinShell access through DCOM
Permissions on registry keys to configure DCOM command shell connection
Enabling agents to connect from UNIX machines
Enabling agents to connect locally on Windows
Releasing a locked MySQL process
WinRM IPv6 connection support
About WinRM authentication and the Agent Manager
Configuring the target (monitored) system
Configuring the Agent Manager (monitoring) system
Generating a configuration file required for WinRM Negotiate authentication
Configuring command-shell connection settings
About WinRM connection ports
Troubleshooting
UNIX- and Linux-specific configuration
Agent Manager service can't start automatically when the operating system restarts
SSH IPv6 connection support
About supported remote monitoring protocols
Configuring the Agent Manager to run as a daemon
Configuring Agent Manager agent privileges
Using sudo to configure secure launcher permissions
Using setuid_launcher to configure secure launcher permissions
Using the HP patch checking tool
About Agent Manager installations on AIX
Preventing Agent Manager core dumps on Linux
Investigating Agent Manager diagnostics
Deploying the Agent Manager to large-scale environments
Using Agent Manager silent installer Parameters
Example: Deploying the Agent Manager to multiple UNIX hosts
Example: Deploying the Agent Manager to multiple Windows hosts
Next steps
How do I upgrade the Agent Manager?
Consult the Foglight Upgrade Guide for detailed upgrade instructions.
How do I uninstall the Agent Manager?
This section topic describes how to completely uninstall the Agent Manager and remove the init.d script used to run the Agent Manager as a daemon or the Foglight® Agent Manager Windows® service.
|
IMPORTANT: Stop the Agent Manager using the init.d script, then remove the init.d script before uninstalling the Agent Manager. |
|
1 |
Launch a command shell on the Agent Manager machine and navigate to <fglam_home>/state/default/. |
|
2 |
|
IMPORTANT: This script must be run as root. |
The setup script fglam-init-script-installer.sh removes the init.d script quest-fglam and all known symlinks to the quest-fglam script. See Installing the Agent Manager using the installer interface for the location from which it is removed.
|
1 |
Launch a Command Prompt window on the Agent Manager machine and navigate to the <fglam_home>\bin directory. |
|
IMPORTANT: On Windows 7 and Vista, you must issue the command to manually remove the Agent Manager as a Windows service using an administrator version of cmd.exe or PowerShell (not just logged in as administrator). |
|
2 |
Run the Agent Manager from the command-line with the --remove-service option: |
|
2 |
Delete the installation directory (referred to as <fglam_home> in this chapter section) and any state directories related to this installation. |
|
The workaround is to move or rename the file before you delete it. For example: |
Where can I find the Agent Manager installation log files?
The Agent Manager saves its log files in the <fglam_home>/state/<state_name>/logs directory.
In addition to the installation log file, Install*.log, that contains messages logged during the installation, the Agent Manager also provides the following log files:
|
• |
FglAM*.log contains messages logged during run-time. |
|
• |
quest-runner*.log contains messages logged by the external process runner. |
|
• |
quest-watchdog*.log contains information from the Agent Manager self-monitoring watchdog process. |
|
• |
auditor/SecurityAudit*.log contains information about agent activities needed for agent developers and Quest Support. |
Why does the message "Created system preferences directory in java.home" appear after I finish installing the Agent Manager on AIX?
This is a benign log message from JavaTM that appears when you finish installing the Agent Manager on AIX®. Java performs the action described the first time a specific user runs Java on a machine.