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

are necessary to run the command, the basic requirements to run the program, and
whether another program must be run first.
■ Deployments Deployments, which are similar to advertisements in prior versions of
Configuration Manager, associate a program with a target collection. In addition,
deployments specify other options regarding how the source files for a program
should be accessed by clients and run. For example, you can configure a software
deployment to be available as an optional installation or as a required installation on
the client. A deployment also can specify an installation schedule and how a program
should run, depending on whether the client's current boundary group has a fast or
slow connection to the distribution point. For example, you can specify that the pro-
gram will not run if the client's boundary group has a slow connection to the selected
distribution point. Traditional software distribution uses the following process: pack-
ages contain programs, and you use deployments to make the programs available to
the collections.
Software deployment also involves a number of other components and concepts:
■ Distribution points Distribution points are site systems that store the package files,
which clients access when running a deployed program. After you create a new pack-
age that contains source files, you must distribute the package to at least one distribu-
tion point before clients can access it and run any of its programs. Typically, you should
place the content on a distribution point that is closest to the clients to which you want
to deploy it.
■ Package definition files You do not always need to create all packages and pro-
grams manually. Many software publishers provide package definition files for their
applications, which allow for automatic creation of packages and programs. Package
definition files specify a package's properties, such as its name and version, and one or
more program definitions. Program definitions in package definition files include the
program command and can include other properties such as disk-space requirements
and supported client architectures and operating systems.

Access accounts If you need to restrict access to a package, you configure which
accounts or groups have permission to access it. By default, administrators have Full
permissions, which enable them to perform any action on a package; users have Read
permissions.

■