How to Create an Application in Configuration Manager 2012


Nasıl Yaparım:

After you start the Create Application Wizard, there are two methods available to configure general information about the application:

·         Automatically detect application information – Configuration Manager attempts to read information about the application from the application installation files, and then automatically populates fields in the Wizard with discovered information.

·         Manually define application information – Information about the application is manually entered by the administrator.

 

Use these procedures to start the Create Application Wizard and to supply general information about the application.

 

To start the create application Wizard

1.       In the Configuration Manager console, click Software Library.

2.       In the Software Library workspace, expand Application Management, and then click Applications.

3.       On the Home tab, in the Create group, click Create Application.

 

To automatically detect application information

1.       On the General page of the Create Application Wizard, select Automatically detect this information using existing content.


 Note:

If you want to define this application information manually, see the procedure To manually define application information below.

 

2.       In the Type field, choose the application installation file type you want to use to detect application information. You can choose installation types for Windows Installer applications, virtual applications and mobile devices.

3.       In the Location field, specify the UNC path in the form \\<server>\<share>\<filename> to the application installation file you want to use to detect application information or click Browse to browse to the installation file location.

4.       Click Next.

5.       On the Import Information page of the Create Application Wizard, review the information that was imported and then click Next. You can also click Previous to go back and correct any errors.

6.       On the General Information page of the Create Application Wizard, specify the following information:


 Note:

Some of the application information might already be present if it was read from the application installation files.

 

·         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 and categories.

·         Installation program – Specify the installation program and any required properties needed to install the applications deployment type.

·         Install for user or System – 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.

7.       Click Next and then complete the Create Application Wizard.

 

To manually define application information

1.       On the General page of the Create Application Wizard, select Manually define the information and then click Next.

2.       On the General page of the Create Application Wizard, specify 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 and categories.

3.       Click Next.

4.       On the Application Catalog page of the Create Application Wizard, specify the following information:

·         Selected language – From the drop-down list, select the language version of the application that you want to configure. Click Add/Remove to configure more languages for this application.

·         Localized application name – Specify the application name in the language selected in the Selected Language drop-down list.

·         User categories – Click Edit to specify application categories in the language selected in the Selected Language drop-down list that users of the Application Catalog can use to help filter and sort the available applications.

·         User documentation – Click Browse to select a file that users of the Application Catalog can read to find out more information about this application.

·         Localized description – Enter a description for this application in the language selected in the Selected Language drop-down list.

·         Keywords – Enter a list of keywords in the language selected in the Selected Language drop-down list that users of the Application Catalog can use to help search for the application.

·         Icon – Click Browse to select an icon for this application from the available icons.

5.       Click Next.

6.       On the Deployment Types page of the Create Application Wizard, click Add to create a new deployment type.

7.       Click Next and then complete the Create Application Wizard.

 

 

How to Create Deployment Types in Configuration Manager 2012

To create deployment types in Microsoft System Center Configuration Manager 2012, use the Create Deployment Type Wizard. The steps to create a deployment type are different depending on whether you automatically import, or manually define deployment information.

 

Start the Create Deployment Type Wizard and Specify General Information about the Deployment Type

When you run the Create Deployment Type Wizard, there are two methods available to configure general information about the deployment type:

·         Automatically detect deployment type information – Configuration Manager attempts to read information about the deployment from the application installation files, and then automatically populates fields in the Wizard with discovered information.

·         Manually define deployment type information – Information about the deployment type is manually entered by the administrator.

 

Use these procedures to start the Create Deployment Type Wizard and to specify general information about the deployment type.

 

To Start the Create Deployment Type Wizard

1.       In the Configuration Manager console, click Software Library.

2.       In the Software Library workspace, expand Application Management, and then click Applications.

3.       Select an application and then, on the Home tab, in the Application group, click Create Deployment Type to create a new deployment type for this application.


 Note:

You can also start the Create Deployment Type Wizard from the Create Application Wizard and from the Deployment Types tab of the <application name>Properties dialog box.

 

 

To Automatically Detect Deployment Type Information

1.       On the General page of the Create Deployment Type Wizard, select Automatically discover this information from files in the application.


 Note:

If you want to define this application information manually, go to the procedure To manually define deployment type information below.

 

