System Center
United States (English) Sign in
Home 2012 Previous Versions Library Forums Gallery
1 out of 5 rated this helpful - Rate this topic

How to Create Deployment Types in Configuration Manager

Updated: January 1, 2013

Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1

Use the following steps to create a deployment type by using Microsoft System Center 2012 Configuration Manager.

Use the following table for the steps, details, and more information about how to create a deployment type.

noteNote
If you select Automatically identify information about this deployment type from installation files on the General page of the Create Deployment Type Wizard, then you do not need to complete some of the steps in the following procedures.

 

Step Details More information

Step 1: Start the Create Deployment Type Wizard.

See Step 1: Start the Create Deployment Type Wizard in this topic.

Step 2: Specify whether you want to automatically detect or to manually define the deployment type information.

There are two methods that you can use to configure general information about the deployment type:

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

  • Manually configure the deployment type information – The information about the deployment type is manually entered by the administrator.

See Step 2: Specify whether you want to Automatically Detect Deployment Type Information or Manually Define the Information in this topic.

Step 3: Specify the content options for the deployment type.

The Content page of the Create Deployment Type Wizard contains options to configure the location of the deployment type content and information about the commands that are used to install and uninstall the content.

See Step 3: Specify Content Options for the Deployment Type in this topic.

Step 4: Configure the detection methods to indicate the presence of the application.

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

See Step 4: Configure Detection Methods to Indicate the Presence of the Application in this topic.

Step 5: Specify the user experience options for the deployment type.

Specify information about the behavior of the deployment type when it is installed on devices.

See Step 5: Specify User Experience Options for the Deployment Type in this topic.

Step 6: Specify the requirements for the deployment type.

Requirements are used to specify the conditions that must be met before a deployment type can be installed on a client device.

See Step 6: Specify Requirements for the Deployment Type in this topic.

Step 7: Specify the dependencies for the deployment type.

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

See Step 7: Specify Dependencies for the Deployment Type in this topic.

Step 8: Confirm the deployment type settings and complete the wizard.

After you perform all the steps, confirm the settings that you selected for the deployment type, and complete the wizard.

See Step 8: Confirm the Deployment Type Settings and Complete the Wizard in this topic.

Step 9: Configure additional options for the deployment types that contain virtual applications.

After you create a deployment type you can configure additional options that control the content and publishing options for the deployment types that contain virtual applications.

See Step 9: Configure Additional Options for Deployment Types that contain Virtual Applications in this topic.

Use the following information when the steps in the preceding table require supplemental procedures.

ImportantImportant
Depending on the type of deployment type you are creating, not all of the options in the wizard will be available.

  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.

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

