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.
This video (9 mins 16 sec) describes how to manage software installations and distributions across the entire network by using the Software Distribution module in BMC Client Management.
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.
The name of the archive which is distributed for the software distribution, its name is composed of the name of the package with a zip extension.
The type of file in which the package is stored. Possible values are the .zip format and the BCM Deploy proprietary .pkg format.
The type of the package. Custom indicates that the package may either be a manually created custom package or a patch package.
Indicates if the package is a patch package, that is, either the MS Secure file package or any other patch package which was manually created.
Package Size (KB)
The size in bytes of the respective package.
Compressed Package Size (KB)
The size of the respective package in its compressed form in KB.
The number of files which are contained in the respective package.
The name of the relay on which the package is stored and to be collected from the target devices.
Defines if the package contents are to be dynamically updated. Be aware, that dynamic packages, that is, when this option is activated, the package cannot be copied to other packagers, as the package content is build during the publishing process.
Automatically forces the reassignment whenever the package is published.
Defines if the package is to be installed under another directory or some of the files shall be mapped to one or more different locations.
The checksum of the respective package.
Defines if a package is only to be referenced by the master, that is, the master receives all information concerning the package but not the package itself. In this case the package is stored in a specific location, which, for example, can also be a removable unit such as a CD/DVD or a USB key, and a relay, which requires the package for itself or its clients, verifies the given location before requesting it from the master.
- Managing a Custom Package
- Managing an MSI Package
- Managing an RPM Package
- Managing Snapshot Packages
- Managing Package Folders
- Managing Package Factory
- Using packager
- Bulk-importing MSI packages
- Managing Transfer Windows
- Managing Storage Relays
- Multicast software delivery
- Managing common content and configuration