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.
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.
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.
You can run commands on Agent-managed Mac devices to perform various operations.
1. |
You can remove the Agent from Mac devices manually by running commands on the devices.
1. |
You can run a command on Mac devices to determine whether the Agent is running.
1. |
root 2159 0.0 1.1 94408 12044 p2 S 3:26PM 0:10.94 /Library/Application Support/Quest/KACE/AMPAgent
You can run a command on Mac devices to verify the version of the Agent installed on those devices.
1. |
The version number is displayed.
You can manually collect information from Mac devices by forcing inventory updates.
See Forcing inventory updates.
To access the KACE Agent status using the Mac menu bar, you must enable the Agent Status On Device option in the Agent and Communication Settings section. For more information, see Configure Agent communication and log settings.
3. |
4. |
5. |
To temporarily suspend the agent's activity during a specific time period, click Snooze Agent, and select a time period in the menu. You can snooze the agent for 15 minutes, 30 minutes, one hour, or two hours. |
NOTE: You can only snooze the agent if the Agent Snooze on Device option is enabled in the Agent and Communication Settings section on the appliance, and if the maximum number of snoozes is not reached. For more information, see Configure Agent communication and log settings. |
6. |
To access any agent-related links, click Shortcuts in the menu, and then click a link, as applicable. Any standard Uniform Resource Identifier (URI) links are supported, such as https, ssh, and ftp URLs. |
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center