2.       In the Type field, choose the application installation file type you want to use to detect deployment type information. You can choose installation types for Windows Installer applications, virtual applications, mobile devices and scripts.

3.       In the Location field, specify the UNC path in the form \\<server>\<share>\<filename> to the application installation file you want to use to detect deployment type information or click Browse to browse to the installation file location.

4.       Click Next.

5.       On the Import Information page of the Create Deployment Type Wizard, review the information that was imported and then click Next. You can also click Previous to go back and correct any errors.

6.       On the General Information page of the Create Deployment Type Wizard, specify the following information:


 Note:

Some of the deployment type information might already be present if it was read from the application installation files.

 

·         General information -  Deployment type such as the name, comments and available languages.

·         Installation program – Specify the installation program and any required properties needed to install the deployment type.

·         Install for user or System – Specify whether the 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.

7.       Click Next and then continue to the procedure To specify deployment type requirements, below.

 

To Manually Define Deployment Type Information

1.       On the General page of the Create Deployment Type Wizard, select Manually define the information and then click Next.

2.       On the General Information page of the Create Deployment Type Wizard, specify a name for the deployment type, an optional description, the languages you want to make this deployment type available in, and then click Next.

 

Specify Content Options for the Deployment Type

The Content page of the Create Deployment Type Wizard contains options to configure the location of the deployment types content and information about the commands used to install and uninstall the content. Use this procedure to specify information about the content associated with your deployment type.

 

To Specify Content Options for the Deployment Type

1.       On the Content page of the Create Deployment Type Wizard, specify the following information:

·         Content location – Specify the location of any content for this deployment type or click Browse to choose the deployment type content folder.

·         Persist content in the client cache - 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.

·         Enable peer-to-peer content distribution – Select this option to reduce load on the network by allowing clients to download content from other clients on the network that have already downloaded and cached the content. This option utilizes Windows BrancheCache and can be used on computers running Windows Vista SP2 and later.

·         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, up to 127 characters. 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.

·         Uninstall program - Specify the name of the uninstall program and any required parameters or click Browse to browse to the uninstall file location.

·         Uninstall start in - Specifies the folder that contains the uninstall program for the deployment type, up to 127 characters. 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.

2.       Click Next.

 

Use Detection Methods to Indicate the Presence of this Application

A detection method in Configuration Manager 2012 contains rules that are used to check whether an application is already installed on a device. This detection occurs before the content is installed and at regular intervals afterwards. This can prevent Configuration Manager from needlessly reinstalling the application and can also detect if the application has been uninstalled by the user.

 

Use these procedures to configure detection methods in Configuration Manager 2012:

 

To Create a Detection Rule to Determine the Presence of an Application

1.       On the Detection Method page of the Create Deployment Type Wizard, select Describe the conditions that indicate the presence of this deployment type and then click Add Clause.

2.       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.

3.       Specify details about the item you want to use to detect whether this deployment type is installed. For example, you can use a file, folder, registry key or value, or a Windows Installer product code.

4.       Specify details about the value you want to assess against the item you are using to detect whether the deployment type is installed. For example, if you are using a file to determine whether the deployment type is installed, you can select The file system setting must exist on the target system to indicate presence of this application.

5.       Click Next to close the Detection Rule dialog box.

 

To Use a Custom Script to Determine the Presence of an Application

1.       On the Detection Method page of the Create Deployment Type Wizard, select Use a custom script to detect this deployment type and then click Edit.

2.       In the Script Editor dialog box, select the script language you want to use to detect the application from the Script type drop down list.

3.       Enter the script you want to use in the Script contents field. You can also paste the contents of an existing script in this field or click Open to browse to an existing saved script.

4.       Click OK to close the Script Editor dialog box.

5.       Click Next.

 

Specify User Experience Options for the Deployment Type

 

To Specify User Experience Options for the Deployment Type

1.       On the User Experience page of the Create Deployment Type Wizard, specify the following information:

·         Install for user or system – From the drop-down list, select one of the following options:

·         Install for user – The application installs for each new user who logs onto a device.

·         Install for System – The application installs only once and is available to all users.

·         Install for System if resource is device; otherwise install as user – If the application is deployed to a device then it will install for all users. If the application is deployed to a user then it will install for only that user.

·         Logon requirement - Specify the logon requirements for this deployment type from the following options:

·         Only when a user is logged on

