• |
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. |
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 |
To access the KACE SMA Agent status using the system tray, you must enable the Agent Status On Device option in the Communication Settings section. For more information, see Configure Agent communication and log settings.
2. |
To find out if the agent is connected to the appliance, observe the icon on the right of the Status option in the menu. |
3. |
You can manually deploy or upgrade the KACE SMA Agent on Linux devices as needed.
2. |
◦ |
/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 |
You can manually upgrade the KACE SMA Agent on Linux devices by running commands on the devices.
2. |
You can manually deploy or upgrade the KACE SMA Agent on Linux devices as needed.
2. |
◦ |
/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 |
You can manually upgrade the KACE SMA Agent on Linux devices by running commands on the devices.
2. |
You can manually deploy or upgrade the KACE SMA Agent on Linux devices as needed.
2. |
◦ |
/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 |
You can manually upgrade the KACE SMA Agent on Linux devices by running commands on the devices.
2. |
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy