• |
Windows 32-bit devices: C:\Program Files\Quest\KACE\ |
• |
Window 64-bit devices: C:\Program Files (x86)\Quest\KACE\ |
The Agent configuration files, logs, and other data are stored in:
• |
Windows 32-bit devices: C:\Documents and Settings\All Users\Quest\KACE |
• |
Window 64-bit devices: C:\ProgramData\Quest\KACE |
2. |
◦ |
Use the following parameters when starting the installer: HOST=<appliance_hostname> TOKEN=<agent_token>, or: |
◦ |
Manually change the installation file name using the following syntax: AMPAgent-xx.xx.xx-x86_<appliance_hostname>+<agent_token>.msi |
The device information appears in the appliance Inventory within a few minutes. See Managing applications on the Software page.
There are several ways to deploy the Agent from the command line on Windows devices.
• |
In a batch file as part of a logon script that runs the installer (msiexec) and sets various parameters, such as the value of the host. |
The following table shows command line parameters used to deploy the Agent.
The system looks for the value of host in these locations in the order shown:
2. |
The HOST property value |
3. |
KACE_SERVER (environment variable) |
4. |
The amp.conf file |
If you want to register the agent with the appliance:
• |
Use the following parameters when starting the installer: HOST=<appliance_hostname> TOKEN=<agent_token>, or: |
• |
Manually change the installation file name using the following syntax: AMPAgent-xx.xx.xx-x86_<appliance_hostname>+<agent_token>.msi |
You can obtain the agent token string from the Agent Token Detail page. For more details, see Registering KACE Agent with the appliance
To access the KACE Agent status using the system tray, 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. |
7. |
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. |
• |
Windows 32-bit devices: C:\Program Files\Quest\KACE\ |
• |
Window 64-bit devices: C:\Program Files (x86)\Quest\KACE\ |
The Agent configuration files, logs, and other data are stored in:
• |
Windows 32-bit devices: C:\Documents and Settings\All Users\Quest\KACE |
• |
Window 64-bit devices: C:\ProgramData\Quest\KACE |
2. |
◦ |
Use the following parameters when starting the installer: HOST=<appliance_hostname> TOKEN=<agent_token>, or: |
◦ |
Manually change the installation file name using the following syntax: AMPAgent-xx.xx.xx-x86_<appliance_hostname>+<agent_token>.msi |
The device information appears in the appliance Inventory within a few minutes. See Managing applications on the Software page.
There are several ways to deploy the Agent from the command line on Windows devices.
• |
In a batch file as part of a logon script that runs the installer (msiexec) and sets various parameters, such as the value of the host. |
The following table shows command line parameters used to deploy the Agent.
The system looks for the value of host in these locations in the order shown:
2. |
The HOST property value |
3. |
KACE_SERVER (environment variable) |
4. |
The amp.conf file |
If you want to register the agent with the appliance:
• |
Use the following parameters when starting the installer: HOST=<appliance_hostname> TOKEN=<agent_token>, or: |
• |
Manually change the installation file name using the following syntax: AMPAgent-xx.xx.xx-x86_<appliance_hostname>+<agent_token>.msi |
You can obtain the agent token string from the Agent Token Detail page. For more details, see Registering KACE Agent with the appliance
To access the KACE Agent status using the system tray, 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. |
7. |
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. |
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. |
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center