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

The following list describes the sections in the Create Deployment Type Wizard and con-
siderations to keep in mind when configuring them.

General Contains basic information about the deployment type, including the name
and type of deployment. You can add additional information as reference information
for the Configuration Manager administrators.

■

Content Contains information about the source files and how this deployment type
will use them. If you are creating a deployment type for files that already exist on the
client devices, you need not specify the content location.

■

Programs Contains information about the install and uninstall commands in this
deployment type. There are some optional fields to ensure that applications install cor-
rectly and enable Windows source management.

■

Detection Method Contains information about how the success of an installation
will be determined. You must specify at least one detection method. For complex
installations, you can create a script to detect the installation.

■

User Experience Contains information about how the user will view and interact
with the deployment.

■

Requirements Contains the conditions that will determine whether to install this
deployment type.

■

Return Codes Contains the codes the program will return when it finishes running.
Return codes can indicate successful installation, failed installation, or some other con-
dition such as when the installation process requires a restart.

■

Dependencies Contains information about the deployment types you must install
before you can install this deployment type. You can configure the dependencies to be
autoinstalled during a deployment.

■

Detection methods
A detection method is a procedure that enables the deployment process to determine
whether an application is present on a system. Detection occurs before the content is
installed and at regular intervals afterward and provides the following functions:
■ Preventing Configuration Manager from reinstalling the application needlessly
■ Reinstalling a required application that the user has uninstalled, for example, through
Control Panel
■ Determining whether an application is present before running a deployed uninstall
command
When you create an application by using one of the automatic methods, Configuration
Manager creates a detection method based on the installer file used to create the applica-
tion. Generally, this is sufficient for most deployments. However, when you create a deploy-
ment type manually or when you need more refinement, you can create enhanced detection
methods.