Share via

  • Article

How to Analyze and Convert Packages in Package Conversion Manager

 

Updated: February 1, 2012

Applies To: System Center 2012 Configuration Manager

Use the information in this topic to help you use Microsoft System Center Configuration Manager Package Conversion Manager to analyze and convert packages to System Center 2012 Configuration Manager applications.

Before you can convert a package, you must first analyze it. Depending on the results of the analysis, you can then perform one of the following tasks:

  • Convert the package to an application.

    On the Package list in the console, the readiness state displays Automatic.

  • Fix and Convert the package, attach collections and create global conditions.

    On the Package list in the console, the readiness state displays Automatic.

  • Fix and Convert the package.

    On the Package list in the console, the readiness state displays Manual.

  • Leave the package unconverted.

    On the Package list in the console, the readiness state displays Not Applicable.

How to analyze packages

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

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

  3. Select the package you want to convert and then, on the Home tab, in the Package group, click Analyze Package.

    The package is analyzed and the readiness state of the package is displayed in the list of packages.

    - To convert a package with a readiness state of **Automatic**, see How to convert packages.

- To convert a package with a readiness state of **Automatic**, attach collections, create global conditions, or both, see How to fix and convert packages.

- To convert a package with a readiness state of **Manual**, see How to fix and convert packages.

- A package with a readiness state of **Not Applicable** is missing required content or a program. Add any missing content or programs, or you can leave it in an unconverted state and continue to deploy it as a package.

How to convert packages

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

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

  3. Select the package you want to convert with a readiness state of Automatic, and then, on the Home tab, in the Package group, click Convert Package.

    The Convert Package to Application wizard opens.

  4. In the Convert Package to Application wizard, review the list of Selected Packages, remove any that you do not want to be converted, and then click OK.

    The package is converted and then, in the Conversion complete window, the Conversion Status of the applications produced is listed.

    Note

    When a package is converted, the date/time of the conversion is recorded as the UTC time.

  5. Follow the instructions in the window, and click either View applications or Close.

How to fix and convert packages

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

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

  3. Select a package with a readiness state of Manual or Automatic, and then, on the Home tab, in the Package group, click Fix and Convert.

  4. In the Package Conversion Wizard, review the information on the Package Selection page, noting the Items to Fix.

  5. Click Next.

  6. In the Dependency Review page of the Wizard, review whether the package you are converting is dependent on other listed packages.

    Note

    If any of the listed dependent packages have not yet been converted, convert those packages, and then restart the package conversion process.

    If a dependency is not required, you can delete it, or, you can ignore it and continue the conversion.

  7. Click Next.

  8. In the Deployment Type page of the Wizard, review the deployment types that will be contained in the new application. You can change the priorities of the deployment types, and you can delete deployment types.

  9. If any of the listed deployment types does not have a detection method associated with it, a warning icon is displayed in the Detection Method column, and you must perform the following actions:

    1. Click Edit Detection Method.

    2. In the dialog box, click Add.

    3. In the Detection Rule dialog box, specify a Setting Type.

    4. For the setting type you specified, enter the additional information required for the detection rule.

    5. Click OK.

      Tip

      You can add multiple detection rules to each deployment type.

    6. Click OK, and then verify that an icon is displayed in the Detection Method column to confirm that the detection method was correctly specified.

  10. Click Next.

  11. In the Requirements Selection page, review the deployment types contained in the application you are creating. When you select a deployment type, the requirements for that deployment type are displayed.

    Note

    The requirements displayed are only those that are converted by Package Conversion Manager. Not all WQL queries in device collection are converted to requirements.

  12. If you want to add requirements for a selected deployment type, enable the required check boxes.

  13. Click Next.

  14. In the Summary page of the Wizard, review details about the application that will be created. If you want to change any of the details, click Previous, otherwise, click Next.

    The application is created and the Completion page opens.

  15. Verify the details of the new application and then complete the Wizard.

    Note

    When a package is converted, the date/time of the conversion is recorded as the UTC time.