Tchater maintenant avec le support
Tchattez avec un ingénieur du support

KACE Systems Management Appliance 14.0 Common Documents - KACE Service Desk Administrator Guide

About the KACE Service Desk Getting started
Configuring the appliance
Requirements and specifications Power-on the appliance and log in to the Administrator Console Access the Command Line Console Tracking configuration changes Configuring System-level and Admin-level General Settings Configure appliance date and time settings Managing user notifications Enable Two-Factor Authentication for all users Verifying port settings, NTP service, and website access Configuring network and security settings Configuring session timeout and auto-refresh settings Configuring locale settings Configuring the default theme Configure data sharing preferences About DIACAP compliance requirements Configuring Mobile Device Access Enable fast switching for organizations and linked appliances Linking Quest KACE appliances Configuring history settings Configuring Content Security Policy
Setting up and using labels to manage groups of items Configuring user accounts, LDAP authentication, and SSO Deploying the KACE Agent to managed devices Using Replication Shares Managing credentials Configuring assets
About the Asset Management component Using the Asset Management Dashboard About managing assets Adding and customizing Asset Types and maintaining asset information Managing Software assets Managing physical and logical assets Maintaining and using manual asset information Managing locations Managing contracts Managing licenses Managing purchase records
Setting up License Compliance Managing License Compliance Setting up Service Desk Configure the Cache Lifetime for Service Desk widgets Creating and managing organizations Importing and exporting appliance resources
Managing inventory
Using the Inventory Dashboard Using Device Discovery Managing device inventory
About managing devices Features available for each device management method About inventory information Tracking changes to inventory settings Managing inventory information Finding and managing devices Registering KACE Agent with the appliance Provisioning the KACE Agent Manually deploying the KACE Agent Using Agentless management Adding devices manually in the Administrator Console or by using the API Forcing inventory updates Managing MIA devices Obtaining Dell warranty information
Managing applications on the Software page Managing Software Catalog inventory
About the Software Catalog Viewing Software Catalog information Adding applications to the Software Catalog Managing License assets for Software Catalog applications Associate Managed Installations with Cataloged Software Using software metering Using Application Control Update or reinstall the Software Catalog
Managing process, startup program, and service inventory Writing custom inventory rules
Deploying packages to managed devices
Distributing software and using Wake-on-LAN Broadcasting alerts to managed devices Running scripts on managed devices Using Task Chains
Patching devices and maintaining security
Using the Security Dashboard About patch management Subscribing to and downloading patches Creating and managing patch schedules Managing patch inventory Managing Windows Feature Updates Managing Dell devices and updates Managing Linux package upgrades Manage quarantined file attachments
Using reports and scheduling notifications Monitoring devices
Getting started with monitoring Working with monitoring profiles Managing monitoring for devices Working with alerts
Using the Service Desk
Configuring Service Desk Using the Service Desk Dashboard Managing Service Desk tickets, processes, and reports
Overview of Service Desk ticket lifecycle Creating tickets from the Administrator Console and User Console Creating and managing tickets by email Viewing tickets and managing comments, work, and attachments Merging tickets Using the ticket escalation process Using Service Desk processes Using Ticket Rules Run Service Desk reports Archiving, restoring, and deleting tickets Managing ticket deletion
Managing Service Desk ticket queues About User Downloads and Knowledge Base articles Customizing Service Desk ticket settings Configuring SMTP email servers
Maintenance and troubleshooting
Maintaining the appliance Troubleshooting the appliance
Appendixes Glossary About us Legal notices

View the Agent version on Linux devices

Performing Agent operations on Linux devices

Start and stop the Agent on Linux devices
Manually remove the Agent from Linux devices
Verify that the Agent is running on Linux devices
View the Agent version on Linux devices
Collecting inventory information

You can run commands on Agent-managed Linux devices to perform various Agent operations.

Start and stop the Agent on Linux devices

You can run commands on Linux devices to start and stop the Agent. This procedure is useful in troubleshooting Agent-related issues.

1.
Open a terminal window from Applications > System Tools.
2.
To start the Agent, enter:
/opt/quest/kace/bin/AMPTools start
3.
To stop the Agent, enter:
/opt/quest/kace/bin/AMPTools stop
Manually remove the Agent from Linux devices

You can remove the Agent from Linux devices manually by running commands on the devices.

1.
Open a terminal window from Applications > System Tools.
2.
At the command prompt, enter:
sudo rpm -e ampagent
3.
Optional: Remove the kace directory:
rm -rf /var/quest/kace/
Verify that the Agent is running on Linux devices

You can run a command on Linux devices to determine whether the Agent is running.

1.
Open a terminal window from Applications > System Tools.
2.
At the command line prompt, enter:
ps aux | grep AMPAgent
This output indicates that the process is running:

root 6100 0.0 3.9 3110640 20384 ? Ssl Mar03 0:00 /opt/quest/kace/bin/AMPAgent --daemon

View the Agent version on Linux devices

You can run a command on Linux devices to verify the version of the Agent installed on those devices.

1.
Open a terminal window from Applications > System Tools.
2.
At the command prompt, enter:
rpm -q ampagent

The version number is displayed.

Collecting inventory information

You can manually collect inventory on Linux devices by forcing inventory updates.

See Forcing inventory updates.

Collecting inventory information

Performing Agent operations on Linux devices

Start and stop the Agent on Linux devices
Manually remove the Agent from Linux devices
Verify that the Agent is running on Linux devices
View the Agent version on Linux devices
Collecting inventory information

You can run commands on Agent-managed Linux devices to perform various Agent operations.

Start and stop the Agent on Linux devices

You can run commands on Linux devices to start and stop the Agent. This procedure is useful in troubleshooting Agent-related issues.