·         Whether or not a user is logged on

·         Only when no user is logged on


 Note:

This option will default to Only when a user is logged on and cannot be changed if you have selected Install for user in the Install for user or system drop-down list.

 

·         Installation program visibility – Specifies the mode in which the deployment type will run on client devices. The following options are available:

·         Maximized – The deployment type runs maximized on client devices. Users will see all installation activity.

·         Normal - The deployment type runs in the normal mode based on system and program defaults. This is the default mode.

·         Minimized – The deployment type runs minimized on client devices. Users might see installation activity in the notification area or taskbar.

·         Hidden – The deployment type runs hidden on client devices and users will see no installation activity.

·         Allow users to interact with this program – Specifies whether a user can interact with the deployment type installation to configure installation options.


 Note:

This option is enabled by default if the option Install for user is selected in the Install for user or system drop-down list.

 

·         Maximum allowed run time (minutes) - Specifies the maximum time (in minutes) that the program is expected to run on the client computer. This setting can be specified as a whole number greater than zero.

The default setting is 120 minutes.

 This value is used for two purposes:

·         To monitor results from the deployment type.

·         To determine if a deployment type will be installed when maintenance windows have been defined on client devices.

Maintenance Windows

When a maintenance window is in place, a program will be launched only if there is time available remaining in the maintenance window to accommodate the Maximum Allowed Run Time setting.

 Important:

A conflict might occur if the Maximum allowed run time is longer than the scheduled maintenance window. If the maximum run time is set by the user to a period exceeding the length of any available maintenance window, that deployment type will not be run.

 

2.       Estimated install time (minutes) – Specify the estimated time that the deployment type will take to install. This is displayed to users of the Application Catalog.

3.       Click Next.

 

Specify Requirements for the Deployment Type

Requirements are used to specify minimum requirements that must be met before a deployment type can be installed on a client device. Use this procedure to add requirements to a Configuration Manager 2012 deployment type.

 

To Specify Deployment Type Requirements

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

2.       From the Select category drop-down list, select whether this requirement is for a device, a user or select Custom to use a previously defined global condition.

3.       From the Select a 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.

4.       From the Choose 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.

5.       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.

6.       Click OK to save the requirement rule and exit the Create Requirement dialog box.

7.       On the Requirements page of the Create Deployment Type Wizard, click Next.

 

Specify Dependencies for the Deployment Type

Dependencies define one or more deployment types 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. Use this procedure to configure dependencies in Configuration Manager 2012.

 

To Specify Deployment Type Dependencies

1.       On the Dependencies page of the Create Deployment Type Wizard, click Add if you want to specify deployment types that must be installed before this deployment type can be installed.

2.       In the Add Dependency dialog box, click Add.

3.       In the Specify Required Application dialog box, select an existing application and one of the application deployment types to use as a dependency.


 Note:

You can click View to display the properties of the selected application or deployment type.

 

4.       Click OK to close the Specify Required Application dialog box.

5.       If you want a dependent application to automatically install, check Auto Install next to the dependent application.

6.       In the Dependency group name field of the Add Dependency dialog box, enter a name to refer to this group of application dependencies.

7.       Optionally, use the Increase Priority and Decrease Priority buttons to change the order in which each dependency is evaluated.

8.       Click OK to close the Add Dependency dialog box.

9.       Click Next.

 

Confirm the Deployment Type Settings and Complete the Wizard

Use the following procedure to complete the Create Deployment Type Wizard.

1.       On the Summary page of the Create Deployment Type Wizard, review the actions that will be taken by the Wizard. Click Next to create the deployment type or click Previous to go back and change deployment type settings.

2.       After the Progress page of the Wizard completes, review the actions that have been taken, and then click Close to complete the Create Deployment Type Wizard.

3.       If you started this wizard from the Create Application Wizard, you will be returned to the Deployment Types page of the wizard.

 

How to Deploy Applications in Configuration Manager 2012

Before you can deploy an application in Microsoft System Center Configuration Manager 2012, you must create at least one deployment type for the application.

 

To deploy a Configuration Manager 2012 Application

1.       In the Configuration Manager console, click Software Library.

2.       In the Software Library workspace, expand Application Management, and then click Applications.

3.       In the Applications list, right-click the application you want to deploy and then click Deploy.

