Deploy and manage desktop and mobile applications - Managing Enterprise Devices and Apps - page 42

Applications and packages
Table 2-1 describes the differences between applications and packages based on application
management features.

TABLE 2-1 Applications and packages

Feature Application Package

Basic software information Options include location of files

used in the deployment and some
additional deployment settings.

Options include location of files
used in the deployment and some
additional deployment settings.

Extended software and support
information

The application model includes
extended information.

This feature is not part of the
package model.

Software command options Deployment types specify:

■

Programs specify:
■

The command to run. The command to run.

The optional Uninstall
command.

Basic requirements.

■ ■

Basic environment
settings.

■

Detection methods.

■

User experience settings. Basic dependency settings.

■ ■

Advanced requirements. Requirements are con-

tained in query rules for
the target collection.

■ ■

Advanced dependency
settings.

■

Multiple deployment options A single application can contain

multiple deployment types.

A package can contain multiple
programs.

Deployment by Application. Package and program.

Deployment option used The deployment type that

Configuration Manager uses is
based on requirements, and it
determines which to use at run
time.

Only one program is available
per deployment; all clients in the
targeted collection run the same
command.

Revision history Revisions are maintained, and you

can revert the application to previ-
ous versions.

Revision history is not maintained.

Supersedence Supersedence enables you to

define a replacement relationship
between applications.

Packages do not include a similar
feature.

Uninstall action You can deploy applications to

install or uninstall an application.

You always deploy packages by
using the Install action.

State-based deployment By using detection methods, the

Configuration Manager client can
determine the state of an applica-
tion in relationship to its action
and purpose and then perform the
appropriate actions if necessary.

Packages do not include a similar
feature.

There is some additional information that you can include in an application and not in a
package. This information includes:

General information, including administrative categories, date published, owners, and
support contacts.

■