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.
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.
See Forcing inventory updates.
You can manually deploy or upgrade the Agent on Mac devices as needed.
This section provides information for manually deploying the KACE Agent on Mac OS X devices. Additional options are described in Use shell scripts to deploy the KACE Agent.
◦ |
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. |
4. |
The installer creates the following directories on your device:
• |
/Library/Application Support/Quest/KACE/bin where the Agent executable files are installed. |
• |
/Library/Application Support/Quest/KACE/data/ where the Agent configuration, logs, and other data is stored. |
◦ |
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. |
sudo sh -c 'KACE_SERVER=kace_sma_name installer -pkg /Volumes/Quest_KACE/AMPAgent.pkg -target /'
hdiutil detach '/Volumes/Quest_KACE'
You can run shell scripts to deploy the Agent to Mac devices.
When using shell scripts to deploy the Agent, you can use the following command line options:
NOTE: The export call must proceed the install call. For example: sudo export KACE_SERVER=kace_sma_name installer -pkg '/Volumes/Dell KACE/AMPAgent.pkg' -target / |
The system looks for the value of host in these locations in the following 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
For information about using shell scripts and command lines, go to http://developer.apple.com.
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center