Application Deployment Types in SCCM 2012

Purpose: How to use Application Deployment Types properly – real-life examples

The new features in SCCM 2012 could confuse at the first sight, if you dont stop to study them for a while. Old SCCM admins are used to packages while new admins are jumping straight into the applications. This post will focus on the applications only.

Deployment Types

When you first create an application, deployment type is one of the tabs you will be going through. You can imagine Application to be the raw framework containing all the metadata of a single software version and a Deployment Type to be one instance of the actual install script.

There can be many different deployment types for one application and they can be prioritized. When the application is deployed, Deployment Types will be tried in the priority order on the target machine. If the first priority requirements are met that deployment type will be selected for the target machine. If the requirements are not met, the first deployment type will be skipped and the second priority type will be tried (and so on).

Deployment Type: One Application, One OS

So this is the basic scenario, if your environment is highly stable. You only need one deployment type for your application to deploy for the target operating system. In this example, it is a Windows 7 operating system (as seen below).

Deployment Type: One Application, Different OS

One of the possible scenarios is to create one Application in SCCM, and several deployment types for different operating systems. This requires that each Deployment Type will have a requirement for a different OS. So in this case SCCM will still begin from the first priority (it does not actually mater, which one is now the first one) and go through all of the Deployment Types until the requirements are met (found correct OS).

Deployment Type: One Application, Install Order

Another possible scenario is that something must be installed before the actual application. SCCM offers various ways to handle this, and one of them is using the Deployment Types. You can first create a Deployment Type that does something that you want to be run AFTER the SCCM begins installing the Application. Create a second Deployment Type that you want to be run BEFORE the first Deployment Type.

Set the first priority Deployment Type to depend on the second priority Deployment Type. Now, when the Application begins installing, the first Deployment Type will first call for the second Deployment Type to install (because it depeneded on it) and after it has been finished the first priority Deployment Type will install.

This could be used to, for example, create user specific settings after an application has been instelled only when a user logs in the target computer.

Leave a Reply

Your email address will not be published. Required fields are marked *

one + three =

Post Navigation