You can create Managed Installations to deploy software to Agent-managed Windows devices.
For specific details on creating a Managed Installation for an MSI, EXE, or a ZIP file, see Examples of common deployments on Windows.
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. |
A name that identifies the Managed Installation. This name appears on the Managed Installations page. | |||||||||||||||
The package deployment setting. Options include:
| |||||||||||||||
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 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. | |||||||||||||||
Use the default commands during installation. Additional Parameters: Specify the installation behavior as follows:
| |||||||||||||||
| |||||||||||||||
Deployment tips from ITNinja. These tips are available only if you share usage data. See Configure data sharing preferences. |
3. |
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. | |||
| |||
6. |
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.
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.
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.
© ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center