The most common Managed Installation package deployments are MSI, EXE, and ZIP files.
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)
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. |
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.
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.
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.
2. |
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. |
a. |
b. |
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. |
8. |
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. |
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. |
c. |
2. |
In the Software drop-down list, select a software title. To search for a title, begin typing in the Software field. |
rpm -U packagename.rpm
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.
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:
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.
//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.
A name that identifies the Managed Installation. This name appears on the Managed Installations page. | |||||||
Select the most appropriate time for this package to be deployed. For the Linux platform, the options are Anytime (next available) and Disabled. | |||||||
Indicate if you want to deploy the software title from Cataloged Software or all Software by selecting one of these options.
| |||||||
| |||||||
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: 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
Where filename is the UNC path to the file. If the path contains spaces, enclose the entire path in double quotation marks.
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. See Distributing packages from alternate download locations and Replication Shares and Add or edit manual labels. | |||||||
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: | |||||||
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 the command only. This does not download the actual digital asset. | |||||||
Deployment tips from ITNinja. These tips are available only if you share usage data. See Configure data sharing preferences. |
Deploy to all devices. Clear the check box to limit the deployment to specific labels or devices. | |||
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. | |||
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.
|
| |||||||
| |||||||
|
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. | |||
| |||
7. |
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.
This creates filename.tar.gz
2. |
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. |
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.
a. |
b. |
c. |
Select the application title with which the TAR.GZ file is associated from the Software drop-down list. |
If no Run Parameters are provided, -U is used.
rpm [-U | Run Parameters] "packagename.tgz"
d. |
e. |
The KACE Agent automatically runs deployment packages with RPM extensions.
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center