4.       On the General page of the Deploy Software Wizard, specify the following information:

·         Software – Displays the application you want to deploy. You can click Browse to select a different application to deploy.

·         Collection – Click Browse to select the collection you want to deploy the application to.

·         Use default distribution points associated to this collection – Select this option if you want to store the application content on the collections default distribution point group. If you have not associated the selected collection with a distribution point group, this option will be unavailable.

·         Automatically distribute content for dependencies – If any of the deployment types in the application contain dependencies then the dependent application content will be distributed.

·         Distribution Points – Click Browse to select the distribution points or distribution point groups that will store the content for the application. If you have selected Use default distribution points associated to this collection then this option will be automatically populated and cannot be modified unless you are a member of the Application Administrator security role.

·         Comments (optional) – Enter an optional description of this deployment.

5.       Click Next.

6.       On the Deployment Settings page of the Deploy Software Wizard, specify the following information:


 Note:

The options shown will vary depending on your selections.

 

·         Action – From the drop-down list, choose whether this deployment is intended to Install or Uninstall the application.

·         Purpose – From the drop-down list, choose one of the following options:

·         Available - If the application is deployed to a user, the user sees the published application in the Application Catalog and can request it on demand. If the application is deployed to a device, the user will see it in the Software Center and can install it on demand.

·         Required - The application is deployed automatically, according to the configured schedule. However, a user can track the application deployment status and install the application before the deadline by using the Software Center.

·         Simulated (Preflight) – This option is not currently fully implemented in Configuration Manager 2012.

·         Priority - Specifies the sending priority for the deployment content. The sending priority is used when content is sent to distribution points at child sites. Content is sent in priority order: High or Normal. Content with identical priorities is sent in the order in which it was created. By default, deployment content has a Normal sending priority.

·         Deploy automatically according to schedule with or without user login – If the deployment purpose is set to Required and this option is selected, the deployment will be installed whether or not a user is logged onto the device.

·         Send wake-up packets – If the deployment purpose is set to Required and this option is selected, a wake-up packet will be sent to computers before the deployment is installed to wake the computer from sleep at the installation deadline time. Before you can use this option, computers must be configured for Wake On LAN.

·         Require administrator approval if users request this application – If this option is selected, the administrator must approve any user requests for the application before it can be installed.

7.       Click Next.

8.       On the Scheduling page of the Deploy Software Wizard, configure when this application will be deployed or made available to client devices.


 Note:

The options on this page will differ depending on whether the deployment action is set to Install or Uninstall.

 

9.       Click Next.

10.   On the User Experience page of the Deploy Software Wizard, specify information about how users can interact with the application installation.


 Note:

These options will be unavailable if the deployment purpose is set to Available.

 

11.   Click Next.

12.   On the Alerts page of the Deploy Software Wizard, configure how Configuration Manager and Operations Manager will generate alerts for this deployment. You can configure thresholds for reporting and turn off reporting for the duration of the deployment.

13.   Click Next.

14.   On the Summary page of the Deploy Software Wizard, review the actions that will be taken, and then click Next to complete the Wizard.

 

 

How to Manage Application Revisions in Configuration Manager 2012

When you make revisions to an application or a deployment type contained in an application, Microsoft System Center Configuration Manager 2012, creates a new revision of the application. You can display the history of each revision made to an application, view its properties, restore a previous revision of an application, or delete an old revision.

 

To display an application revision history

1.       In the Configuration Manager console, click Software Library.

2.       In the Software Library workspace, expand Application Management, click Applications, and then click the application you want.

3.       On the Home tab, in the Application group, click Revision History to open the Application Revision History dialog box.

 

To view an application revision

1.       In the Application Revision History dialog box, select an application revision, and then click View.

2.       In the Properties dialog box examine the properties of the selected application.


 Note:

The application properties displayed are read-only.

 

3.       Close the Properties dialog box.

 

To restore an application revision

1.       In the Application Revision History dialog box, select an application revision, and then click Restore.

2.       In the Confirm Revision Restore dialog box, click Yes to restore the selected application revision.

 

To delete an application revision

1.       In the Application Revision History dialog box, select an application revision, and then click Delete.

2.       In the Delete Application Revision dialog box, click Yes.

 

How to Use Application Supersedence in Configuration Manager 2012

