Chat now with support
Chat mit Support

KACE Systems Management Appliance 13.2 Common Documents - Administrator Guide

About the KACE Systems Management Appliance 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 Agent 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
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 Managing Mac profiles 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 Maintaining device and appliance security Manage quarantined file attachments
Using reports and scheduling notifications Monitoring servers
Getting started with server 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

Standard EXE example

Examples of common deployments on Windows

Standard MSI example
Standard EXE example

The most common Managed Installation package deployments are MSI, EXE, and ZIP files.

Standard MSI example

Using MSI files is an easy, self-contained way to deploy software to Windows devices. If your MSI file requires no special transformation or customization, the deployment is straightforward.

MSI files require a /i switch when using other switches with an install.

The appliance parameter line does not require the filename or msiexec syntax. Only the /* input is required:

/qn /I (Correct)

msiexec /I /qn (Incorrect)

* 
NOTE: To use parameters with MSI files, all your target devices must have the same version of Windows Installer (available from Microsoft). Some switches might not be active on older versions. The most up-to-date version of Windows Installer can be distributed to devices from the appliance.
* 
TIP: If you are using Windows Installer 3.0 or higher, you can identify the supported parameters by selecting the Run program available from the Start menu. Enter msiexec in the pop-up window. A window that shows the supported parameters list appears.
Standard EXE example

EXE files are similar to MSI files with one exception.

EXE files differ from MSI files as follows: /I is not required in the Run Parameters line when using an EXE file.

When using an executable file, it is often helpful to identify switch parameters for a quiet or silent installation. To switch parameters, specify /? in the Run Parameters field.

Create Managed Installations for ZIP files

Create Managed Installations for ZIP files

Deploying software using a ZIP file is a convenient way to package software when multiple files are required to deploy a title.

For example, a software title might require a setup.exe file, configuration files, and data files. If you have a CD-ROM that contains a group of files required to install a particular application, you can package them together in a ZIP file and upload them to the appliance for deployment.

* 
NOTE: The KACE Agent automatically runs deployment packages with MSI and EXE extensions.
NOTE: In addition, you can create a ZIP archive that contains many files and direct the appliance to unpack the archive and run a specific file. Place the name of the file that you want to run in the command (executable) field within the deployment package (for example, runthis.exe).

To distribute applications to managed devices, you must attach the digital assets, which are the files required for installation, to applications. In addition, you must select the supported operating systems for applications. See Attach digital assets to applications and select supported operating systems.

1.
Browse to the location that contains the necessary installation files, select all the files and create a ZIP file using a utility such as WinZIP®.
2.
Log in to the appliance Administrator Console.
3.
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information.
4.
Create an inventory item for the target deployment.
You can do this manually from the Inventory > Software page or by installing the package on a device that regularly connects to the appliance. See About the Software page.
5.
Associate the ZIP file with the inventory item and upload it to the appliance:
a.
On the left navigation bar, click Distribution, then click Managed Installations.
b.
Select Choose Action > New.
c.
Select the application title that the ZIP file is associated with from the Software drop-down list. To see all application titles, clear the check box Only display records with an associated file.
6.
In the Run Parameters field, specify the complete command with arguments.
For example: setup.exe /qn
7.
Specify additional settings as needed.
See Create Managed Installations for Windows devices.
8.
Click Save.

Create Managed Installations for RPM files

Create Managed Installations for RPM files

You can create Managed Installations to deploy software on Linux-based devices using RPM files.

To distribute applications to managed devices, you must attach the digital assets, which are the files required for installation, to applications. In addition, you must select the supported operating systems for applications. See Attach digital assets to applications and select supported operating systems.

1.
Go to the Managed Installation Detail page:
a.
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information.
b.
On the left navigation bar, click Distribution, then click Managed Installations.
c.
Select Choose Action > New.
2.
In the Software drop-down list, select a software title. To search for a title, begin typing in the Software field.
By default, the KACE Agent attempts to install the RPM file using the following command. In general, this command is sufficient to install a new package or update an existing one to a new version:

rpm -U packagename.rpm

If you select a ZIP, TGZ, or TAR.GZ file, the content is unpacked, and the root directory is searched for all RPM files. The installation command runs against each of these files. The appliance finds all RPM files at the top level of an archive automatically, so you can install more than one package at a time. You can also create an archive containing a shell script and then specify that script name as the full command. The appliance runs that command if it is found; otherwise, the appliance logs an error.

Default parameters are used unless you specify parameters in the Run Parameters field.

You can specify wildcards in the filenames you use. If the filename contains spaces, enclose it in single or double quotation marks. The files are extracted into a directory in /tmp and it becomes the current working directory of the command.

* 
NOTE: On Red Hat Linux, if you only want to run your script, you do not need to include any other files in your archive.

If the path environment variable of your root account does not include the current working directory, and you want to run a shell script or other executable that you have included inside an archive, specify the relative path to the executable in the Full Command Line field. The command runs inside a directory alongside the files that have been extracted.

For example, to run a shell script called installThis.sh, package it alongside an RPM file, and then enter the command: ./installThis.sh in the Installation Command field. If you archive it inside another directory, the Installation Command field is:

./dir/filename.sh

Both these examples, as well as some other appliance functions, assume that sh is in the root's path. If you are using another scripting language, you might need to specify the full path to the command processor you want to run in the installation command, such as:

/bin/sh ./filename.sh

Include appropriate arguments for an unattended, batch script.

If you select the uninstall check box in the MI detail, the KACE Agent runs the following command on either your standalone RPM file or each RPM file it finds in the archive, removing the packages automatically:

//usr/sbin/rpm -e packagename.rpm

The package is removed only if the archive or package has been downloaded to the device. If you select the Uninstall Using Full Command Line check box, specify a full command line in the Installation Command field to ensure the correct removal command runs on the correct package. Because no package is downloaded in this case, specify the path in the installation database where the package receipt is stored.

3.
If your package requires additional options, provide the following information:

Option

Description

Name

A name that identifies the Managed Installation. This name appears on the Managed Installations page.

Execution

Select the most appropriate time for this package to be deployed. For the Linux platform, the options are Anytime (next available) and Disabled.

Inventory

Indicate if you want to deploy the software title from Cataloged Software or all Software by selecting one of these options.

•
To search for a specific title, begin typing in the Software or Cataloged Software field.
* 
NOTE: Reclaiming unused software licenses only. The name of the software that you want to uninstall appears in this field by default. For more information, see Reclaim unused software licenses.
•
If you want to display only the software that has one or more associated files, select Only Display Software With an Associated File.

Associated File

A Software and Cataloged Software title can have one or more files attached to them, as needed. Indicate if you want to select a specific file associated with the selected software title.

•
Choose associated file: Select this option if you want to associate a file. You can select a file in the list. If you know the file name, start typing it in the box, and select it from the available entries in the list.
•
Do not associate file: Select this option if you do not want to associate a file.

Alternate Location

Specify a location from which files can be downloaded for a specific Managed Installation.

Path: Enter the location where the KACE Agent can retrieve digital installation files.

Checksum: Enter an alternate checksum (MD5) that matches the MD5 checksum on the remote file share. If no checksum is entered, the digital asset on the file share must match the digital asset associated with the deployment package on the appliance. Also, the target path must include the complete filename (for example,\\fileserver_one\software\adobe.exe). You can create the checksum using any tool, including KDeploy.exe, which is installed with the KACE Agent.

To create the checksum using KDeploy.exe:

1.
On a device with the KACE Agent installed, open a command prompt or terminal window.
2.
Go to the Quest KACE installation directory. For example:

Windows 32-bit devices: C:\Program Files\Quest\KACE

Windows 64-bit devices: C:\Program Files (x86)\Quest\KACE

Mac OS X devices: /Library/Application Support/Quest/KACE/bin

3.
Enter the following command: KDeploy -hash=filename

Where filename is the UNC path to the file. If the path contains spaces, enclose the entire path in double quotation marks.

4.
Press Ctrl C or Command C to copy the MD5 checksum. You can then paste it into other files, such as Notepad.

Credential: The details of the service account required to connect to the device and run commands. Select existing credentials from the drop-down list, or select Add new credential to add credentials not already listed. See Add and edit User/Password credentials.

* 
NOTE: If the target device is part of a replication label, the appliance does not fetch applications from the alternate download location. You can edit an existing label or create a label to specify the alternate location globally. Because that label cannot be specific to any Managed Installation, you cannot specify an alternate checksum that matches the checksum on the remote file share.

See Distributing packages from alternate download locations and Replication Shares and Add or edit manual labels.

Installation Command

Installation command options.

Default Installation

Select this option if you have an RPM file and you want the appliance to run the default installation command. Linux devices use: rpm [-U | Run Parameters] "packagename.tgz"

Run Parameters: (Optional) If you select Use Default, specify the parameters to use. Run parameters are not required if you have an RPM file.

Enter a value to override (Default -U default).

For example, if you set Run Parameters to: -ivh --replacepkgs, then the command that runs on the device is:

rpm -ivh –replacepkgs package.rpm

Override Default Installation

Select this option to specify the complete command line here. If you are using an archive file, this command runs against all of the RPM files it finds.

Uninstall

Remove the package from the device using the command line. If you specified a command in the Full Command Line field, the command runs. Otherwise, the KACE Agent attempts to run the command, which is generally expected to remove the package.

Run Command Only (do not download file)

Run the command only. This does not download the actual digital asset.

Delete Downloaded Files

Delete the files when the deployment is complete.

ITNinja

Deployment tips from ITNinja. These tips are available only if you share usage data. See Configure data sharing preferences.

4.
Specify deployment settings:

Option

Description

All Devices

Deploy to all devices. Clear the check box to limit the deployment to specific labels or devices.

Labels

Limit deployment to devices that belong to specified labels. To select labels, click Edit, drag labels to the Limit Deployment to window, then click Save.

If you select a label that has a Replication Share or an alternate download location, the appliance copies digital assets from that Replication Share or alternate download location instead of downloading them directly from the appliance.

* 
NOTE: The appliance uses a Replication Share before it uses the KACE Alt Location.

Devices

Limit deployment to specific devices. In the drop-down list, select the devices to which you want to deploy the application. To filter the list, type a few characters in the Devices field. The number next to the field indicates the number of devices available.

* 
NOTE: Reclaiming unused software licenses only. Any devices from which you want to remove the applicable software are listed. You can edit the list of devices, as needed. To remove the software from all devices, simply select , as described above. For more information, see Reclaim unused software licenses.
5.
Specify the user notification settings:

Option

Description

Alert user before run

Display a message on managed devices before installation. When you select this option, the following fields appear:

•
Message: The message that appears on managed devices before installation begins. It starts with snooze options that allow the user to run the managed install at a later time.
•
Timeout: The length of time, in minutes, during which the message appears.
•
Action: The action that takes place at the end of the Initial Message Timeout period. Options include Install later or Install now. Select Install now to install the application immediately, or select Install later to postpone the installation until a user responds. Install later is useful when you want to notify users of an installation or reboot before it occurs.

Initial Message

Display a message on managed devices before installation. When you select this option, the following fields appear:

•
Message: The message that appears on managed devices before installation begins.
•
Timeout: The length of time, in minutes, during which the message appears.
•
Action: The action that takes place at the end of the Initial Message Timeout period. Options include Install later or Install now. Select Install now to install the application immediately, or select Install later to postpone the installation until a user responds. Install later is useful when you want to notify users of an installation or reboot before it occurs.

Completion Message

Display a message on managed devices after the installation is complete. When you select this option, the following fields appear:

•
Message: The message that appears on managed devices when the installation is complete.
•
Timeout: The length of time, in minutes, during which the message appears.
6.
Select Schedule options:

Option

Description

Deployment Window

Start

End

The time, in 24-hour clock format, for package deployment to start and end. The Deployment Window time affects all Action options. Also, the run intervals defined in the appliance Settings interact with or override the deployment window of specific packages.

Order

The order in which to install or uninstall applications. The lowest value is deployed first. If an install action and an uninstall action both have the same order value, the uninstall action is performed first.

* 
NOTE: Managed Installations are always deployed in order, regardless of whether their specified software packages come from the Software Catalog or the Software list. Managed Installations with a lower deploy order always prevent other Managed Installations from running until they are successfully installed or exceed the specified retry times.

Maximum Attempts

The maximum number of attempts, between 0 and 99, to indicate the number of times the appliance tries to install the package. If you specify 0, the appliance attempts to install the package indefinitely.

7.
Click Save.

Create Managed Installations for TAR.GZ files

Create Managed Installations for TAR.GZ files

Deploying software using a TAR.GZ file is a convenient way to package software when more than one file is required to deploy a particular software title.

For example, some applications require several files, such as RPM, configuration, and data files, for deployment. You can package these files together in a TAR.GZ file, upload them to your appliance, and create Managed Installations that use the TAR.GZ files.

To distribute applications to managed devices, you must attach the digital assets, which are the files required for installation, to applications. In addition, you must select the supported operating systems for applications. See Attach digital assets to applications and select supported operating systems.

1.
Use the following two commands to create a TAR.GZ file:
a.
tar –cvf filename.tar packagename.rpm
b.
gzip filename.tar

This creates filename.tar.gz

2.
Log in to the appliance Administrator Console.
3.
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information.
4.
Create an inventory item for the target deployment.

You can do this manually from the Inventory > Software page, or by installing the package on a managed device that regularly connects to the appliance. See About the Software page.

5.
Associate the TAR.GZ file with the inventory item, and upload it to the appliance:
a.
On the left navigation bar, click Distribution, then click Managed Installations.
b.
Select Choose Action > New.
c.
Select the application title with which the TAR.GZ file is associated from the Software drop-down list.
During installation, the file is uncompressed and the installation command runs against each of the RPM packages.

If no Run Parameters are provided, -U is used.

You do not need to specify a full command line. The appliance runs the installation command by itself. The Linux device tries to install using:

rpm [-U | Run Parameters] "packagename.tgz"

d.
Optional: If you have many files, create a ZIP archive that contains them, then direct the appliance to unpack the archive and run a specific file.
To do this, place the name of the file that you want to run in the command (executable) field within the deployment package (for example, runthis.exe). Provide additional package details. See Using Managed Installations.
e.
Click Save.

The KACE Agent automatically runs deployment packages with RPM extensions.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen