Modifying an Existing Package

2/9/2009

You can use the Modify Package Wizard in Mobile Device Manager Software Distribution Console to review and modify the package settings that you configured by using the Create Package Wizard.

Note

This procedure does not let you change the file that is contained in the package. To deliver a different file, you must create a new package.

To modify an existing package

  1. In the navigation pane, expand Packages, and then select Software Packages.

  2. In the details pane, right-click the package that you want to modify and then select Modify.

  3. In the Modify Package Wizard, on the Software Package page, choose Next to review and modify the package settings.

  4. On the Target Devices page, select which managed Windows Mobile devices should receive the package. If you want all the managed devices to receive the package, choose All. Or, select only the managed devices that should receive the package. Choose Next.

  5. On the Permit Uninstall page, choose Yes if you want users to be able to uninstall the package from their managed devices. Choose No if you do not want users to be able to uninstall the package from their managed devices. Choose Next.

  6. On the Device Languages page, select one or more languages that are required to be on the managed device before the package can be installed. If the package is valid for all languages, select All languages, and then choose Next.

  7. On the Software Dependencies page, select one or more packages that must be present on the managed device before the package can be installed. The packages listed are packages that you already created in MDM Software Distribution Console. If the package does not require other software to be present on the managed device, select No software dependencies. Choose Next.

    Note

    If you create a software package, for example Package 1, that has a dependency on another software package (Package 2), MDM Software Distribution will install Package 2 on the device then Package 1. If for some reason the installation of Package 2 fails, Package 1 will not be installed because of its dependency. This behavior is by design.

  8. On the Registry Dependencies page, select one or more registry keys or data that must be on the managed device before the package can be installed. To add a registry key or data to the list, choose Add, enter the registry information, and then choose OK. If the package requires no registry key to be present on the managed device, select No registry dependencies. Choose Next.

    Note

    You cannot test for binary registry data.

  9. On the Modify Installation Package page, verify the information in the Configuration Summary to make sure that all the information is correct. If not, you can choose Back to make adjustments. Choose Modify.

  10. Choose Finish to close the wizard.

See Also

Other Resources

Creating and Managing Packages