You can manually deploy or upgrade the KACE Agent on Linux devices as needed.
◦ |
Use the KACE_HOST and KACE_TOKEN environment variables to specify the appliance host name and agent token before you run the installation file, or: |
◦ |
Manually change the installation file name using the following syntax: <agent_installation_filename>_<appliance_hostname>+<agent_token>.<extension> |
3. |
◦ |
/opt/quest/kace/bin/ where the Agent executable files are installed. |
◦ |
/var/quest/kace/ where the Agent configuration, logs, and other data is stored. |
The device information appears in the appliance Inventory within a few minutes. See Managing applications on the Software page.
You can schedule the Agent to be deployed when users start or log in to Linux devices.
The export call must precede the call to the installer. For example: export KACE_SERVER=kace_sma_name rpm -Uvh kace_sma_agent-12345.i386.rpm
The system looks for the value of host in these locations in the order shown:
2. |
KACE_SERVER (environment variable) |
3. |
The amp.conf file |
If you want to register the agent with the appliance:
◦ |
Use the KACE_HOST and KACE_TOKEN environment variables to specify the appliance host name and agent token before you run the installation file, or: |
◦ |
Manually change the installation file name using the following syntax: <agent_installation_filename>_<appliance_hostname>+<agent_token>.<extension> |
You can obtain the agent token string from the Agent Token Detail page. For more details, see Registering KACE Agent with the appliance
You can manually upgrade the KACE Agent on Linux devices by running commands on the devices.
◦ |
Use the KACE_HOST and KACE_TOKEN environment variables to specify the appliance host name and agent token before you run the installation file, or: |
◦ |
Manually change the installation file name using the following syntax: <agent_installation_filename>_<appliance_hostname>+<agent_token>.<extension> |
3. |
You can manually deploy or upgrade the KACE Agent on Linux devices as needed.
◦ |
Use the KACE_HOST and KACE_TOKEN environment variables to specify the appliance host name and agent token before you run the installation file, or: |
◦ |
Manually change the installation file name using the following syntax: <agent_installation_filename>_<appliance_hostname>+<agent_token>.<extension> |
3. |
◦ |
/opt/quest/kace/bin/ where the Agent executable files are installed. |
◦ |
/var/quest/kace/ where the Agent configuration, logs, and other data is stored. |
The device information appears in the appliance Inventory within a few minutes. See Managing applications on the Software page.
You can schedule the Agent to be deployed when users start or log in to Linux devices.
The export call must precede the call to the installer. For example: export KACE_SERVER=kace_sma_name rpm -Uvh kace_sma_agent-12345.i386.rpm
The system looks for the value of host in these locations in the order shown:
2. |
KACE_SERVER (environment variable) |
3. |
The amp.conf file |
If you want to register the agent with the appliance:
◦ |
Use the KACE_HOST and KACE_TOKEN environment variables to specify the appliance host name and agent token before you run the installation file, or: |
◦ |
Manually change the installation file name using the following syntax: <agent_installation_filename>_<appliance_hostname>+<agent_token>.<extension> |
You can obtain the agent token string from the Agent Token Detail page. For more details, see Registering KACE Agent with the appliance
You can manually upgrade the KACE Agent on Linux devices by running commands on the devices.
◦ |
Use the KACE_HOST and KACE_TOKEN environment variables to specify the appliance host name and agent token before you run the installation file, or: |
◦ |
Manually change the installation file name using the following syntax: <agent_installation_filename>_<appliance_hostname>+<agent_token>.<extension> |
3. |
You can run commands on Agent-managed Linux devices to perform various Agent operations.
1. |
You can remove the Agent from Linux devices manually by running commands on the devices.
1. |
3. |
You can run a command on Linux devices to determine whether the Agent is running.
1. |
root 6100 0.0 3.9 3110640 20384 ? Ssl Mar03 0:00 /opt/quest/kace/bin/AMPAgent --daemon
1. |
The version number is displayed.
You can manually collect inventory on Linux devices by forcing inventory updates.
See Forcing inventory updates.
You can run commands on Agent-managed Linux devices to perform various Agent operations.
1. |
You can remove the Agent from Linux devices manually by running commands on the devices.
1. |
3. |
You can run a command on Linux devices to determine whether the Agent is running.
1. |
root 6100 0.0 3.9 3110640 20384 ? Ssl Mar03 0:00 /opt/quest/kace/bin/AMPAgent --daemon
1. |
The version number is displayed.
You can manually collect inventory on Linux devices by forcing inventory updates.
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center