How applications are installed:

Applications are targeted to either a device or the user and are classified as just "available" or "mandatory" (required by a certain date).

Where the Application Will Be Presented	Required Deployment	Available Deployment
User targeted	Software Center	Application Catalog website point and Software Center (once installed)
Device targeted	Software Center	Software Center

Source: Agerlund, Kent (2014-08-13). System Center 2012 R2 Configuration Manager: Mastering the Fundamentals, 3rd Edition (p. 247). Deployment Artist. Kindle Edition.

 

The Application (key points)

You will not be creating a single .MSI document, nor will you be creating a single .exe file to deploy the application.

• You will be creating specific software packages that will include all possible deployment types.
• The application package will be a package that contains multiple "child" deployment types, of which only one will be used to deploy the application.

 

The Create Application Wizard

Application Tab	Description
Application Properties	Naming standards important here for consistency.
Application Catalog	Enables users to search for applications and for users to obtain more information about the application.
References	If there are any other applications that are part of the same "family" of applications and is where it is stated whether the application has dependencies or is superseded by another application.
Distribution Settings	Directs the package to be distributed to specified distribution points.
Deployment Type	Lists associated deployment types.
Content Locations	A list of the distribution point( s) and distribution point group( s) where the content can be located.
Supersedence	Creates a relationship between this application an the application you want to supersede.
Security	Security information for the application.

 

The Deployment Type

Depending on what type of deployment you choose, you will be prompted with various deployment type settings as described in the table below.

 

Deployment Type Tab	Short Description
General	Properties like name, technology, comments, language will be entered here.
Content	Source location, plus allows for Microsoft BranchCache support ("in house") application sharing to create a fallback source location.
Programs	You specify the install and uninstall programs here.
Detection Method	Required. Used by the client to determine it the program is already in installed on the device.
User Experience	Defines user vs device installation here.
Requirements	Sets "global conditions", which are device, user, and custom requirements that have to be evaluated before the application can be installed.
Return Codes	You specify the return code for successful, restart, failure installs.
Dependencies	Lists other deployment types that this deployment type depends on - does the target computer have the necessary "prerequisite" applications installed so that the deployed application will actually work.
Publishing	Only available for virtual applications. This defines the icons that are published when this type of application is installed (or made available).

 

The Deployment

Settings here are dependent on the target of your deployment - user or device, available or mandatory (deadline specified). This table summarizes the pages that you will configure for you deployment settings.

Deployment Tab	Description
General	Contains information about software used, collection, and optional comments.
Content	Lists distribution point(s) and distribution point group(s) where the content is available.
Deployment Settings	Defines the deployment action, install or uninstall; the purpose of the deployment, available or required; security control. Also allows for Wake On LAN installations.
Scheduling	Define when the application is available (if applicable), deadline (if required).
User Experience	Defines how the user must interact with the deployment. If required, options are available to hide notification/software center. If available, level of notifications shown, always available in the software center. Maintenance schedules (or opt-out) can also be defined.
Alerts	These alerts pertain to the deployment success/failure.