Default language.

Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Managing Packages

Packages are one of the key components of software distribution. They contain the instructions necessary to install software on a target device and all the files of the application to install. The package is essentially a compressed archive of new files plus some intelligence. The intelligence is automatically built into an operational rule containing the scripts that deal with creating directories, installing the files, adding icons, changing the Registry and starting services. The scripts also deal with error checking during installation and the creation of log files. Packages should be created on a reference device in a Production Environment.

The Packages node of the CM console provides all published packages of any type which are available within your network for software distribution. The packages are not created here, they are created on individual clients through the Package Factory, they are only stored under this node to be available to everybody. Under this node you can define the devices and device groups to which the packages will be distributed and the schedules for the package executions.

Like other objects in CM, published packages are stored in folders. These folders are for grouping one or more packages by type to make organisation and finding packages easier.

Package Folders are created as organisational containers for different types of packages. They can contain any number of predefined or custom-made packages and package folders for software distribution within your network.

Automatically creating packages and folders

A number of Packages and Package Folders are created automatically:

  • The CMUpgrade folder is created automatically when the master is installed or updated. It contains the files necessary to update the relays and clients in your network to the current version.
  • The Patches folder is created when the first patch download is requested and executed. All patches that are downloaded and published will be located in their respective directories under this main folder. Be aware that the packages created by this patch download and publication process can be edited via the Package Factory but their object associations are not modifiable.
  • The ConfigFiles.cst package is created if you have a valid Patch Management license. This file is the database file for the patch inventory generation and when the agent is started for the first time, it will download and publish the newest version of this group of files in the form of a custom package.

Related topics

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*