Use one of the following procedures to automatically detect, or to manually define deployment type information.

  1. On the General page of the Create Deployment Type Wizard, select Automatically identify information about this deployment type from installation files.

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

  2. In the Type field, choose the application installation file type that you want to use to detect the deployment type information. You can choose from the following installation types.

     

    Installation type More information

    Windows Installer (Native) (Configuration Manager with no service pack)

    Windows Installer (*.msi file) (Configuration Manager SP1)

    Detects application information and deployment types from a Windows Installer (.msi) file.

    For Configuration Manager SP1 only:

    Windows app package (.appx file)

    Detects application information and deployment types from a Windows app package (.appx) file.

    ImportantImportant
    Because Windows XP does not support the libraries required to create an application of this type, you cannot create a Windows app package application from a Configuration Manager console running on a Windows XP computer.

    For Configuration Manager SP1 only:

    Windows app package (in the Windows Store)

    Detects application information and deployment types by providing a link to the application on a computer where the application is already installed.

    noteNote
    To be able to connect to the Windows Store, users of client computers must have a valid account.

    Script Installer (Native) (Configuration Manager with no service pack)

    Script Installer (Configuration Manager SP1)

    Specifies a script that runs on client devices to install content or to perform an action.

    Microsoft Application Virtualization (Configuration Manager with no service pack)

    Microsoft Application Virtualization 4 (Configuration Manager SP1)

    Detects application information and deployment types from a Microsoft Application Virtualization 4 manifest (.xml) file.

    For Configuration Manager SP1 only:

    Microsoft Application Virtualization 5

    Detects application information and deployment types from a Microsoft Application Virtualization 5 (.appv) package file.

    For Configuration Manager SP1 only:

    Windows Phone app package (*.xap file)

    Detects application information and deployment types from a Windows Phone app package (.xap) file.

    For Configuration Manager SP1 only:

    Windows Phone app package (in the Windows Phone Store)

    Configures application and deployment type information by specifying a link to the app in the Windows Phone Store.

    Windows Mobile Cabinet

    Detects application information and deployment types from a Windows Mobile cabinet (.cab) file.

    For Configuration Manager SP1 only:

    App package for iOS (*.ipa file)

    Detects application information and deployment types from an app package for iOS (.ipa) file.

    For Configuration Manager SP1 only:

    App package for iOS from App Store

    Configures application and deployment type information by specifying a link to the app in the App Store.

    For Configuration Manager SP1 only:

    App package for Android (*.apk file)

    Detects application information and deployment types from an app package for Android (.apk) file.

    For Configuration Manager SP1 only:

    App package for Android on Google Play

    Configures application and deployment type information by specifying a link to the app on Google Play.

    Nokia SIS file

    Detects application information and deployment types from a Nokia Symbian installation (.sis or .sisx) file.

    For Configuration Manager SP1 only:

    Mac OS X

    Detects application information and deployment types from a Mac OS X Installer (.cmmac) file that was created by using the CMAppUtil tool.

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

    noteNote
    You must have access to the UNC path that contains the application and any subfolders that contain the application content.

  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:

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

    • Specify general information about the deployment type, such as the name, administrator comments, and available languages.

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

    • Install behavior – 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 that the deployment type will be installed to a user only if it is deployed to a user.

  7. Click Next, and then continue to the procedure in Step 6: Specify Requirements for the Deployment Type.

  1. On the General page of the Create Deployment Type Wizard, select Manually specify the deployment type information.

    noteNote
    If you want to automatically retrieve the deployment type information, go to the procedure To automatically detect the deployment type information.

  2. In the Type field, choose the application installation file type that you want to use to detect the deployment type information. You can choose the same installation types that you would use when you automatically detect the deployment type information, and you can additionally specify a script to install the deployment type.

  3. Click Next.

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

  5. Continue to Step 3: 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 the content for this deployment type, or click Browse to choose the deployment type content folder.

      ImportantImportant
      The System account of the site server computer must have permissions to the content location that you specify.

    • Persist content in the client cache - Specifies whether the 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 to be available for applying updates, it will reduce the available cache space. If you specify this option, it might cause a large deployment to fail at a later point if the cache does not have sufficient available space.

    • Allow clients to share content with other clients on the same subnet – 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 it can be used on computers that run 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. 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.

    • 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 that is relative to the distribution point folder that contains the package. This field is optional.

  2. Click Next.

  1. On the Detection Method page of the Create Deployment Type Wizard, select Configure rules to detect the presence of this deployment type and then click Add Clause.

    noteNote
    You can also select Use a custom script to detect the presence of this deployment type. For more information, see the To use a custom script to determine the presence of a deployment type section in this topic.

  2. In the Setting type drop-down list of the Detection Rule dialog box, choose the method that you want to use to detect the presence of the deployment type. You can choose from the following available methods:

    • File System – This method allows you to detect whether a specified file or folder exists on a client device, thus indicating that the application is installed.

      noteNote
      The File system setting type does not support specifying a UNC path to a network share in the Path field. You can only specify a local path on the client device.

      noteNote
      Select the option This file or folder is associated with a 32-bit application on 64-bit systems to check 32-bit file locations for the specified file or folder first. If the file or folder is not found, then 64-bit locations will be searched.

    • Registry – This method allows you to detect whether a specified registry key or registry value exists on a client device, thus indicating that the application is installed.

      noteNote
      Select the option This registry key is associated with a 32-bit application on 64-bit systems to check 32-bit registry locations for the specified registry key first. If the registry key is not found, then 64-bit locations will be searched.

    • Windows Installer – This method allows you to detect whether a specified Windows Installer file exists on a client device, thus indicating that the application is installed.

  3. Specify details about the item that 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 that you want to assess against the item that you use to detect whether the deployment type is installed. For example, if you use 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.

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

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

  3. Enter the script that 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. Configuration Manager determines the results from the script by reading the values that are written to STDOUT, STDERR, and the exit code from the script. If the exit code is a non-zero value, then the script has failed and the application detection status is unknown. If the exit code is zero and STDOUT contains data, then the application detection state is installed.

    Use the following table to determine how you can use the output from a script to determine if an application is installed:

     

    Script exit code Data read from STDOUT Data read from STDERR Script result Application detection state

    0

    Empty

    Empty

    Success

    Not installed

    0

    Empty

    Not empty

    Failure

    Unknown

    0

    Not empty

    Empty

    Success

    Installed

    0

    Not empty

    Not empty

    Success

    Installed

    Non-zero value

    Empty

    Empty

    Failure

    Unknown

    Non-zero value

    Empty

    Not empty

    Failure

    Unknown

    Non-zero value

    Not empty

    Empty

    Failure

    Unknown

    Non-zero value

    Not empty

    Not empty

    Failure

    Unknown

    The following table contains Visual Basic (VB) script sample code that you can use to write your own application detection scripts:

     

    VB script sample Description

    WScript.Quit(1)

    The script returns an exit code that is not zero, which indicates that it failed to run successfully. In this case, the application detection state is unknown.

    WScript.StdErr.Write "Script failed"

    WScript.Quit(0)

    The script returns an exit code of zero, but the value of STDERR is not empty, which indicates that the script failed to run successfully. In this case, the application detection state is unknown.

    WScript.Quit(0)

    The script returns an exit code of zero, which indicates that it ran successfully. However, the value for STDOUT is empty, which indicates that the application is not installed.

    WScript.StdOut.Write "The application is installed"

    WScript.Quit(0)

    The script returns an exit code of zero, which indicates that it ran successfully; and the value for STDOUT is not empty which, indicates that the application is installed.

    WScript.StdOut.Write "The application is installed"

    WScript.StdErr.Write "Completed"

    WScript.Quit(0)

    The script returns an exit code of zero, which indicates that it ran successfully; and the values for STDOUT and STDERR are not empty, which indicates that the application is installed.
    noteNote
    The maximum size that you can use for a script is 32 KB.

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

  5. Click Next.

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

    • Installation behavior – From the drop-down list, select one of the following options:

      • Install for user – The application installs only for the user to whom the application is deployed.

      • Install for System – The application installs only once and it 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

      noteNote
      This option will default to Only when a user is logged on, and it cannot be changed if you selected Install for user in the Installation behavior 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 the 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 the installation options.

      noteNote
      This option is enabled by default if you selected the Install for user option in the Installation behavior drop-down list.

    • Maximum allowed run time (minutes) - Specifies the maximum time 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 the results from the deployment type.

      • To determine if a deployment type will be installed when maintenance windows are defined on client devices.

        Maintenance Windows

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

        ImportantImportant
        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 that exceeds the length of any available maintenance window, that deployment type will not be run.

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

  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.

    noteNote
    You can also add new requirements on the Requirements tab of the <deployment type name>Properties dialog box.

  2. From the Category drop-down list, select whether this requirement is for a device or 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. For more information about global conditions, see How to Create Global Conditions in Configuration Manager.

    ImportantImportant
    If you create a requirement of the category User and the condition Primary Device, and then deploy the application to a device collection, the requirement will evaluate as false.

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

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

    ImportantImportant
    The available requirements will differ depending on the device type the deployment type is for.

  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.

