3 |
Run the Agent Manager from the command-line with the --configure option: |
IMPORTANT: On Windows 7 and Vista, it is recommended to run the command fglam ‑‑configure from an administrator version of cmd.exe or PowerShell (not just logged in as administrator) if you installed the Agent Manager as administrator. |
4 |
5 |
6 |
If Quest Support instructs you to reset the unique ID assigned to this Agent Manager instance, select the Yes, reset this client’s ID check box. Otherwise, ensure that the check box is clear. |
7 |
Click Next. |
8 |
Continue to navigate through the remaining steps and set the desired options, as prompted. Use the Next and Previous buttons to navigate through the steps. The remaining steps are the same as in the Agent Manager installer interface. For more information, see Installing the Agent Manager using the installer interface. |
9 |
10 |
You can check the value of the property fips.approved.mode.enabled in <fglam_home>/state/default/config/client.config file to see in which mode this Agent Manager is running. If the property is True, it means this Agent Manager is FIPS-compliant, and vice versa. In case the property is not found, it means this Agent Manager is not FIPS-compliant as well.
NOTE: Do NOT change the value of fips.approved.mode.enabled property, otherwise the Agent Manager won’t work with the Foglight Management Server if their FIPS-compliant modes are inconsistent. |
2 |
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/bin directory. |
4 |
Review the information provided in this step. If you do not want to make any changes to the auth-token, press Enter. |
5 |
Review the information in the Introduction step, and press Enter. |
6 |
In the Host Display Name step, set the desired options, if applicable, and press Enter. |
7 |
If Quest Support instructs you to reset the unique ID assigned to this Agent Manager instance, type Y at the prompt and press Enter. |
8 |
9 |
When you navigate to the Summary step, press Enter. |
10 |
Restart the Agent Manager instance in the desired mode. See Starting or stopping the Agent Manager process for information about the different modes in which you can run the Agent Manager. |
You can set this option either while installing the Agent Manager, or after installation. See Installing the Agent Manager , or Configuring the Agent Manager , for more information about configuring the Agent Manager to connect to the Management Server using HTTPS.
By default, Foglight® ships with a self-signed SSL certificate. If you configure the Management Server to use an SSL certificate signed by a third-party Certificate Authority (CA), whose root certificate is already included in the JRE used by the Agent Manager, you do not need to add a new CA to the Agent Manager keystore. Instead, ensure that the Agent Manager connects to the Management Server using HTTPS.
You must add a new CA to the JRE used by the Agent Manager if:
1 |
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/jre/<jre_version>/jre/bin directory. |
1 |
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/bin directory. |
a |
6 |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center