Element

Description

Dependency

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.
 

Priority

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.
 

Collect Online

This checkbox 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).

• x86: If the package is installed in an x64 environment the package installation will be done in the 32 bit context.
• x64:If the package is installed in an x64 environment the package installation will be done in the 64 bit context.
• Dynamic: If the package is installed in an x86 environment the package installation will be done in the 32 bit context. If the package is installed in an x64 environment the package installation will be done in the 64 bit context.

Element

Description

Name

The name of the package.

Description

Description of the package.

Element

Description

Link

This will synchronize the package to the Management Server.

Unlink

This will remove the package from the Management Server.

Element

Description

The package is published to catalog

Mark this checkbox 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.
 

Name

Enter the name of the package. This is the name that will appear in the catalog and shown to users.
 

Category

Select the name of the catalog category to which the package should belong. Categories will help users find what they need in a large catalog. See Catalog groups for more information on catalogs.
 

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.

Description

This provides a description for users browsing the catalog of user-selectable packages.
 

Element

Description

Metering Group

Metering groups are created in Asset Management and can be linked to the software. Select an existing metering group in the drop-down to link the package to the metering group.
See Application groups for more information on metering groups.
 

Inactive period

This determines how many days the software linked to the metering group can be inactive before the package is uninstalled.