Dependencies define one or more deployment types from another application that must be installed before a deployment type is installed. You can configure the dependent deployment types to install automatically before a deployment type is installed. Use this procedure to configure dependencies in Configuration Manager.

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

    noteNote
    You can also add new dependencies on the Dependencies tab of the <deployment type name>Properties dialog box.

  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.

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

    noteNote
    A dependent application does not need to be deployed to be automatically installed.

  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.

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 the deployment type settings.

  2. After the Progress page of the wizard completes, review the actions that were 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. For more information, see How to Create Applications in Configuration Manager.

Use the following procedures to configure additional options for deployment types that contain virtual applications.

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

  2. In the Software Library workspace, click Applications.

  3. In the Applications list, select an application that contains an App-V deployment type and then, in the Home tab, in the Properties group, click Properties.

  4. On the Deployment Types tab of the <Application Name>Properties dialog box, select an App-V deployment type and then click Edit.

  5. In the Content tab of the <Deployment Type Name>Properties dialog box, configure the following options if required:

    • Persist content in the client cache – Select this option to ensure that the content for this deployment type is not deleted from the Configuration Manager client cache.

    • Load content into App-V cache before launch – Select this option to ensure that all content for the virtual application is loaded into the App-V cache before the application is launched. Selection of this option also ensures that the application content is not pinned in the cache and can be deleted as required.

  6. Click OK to close the <Deployment Type Name>Properties dialog box.

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

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

  2. In the Software Library workspace, click Applications.

  3. In the Applications list, select an application that contains an App-V deployment type and then, in the Home tab, in the Properties group, click Properties.

  4. On the Deployment Types tab of the <Application Name>Properties dialog box, select an App-V deployment type and then click Edit.

  5. On the Publishing tab of the <Deployment Type Name>Properties dialog box, select the items in the virtual application that you want to publish.

  6. Click OK to close the <Deployment Type Name>Properties dialog box.

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

-----
For additional resources, see Information and Support for Configuration Manager.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012 Configuration Manager. For instructions and examples, see Search the Configuration Manager Documentation Library.
-----
Did you find this helpful?
(1500 characters remaining)
© 2013 Microsoft
|
Site Feedback
© 2013 Microsoft. All rights reserved.