The section below describes basic options for running the Agent Manager.
This section covers the following key areas:
The Agent Manager should be installed in a directory that is local to the system. It should also run using a local account, not a network or domain account. This should also include a local user home directory. Because the Agent Manager monitors and detects problems such as network and disk failures, having the Agent Manager installed in a local directory and running it as a local user makes the Agent Manager more resistant to failures in those services and better able to detect and report those failures.
Otherwise, having the Agent Manager installed on a network drive, could cause the Agent Manager to lock itself when the network drive fails, preventing this failure from being reported.
In a default installation, the Agent Manager is installed as a Windows service or a Unix daemon, this process starts immediately after the installation. You can override this default behavior by using the –no-start-on-exit option.
To start the Agent Manager:
To restart the Agent Manager:
To stop the Agent Manager:
To run the Agent Manager as a daemon on UNIX:
To run the Agent Manager as a Windows service:
The Agent Manager has different process names on different operating systems.
The Agent Manager determines a unique ID for each system on which it runs, and includes that ID with the data submission from each agent. On some Linux systems, however, the Agent Manager may be unable to determine a unique system ID. In such cases, the Agent Manager does not return any system ID in the data submission.