Obtenha ajuda em tempo real
Replication Shares are devices that keep copies of files for distribution. Replication shares are especially useful if your managed devices are deployed across multiple geographic locations.
For example, using a Replication Share, a device in New York could download files from another device at the same office, rather than downloading those files from an appliance in Los Angeles. A Replication Share is a full replication of all digital assets and is managed automatically by the appliance. Whenever a Replication Share is specified for a label, devices in that label go to the Replication Share to get files.
The KACE Agent always looks to the appliance for distribution files if no Replication Shares are specified for any label applied to a device. If the appliance uses multiple Replication Shares, the agent makes a random selection.
The appliance provides various methods for distributing applications, updates, and files to Mac OS X devices.
On Mac OS X, there is a universal installer with the usual PKG file extension. You cannot upload a PKG file directly, as these files consist of low-level directories, and web browsers cannot handle uploading entire directories.
Plain (APP) packages, which can be installed by dragging them to the Applications folder on the Mac, do not require installers. However, APP packages must be archived because they consist of low-level directories, similar to the installer packages.
You can archive installers along with plain applications. The appliance runs installers first and then copies applications into the Applications folder.
The supported package deployments are PKG, APP, DMG, ZIP, TGZ, and TAR.GZ.
If you package the file as a disk image, the appliance mounts and unmounts it quietly. This section provides examples for each type of deployment. For each of these examples, you must have already uploaded the file to the appliance prior to creating the Managed Installation package. Quest recommends that you install the application on a test device. When the KACE Agent connects to the appliance, the appliance creates an inventory item and a Managed Installation package for the application.
Managed Installations (MI) are the primary mechanism for deploying applications to, or removing applications from managed devices. Each Managed Installation describes a specific application title and version to be installed or removed, including installation commands, installation files, and target devices (identified by label).
Managed Installations always take place at the same time that managed devices upload inventory data to the appliance. In this way, the appliance confirms that the installation is actually needed before it performs the installation. Installation packages can be configured to run silently or with user interaction. Managed Installations can include installation, uninstallation, and command-line parameters.
Managed Installations requires an active network connections to the appliance. If the connection becomes disrupted during an installation, the process continues when the agent reconnects.
On Windows the most common Managed Installation package deployments are MSI, EXE, and ZIP files.
Supported package deployments for Linux devices include RPM, ZIP, BIN, TGZ, and TAR.GZ files.
Before you create a Managed Installation, the files you want to deploy must be associated with an application on the Software page. If the application is not yet on the Software page, you can add it as needed.
To add an application that is not on the Software page, you can:
CAUTION: If the display name of the application inventory item does not exactly match the name that the application registers in Add/Remove programs, the appliance might attempt to deploy a package repeatedly even though it is already there. To solve this problem, add the application to the Software inventory list, then use the registered application name in the Managed Installation.