Assumptions

System Center 2012 is installed a configured.

There is at least one application in a source folder somewhere that is accessible.

Create a New Application

 

Go to Software Library and choose Application Management

Choose Applications

Depending on screen resolution choose either Create and Create Application or directly on Create Application (in the upper left corner of the console).

Create Application Wizard

Depending on which type of application you would like to create.

1. Automatically detect application information –Configuration Manager attempts to read information about the application from the application installation files, malady and then automatically populates fields in the wizard with discovered information. Use this method when you want to create an application with a single deployment type that uses the default settings.

2. Manually define application information – Information about the application is manually entered by the administrator. Use this method when you want to create a more complex application with multiple deployment types, cheap detection methods, viagra requirements or dependencies, or when application information could not be read from the installation files.

 

Windows Installer (Native)

Click Next

Note
Some of the application information might already be present if it was read from the application installation files.
  1. General information about the application such as the application name, comments, version and an optional reference to help you reference the application in the Configuration Manager console.
  2. Option: create or add to an existing category.
  3. Specify whether the applications deployment type will be installed for the currently logged on user or for all users. You can also specify that the deployment type will be installed for all users if it is deployed to a device or to a user only if it is deployed to a user.

Click Next

Click Close

Editing the application

Right click the application and choose Properties

Adding general information

This information is for the administrators and will not show up for the end users.

Adding information to Application Catalog

Type in what kind of information the end users should see in the Application Catalog for this application.

You may create or choose an already existing category so the user can filter applications.

User documentation can be either a local document or a weblink.

Write any additional information about the application.

Type in one or more keywords that are associated with this application. Users can search for this and get a hit in the Application Catalog.

Choose an icon if desired.

References

Here you can see if the applications are dependent on this application or applications that supersede it.

Distribution Settings

  1. Choose distribution priority Low, Medium, High (recommended Medium)
  2. Check this box if the first client that ask for this application should automatically download it to the preferred distribution point if it’s missing.
  3. Prestaging
    1. Automatically download content when packages are assigned to distribution points – This option is designed when you have smaller packages that the scheduling and throttling settings will be enough control for the distribution of content.  An example for this is Silverlight or any other small content package
    2. Download only content changes to the distribution point – This option is desgined when you initial package maybe large, but then future updates to the content in the package are generally smaller.  A couple examples are Microsoft Office, the initial package may be 700 MB and that is too much to send over the network.  However updates to this package might be something like a monthly security update and the 10 MB size is OK to distribute over the network.  Driver Packages are another great example of this.  Incremental additions of drivers might be small, but the initial package is large is size. (Not available for Applications in Beta 2, but will be available post Beta 2).
    3. Manually copy the content in this package to the distribution point – This option is designed to never send the package to distribution point.  This is designed for large file packages like an operating system image or when you just want to ensure that the network to the distribution point is not used for content distribution.

Deployment Types

  1. Increase or decrease the priority of the chosen deployment type
  2. Deployment type; MSI, App-V, CAB, SIS, Other
  3. Add, Edit, Copy or Delete a deployment type.

Edit a Deployment Type

 

This tab should be okay, but edit Name, Comments and Language if desirable.

  1. Specifies whether content should be retained in the cache on the client computer indefinitely even if it has already been run. Although this option can be useful with some deployments, such as Windows Installer-based software that requires a local source copy be available for applying updates, it will reduce the available cache space. Specifying this option might cause a large deployment to fail at a later point if there is insufficient space available in the cache.
  2. Select this option to reduce load on the network by allowing clients to download content from other local clients on the network that have already downloaded and cached the content. This option utilizes Windows BranchCache and can be used on computers running Windows Vista SP2 and later.

1. Installation program – Specify the name of the installation program and any required installation parameters or click Browse to browse to the installation file location.

Installation start in – Specifies the folder that contains the installation program for the deployment type. This folder can be an absolute path on the client or a path to the distribution point folder that contains the installation files. This field is optional.

2. Uninstall program – Specify the name of the uninstall program and any required parameters or click Browse to browse to the uninstall file location. This field is optional.

Uninstall start in – Specifies the folder that contains the uninstall program for the deployment type. This folder can be an absolute path on the client or a path relative to the distribution point folder that contains the package. This field is optional.

 

In the Setting type drop-down list of the Detection Rule dialog box, choose the method you want to use to detect the presence of the deployment type.

The available methods are:

File System – Allows you to detect whether a specified file or folder exists on a client device indicating that the application is installed.

Registry – Allows you to detect whether a specified registry key or registry value exists on a client device indicating that the application is installed.

Windows Installer – Allows you to detect whether a specified Windows Installer file exists on a client device indicating that the application is installed.

 

On the Requirements page of the Create Deployment Type Wizard, click Add to open the Create Requirement dialog box and add a new requirement.

From the Category drop-down list, select whether this requirement is for a device, a user or select Custom to use a previously created global condition. When you select Custom, you can also click Create to create a new global condition.

From the Condition drop-down list, select the condition that you want to use to assess whether the user or device meets the installation requirements. The contents of this list will vary depending on the selected category.

From the Operator drop-down list, choose the operator that will be used to compare the selected condition to the specified value to assess whether the user or device meets in the installation requirement. The available operators will vary depending on the selected condition.

In the Value field, specify the values that will be used with the selected condition and operator whether the user or device meets in the installation requirement. The available values will vary depending on the selected condition and the selected operator.

 

Dependencies define one or more deployment types from another application that must be installed before a deployment type is installed. You can configure dependent deployment types to install automatically before a deployment type is installed

Done.

There are a lot of other things you can do and other ways of creating an application, but this should get you going.

Enjoy!

 

Leave a Reply