1.
Open a terminal window from Applications > System Tools.
2.
To start the Agent, enter:
/opt/quest/kace/bin/AMPTools start
3.
To stop the Agent, enter:
/opt/quest/kace/bin/AMPTools stop
Manually remove the Agent from Linux devices

You can remove the Agent from Linux devices manually by running commands on the devices.

1.
Open a terminal window from Applications > System Tools.
2.
At the command prompt, enter:
sudo rpm -e ampagent
3.
Optional: Remove the kace directory:
rm -rf /var/quest/kace/
Verify that the Agent is running on Linux devices

You can run a command on Linux devices to determine whether the Agent is running.

1.
Open a terminal window from Applications > System Tools.
2.
At the command line prompt, enter:
ps aux | grep AMPAgent
This output indicates that the process is running:

root 6100 0.0 3.9 3110640 20384 ? Ssl Mar03 0:00 /opt/quest/kace/bin/AMPAgent --daemon

View the Agent version on Linux devices

You can run a command on Linux devices to verify the version of the Agent installed on those devices.

1.
Open a terminal window from Applications > System Tools.
2.
At the command prompt, enter:
rpm -q ampagent

The version number is displayed.

Collecting inventory information

You can manually collect inventory on Linux devices by forcing inventory updates.

See Forcing inventory updates.

Manually deploying and upgrading the KACE Agent on Mac devices

Manually deploying and upgrading the KACE Agent on Mac devices

Deploy or upgrade the KACE Agent to Mac devices using the Agent installer
Deploy the Agent to Mac devices using the terminal window
Use shell scripts to deploy the KACE Agent

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.

* 
NOTE: Some commands must be run as root.
NOTE: Proceed with su or sudo as required.
Deploy or upgrade the KACE Agent to Mac devices using the Agent installer

You can manually deploy the KACE Agent on Mac devices by copying the Agent installation files to the devices and running the installer.

1.
Copy the KACE Agent installation file to the device.
See Obtaining Agent installation files.
2.
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.
3.
Double-click ampagent-x.x.build_number.dmg.
4.
Double-click AMPAgent.pkg.
5.
Follow the instructions in the installer.
Be sure to enter the name of your appliance.

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.
Deploy the Agent to Mac devices using the terminal window

You can manually deploy the KACE Agent on Mac devices by copying the Agent installation files to the devices and running commands.

1.
Copy the KACE Agent installation file to the device.
See Obtaining Agent installation files.
2.
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.
3.
Open a terminal window from Applications > Utilities.
4.
At the command prompt, enter the following commands to set the name of the server and install the Agent:
hdiutil attach ./ampagent-x.x.xxxxx-all.dmg

sudo sh -c 'KACE_SERVER=kace_sma_name installer -pkg /Volumes/Quest_KACE/AMPAgent.pkg -target /'

hdiutil detach '/Volumes/Quest_KACE'

Use shell scripts to deploy the KACE Agent

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:

•
hdiutil attach ./ampagent-6.x.xxxxx-all.dmg
•
sudo sh -c 'KACE_SERVER=kace_sma_name installer -pkg
•
/Volumes/Quest_KACE/AMPAgent.pkg -target /'
•
hdiutil detach '/Volumes/Quest_KACE'
* 
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:

1.
The installer file
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.

CAUTION:
 
CAUTION: If you leave the host value empty, you must set the environment variable. Otherwise, the Agent will not connect to the appliance. Quest KACE recommends that you use the fully qualified domain name as the hostname.

Deploy or upgrade the KACE Agent to Mac devices using the Agent installer

Manually deploying and upgrading the KACE Agent on Mac devices

Deploy or upgrade the KACE Agent to Mac devices using the Agent installer
Deploy the Agent to Mac devices using the terminal window
Use shell scripts to deploy the KACE Agent

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.

* 
NOTE: Some commands must be run as root.
NOTE: Proceed with su or sudo as required.
Deploy or upgrade the KACE Agent to Mac devices using the Agent installer

You can manually deploy the KACE Agent on Mac devices by copying the Agent installation files to the devices and running the installer.

1.
Copy the KACE Agent installation file to the device.
See Obtaining Agent installation files.
2.
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.
3.
Double-click ampagent-x.x.build_number.dmg.
4.
Double-click AMPAgent.pkg.
5.
Follow the instructions in the installer.
Be sure to enter the name of your appliance.

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.
Deploy the Agent to Mac devices using the terminal window

You can manually deploy the KACE Agent on Mac devices by copying the Agent installation files to the devices and running commands.

1.
Copy the KACE Agent installation file to the device.
See Obtaining Agent installation files.
2.
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.
3.
Open a terminal window from Applications > Utilities.
4.
At the command prompt, enter the following commands to set the name of the server and install the Agent:
hdiutil attach ./ampagent-x.x.xxxxx-all.dmg

sudo sh -c 'KACE_SERVER=kace_sma_name installer -pkg /Volumes/Quest_KACE/AMPAgent.pkg -target /'

hdiutil detach '/Volumes/Quest_KACE'

Use shell scripts to deploy the KACE Agent

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:

•
hdiutil attach ./ampagent-6.x.xxxxx-all.dmg
•
sudo sh -c 'KACE_SERVER=kace_sma_name installer -pkg
•
/Volumes/Quest_KACE/AMPAgent.pkg -target /'
•
hdiutil detach '/Volumes/Quest_KACE'
* 
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:

1.
The installer file
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.

CAUTION:
 
CAUTION: If you leave the host value empty, you must set the environment variable. Otherwise, the Agent will not connect to the appliance. Quest KACE recommends that you use the fully qualified domain name as the hostname.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation