The following procedure shows you how to use the Create Package Wizard in Mobile Device Manager (MDM) Software Distribution Console to create a new package to distribute software to one or more managed Windows Mobile devices.

To distribute software packages to managed Windows Mobile devices, you must sign the .cab file and its contents by using certificates. For more information, see Signing CAB Files in Packages.

To create a new package

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

  2. Right-click the package group and then select Create.

  3. In the Create Package Wizard, choose Next.

  4. On the Software Packagepage, choose Browseto locate the file. Or, in the Filebox, enter the path and name of the file that you want to install.

  5. In the Package titlebox, enter a title and a description of the package in the Package descriptionbox, and then choose Next.

  6. On the Target Devicespage, select the managed device types that should receive the package.

    Or, select Allto have all types of managed devices receive the package. Choose Next.

  7. On the Permit Uninstallpage, select Yesif you want users to be able to uninstall the package from their managed devices.

    Or, select Noif you do not want users to be able to uninstall the package. Choose Next.

  8. On the Device Languagespage, select one or more languages that are supported by this package and allow it to be installed. Or, select All languagesif the package is valid for all languages. Choose Next.

  9. On the Software Dependenciespage, the packages listed are packages you already created in MDM Software Distribution Console. Select any packages that must be present on the managed device before the new package can be installed. Select No software dependenciesif the package does not require any other software to be present. Choose Next.

    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.
  10. On the Registry Dependenciespage, select one or more registry keys or data that must be on the managed device before the package can be installed. Choose Addto add a registry key or data to the list, type the registry information, and then choose OK. Select No registry dependenciesif the package does not require any registry key to be present on the managed device. Choose Next.

    You cannot test for binary registry data.
  11. On the Create Installation Packagepage, verify the Configuration Summaryinformation to make sure that all the information is correct. If it is necessary, you can choose the Backbutton to make changes. Choose Create.

  12. Choose Finishto close the wizard.

See Also