Application management in Microsoft System Center Configuration Manager 2012 allows you to upgrade or replace existing applications using a supersedence relationship. When you supersede an application, you can specify a new deployment type to replace the deployment type of the superseded application and also configure whether to uninstall the superseded application.

 

 Important:

When you supersede an application, this applies to all future deployments and Application Catalog requests. It will not affect current installations of the application.

 

 

To specify a supersedence relationship

1.       In the Configuration Manager console, click Software Library.

2.       In the Software Library workspace, expand Application Management, click Applications, and then click the application you want to supersede another application.

3.       On the Home tab, in the Properties group, click Properties to open the <Application Name>Properties dialog box.

4.       On the Supersedence tab of the <Application Name>Properties dialog box, click Add.

5.       In the Specify Supersedence Relationship dialog box, click Browse.

6.       In the Choose Application dialog box, select the application you want to supersede and then click OK.

7.       In the Specify Supersedence Relationship dialog box, select the deployment type that will replace the deployment type of the superseded application.


 Note:

By default, the new deployment type will not uninstall the deployment type of the superseded application. This scenario will commonly be used when you want to upgrade an existing application. Select Uninstall to remove the existing deployment type before the new deployment type is installed.

 

8.       Click OK to close the <Application Name>Properties dialog box.

 

To display applications that supersede the current application

1.       In the Configuration Manager console, click Software Library.

2.       In the Software Library workspace, expand Application Management, click Applications, and then click the application you want.

3.       On the Home tab, in the Properties group, click Properties to open the <Application Name>Properties dialog box.

4.       On the References tab of the <Application Name>Properties dialog box, select Applications that supersede this application from the Select a relationship type to review drop-down list.

5.       Review the list of applications that supersede the selected application, then click OK to close the <Application Name>Properties dialog box.

 

How to Uninstall Applications in Configuration Manager 2012

You can uninstall an application by using Microsoft System Center Configuration Manager 2012 when you perform the following steps:

·         Specify the command line to uninstall the deployment type content.

·         Deploy the application with the Uninstall action

 

To uninstall an application

1.       Configure the application deployment type with the uninstall command line by using one of the following methods:

·         On the General page of the Create Deployment Wizard, select the option Automatically discover this information from files in the application. If the information is available in the installation files, the uninstall command line is automatically added to the deployment type properties.

·         On the Content page of the Create Deployment Type Wizard, in the Uninstall program field, specify the command line to uninstall the application.


 Note:

The Content page is displayed only if you select the option Manually define the information on the General page of the Create Deployment Type Wizard.

 

·         In the Programs tab of the <deployment type name>Properties dialog box specify the command line to uninstall the application.

2.       Deploy the application and select the deployment action Uninstall from the Deployment Settings page of the Deploy Software Wizard.


 Note:

When you select a deployment action of Uninstall, the deployment purpose is automatically configured as Required.

 

 

Source: http://blogs.msdn.com/b/scstr/

Source: http://www.mycloud-tr.com/

İsmail Şen

Comments (6)

  1. Leif Alire says:

    Perfect explained what I needed for the following section "install for system if resource is device".

  2. Mikey says:

    Information is just Awesome. One of the best doc, which covers the step by step detailed procedure. Thankyou very much.

  3. Tuan says:

    Clarification question. Are the WOL packages sent at Software available time, or at Installation deadline? Thanks.

  4. Morteza says:

    What is the program schedule information

  5. Nitesh Sawant says:

    Hi,

    I am getting folloiwng error while importing package through SCCM 12 even though there is no dependent application. Error: "one or more dependent application could not be located"

  6. Tim says:

    Question:

    I am on SCCM 2012 and want to deploy applications to a technicians user group.  I would like these to be available in the software center.  We have only one local admin account to keep multiple technician profiles off of the computer.  Our technicians log in as local admin to perform administrative tasks.

    Ok so this all works IF the technician is logged in and goes to the software center.  But if the technician logs in as a local admin then opens the software center, it will not install the application.  How do I accomplish this?

    I would like three installation groups:

    1. For our users – which is easy and will work.

    2. For the Helpdesk – applications such as Adobe Flash, Reader, Shockwave, etc.

    3. For our Technicians – More complicated applications

    All based on software center permissions but install takes place under the local admin account.

    Is this possible?

Skip to main content