The following is a description of the package properties. Right click on the package and click Properties to open this view. The options are separated into 5 areas: Options, description, servers, catalog and license consolidation.
The package can be set to run only after the successful installation of another package. For example, Microsoft Internet Explorer must be installed before installing Microsoft Office. Package dependencies can only be made based on the other packages of the same type.
|Dependency Tree||Clicking this button will open the Dependency Tree.|
You can change the priority of the package with the slider or type it directly in the priority box. The lower the number, the higher its priority will be.
Package is mandatory
If the package is to be installed on all computers it can be set to mandatory, meaning that all computers that are running the CapaInstaller Agent will run the package. This will include new units added to the system later.
Allow package to be installed on a server
Computers that are running a server operating system will only run packages for which this box is checked. This includes packages otherwise marked as mandatory. This feature gives managers very specific control over which types of software are installed on servers, for which stability is paramount and which typically run a very different set of application than workstations.
Package must run interactively
Typically the CapaInstaller Agent is running as a service on the local workstation. A service runs in its own user context and does not display any kind of GUI. Some packages require user interaction, and in these cases, mark this check box.
This check box will only be available on certain CapaInstaller default packages. It defines if data is collected in batch mode or online.
Client Execution Environment
This lets you specify what environment the package is executed in. The options are x86, x64 or Dynamic (can run on both as well as other environments).
The name of the package.
Description of the package.
In this window you can decide on which Management Servers the package
should be synchronized to. The Management Servers
available are those linked to the Management Point the package resides
Right click a Management Server:
This will synchronize the package to the Management Server.
This will remove the package from the Management Server.
Package is published to catalog
Mark this check box to set the package as an optional install available in the catalog. Clear this box to automatically run the package on all units to which you have assigned it.
Enter the name of the package. This is the name that will appear in the catalog and shown to users.
Select the name of the catalog category to which the package should belong. Categories
Publish to everyone
Use this pair of radio buttons to decide who will be able to see the package. Advertise to everyone makes it available to all users.
Publish to package members only
The package will only be advertised to those units to which it has been assigned.
This provides a description for users browsing the catalog of user selectable packages.
In this window you can link the package to a metering group, and define how long the software can be inactive before it is automatically uninstalled.
This feature is only available for computer and user packages, and they must have a uninstall job.
Capainstaller 4 default packages do not have this feature.
The package 'License Consolidation 4.1' is responsible for performing the actual consolidation.
The package is located in the CapaInstaller 4 folder and must be scheduled to the target units/group.
Metering groups are created in Asset Management, and can be linked to software. Select an existing metering group in the drop down to link the package to the metering group.
This determines how many days the software linked to the metering group can be inactive before the package is uninstalled.
In this windows you can see the dependency tree for a given package. The selected package is displayed in bold. The tree shows the dependency in both directions. Packages which this package is dependent upon and all packages that are dependent on this package. Packages dependent on this package will also have their dependency tree resolved recursively. Clicking 'Copy to clipboard' will copy a textural representation of the tree to clipboard.
Packages are listed by their display name and priority is displayed in parentheses following display name.