Product Documentation

Creating Deployment Packages

Mar 24, 2014
You can remotely deploy a package of settings to a mobile device from the Deployment tab in the web console. You can use the Package building wizard to build packages by using pre-configured objects. Connected devices receive the package as soon as scheduling rules are met. Reconnecting devices receive the package as they reconnect subject to other rule criteria.

Packages are compilations of previously created resources, prepared into configurations for the various user groups. Packages include the following:

  • A package name
  • Groups of users
  • Resources, which, depending on the operating device, are a combination of the following:
    • A server group
    • App tunnels
    • Registry configurations
    • XML configurations
    • Software inventory
    • Applications
    • Files
  • Deployment schedule
  • Deployment rules

How Base Packages Work

XenMobile contains preconfigured base deployment packages that enable basic device management. Device Manager automatically deploys the base packages to devices when users enroll. The policy configurations and applications in the base packages for each device platform are listed below. Note that the Windows 8.1 and Windows Phone 8 base packages are not listed because they are empty by default and are not deployed.

For more information about configuring policies, see Creating Device Manager Policies. For more information about deploying packages, see To create and deploy a deployment package.

iOS

  • Software inventory policy
  • Web clip policy for MyAppStore (Worx Home)
  • ShareFile
  • Citrix Receiver
  • GoToMeeting
  • Podio

Android

  • Scheduling policy for connections to XenMobile
  • XenMobile configuration policy for connection timers
  • Remote support tunnel
  • Shortcut policy for MyAppStore (Worx Home)
  • Software inventory policy
  • Citrix Receiver
  • GoToMeeting

Windows 8

  • Software inventory policy

Windows Mobile

  • Scheduling policy for connections to XenMobile
  • XenMobile configuration policy for connection timers
  • Software inventory policy

Symbian

  • Software inventory policy

To create a software inventory package

A software inventory policy in Device Manager enables you to check the following apps and software packages installed on a device:
  • iOS: All non-default apps
  • Android: All non-default apps
  • Windows: All apps installed by the XenMobile system
A software inventory policy exists inside of a Device Manager package. You can deploy the policy to any user group for any device platform.
  1. Click the Deployments tab and then click New Package > New <platform> package.
  2. On the Package Name page of the Create New Package wizard, enter a name for the policy and then click Next.
  3. On the Groups of users page, select the users whose devices you want to inventory and then click Next.
  4. On the Resources to be deployed page, in Available Resources, select the Software Inventory, click the right arrow to move Software Inventory into the Resources to Deploy column and then click Next.
  5. On the Deployment schedule page, configure the package to push Now or at a specified time in the future and then click Next.
  6. On the Deployment rules page, specify any deployment rules you want to associate with the package and its deployment and then click Next.
  7. On the Package summary page, review the configuration and then click Finish.

To deploy the package, select the package and then click Deploy. Connected devices receive the package as soon as scheduling rules are met.

To create and deploy a deployment package

  1. In the Device Manager management console, click the Deployment tab.
  2. On the New Package menu, select New <platform> package.
  3. On the Package Name page of the Create New Package wizard, enter a name for the app removal policy and then click Next.
  4. On the Groups of users page, select the users from whose devices you want to remove the app and then click Next.
  5. On the Resources to be deployed page, in Available Resources, select the app removal policy you want to use for the package and then click the right arrow button to add the resource to the package.
  6. Click Next.
  7. On the Deployment schedule page, configure to push the app now or at a specified time in the future.
  8. Click Next.
  9. On the Deployment rules page, specify any deployment rules you want to associate with the app and its deployment.
  10. Click Next.
  11. On the Package summary page, review the app removal package configuration and then click Finish.
  12. Click Deploy in the toolbar.

All connected devices receive all configured packages as soon as scheduling rules are met. Reconnecting devices receive the package when they connect subject to other rule criteria.

Configuring Deployment Rules

You can set any number of parameters that will affect the deployment outcome of a package.

For example, your package deployment could be based on a specific operating system version, on a particular hardware platform, or some other combination. In this wizard, you will find both a Simple and Advanced rule editor. The Advanced view is a free-form editor.

Simple Deployment Rules

Simple deployment rules are comprised of predefined tests and resulting actions. When possible, the results are pre-built into the example tests. For example, when basing a package deployment on a hardware platform, all existing known platforms are populated into the resulting test, drastically reducing your rule creation time and limiting possible errors.

Click New rule to add a rule to the package.
Note: The rule builder includes further information, specific to each test.

To create a new rule, you select a rule template, select the condition type, and then customize the rule. Customizing the rule includes modifying the description. When you finish configuring settings, you add the rule to the package.

You can add as many rules as you want. The package is deployed when all of the rules match.

Advanced Deployment Rules

If you click on the Advanced tab, the Advanced Rule Editor appears.

In this mode, you can specify what relationship is set between the rules. The operators AND, OR, and NOT are available.

Configuring Deployment Schedules

The deployment schedule allows you to define when to deploy a package.

You can schedule the deployment in the following ways:

  • For a future time (do not deploy).
  • For a single deployment (one time).
  • As a permanent deployment to make sure that the devices always have the package content (on every connection). This is designed to ensure that the devices initially and continue to comply with your application policies.

The available options might change depending on the platform type.

You can configure the schedule to make sure that a package is only deployed one time. For example, if users change deployment settings, the package will not deploy again.

The windows differ by device type. For Windows Mobile devices, the window appears as follows:

Important: Some devices may not observe the schedule. When selecting a precise date for the deployment, the targeted devices receive the information to try to reconnect during that time frame, even if they do not have a connection scheduling in place during the specified time frame. However, if the device does not connect or connects later than the configured time frame, the device does not receive the package.

Configuring Deployment Schedules

The deployment schedule allows you to define when to deploy a package.

You can schedule the deployment in the following ways:

  • For a future time (do not deploy).
  • For a single deployment (one time).
  • As a permanent deployment to make sure that the devices always have the package content (on every connection). This is designed to ensure that the devices initially and continue to comply with your application policies.

The available options might change depending on the platform type.

You can configure the schedule to make sure that a package is only deployed one time. For example, if users change deployment settings, the package will not deploy again.

The windows differ by device type. For Windows Mobile devices, the window appears as follows:

Important: Some devices may not observe the schedule. When selecting a precise date for the deployment, the targeted devices receive the information to try to reconnect during that time frame, even if they do not have a connection scheduling in place during the specified time frame. However, if the device does not connect or connects later than the configured time frame, the device does not receive the package.

Configuring Package Hierarchy and Relationship Rules

Hierarchy rules apply to assignments between packages and sub-packages. The following table shows how user group and package structures work.

User Group Structure Package Structure
ABC (Group parent)
  • Marketing (Group child)
  • R&D (Group child)
  • Admin (Group child)
XYZ
  • Marketing
  • RD
  • Admin

Scenario 1: If the assignment was made at the parent package level, but not at the sub-package level, the latter inherits its parent package assignments. The conditions are:

  • The XYZ package is not assigned to a specific group.
  • The Marketing, R&D, and Admin sub-packages are assigned to the ABC.Marketing, ABC.RD, and ABC.Admin subgroups, respectively.

The result is that the ABC Marketing, ABC RD, and ABC.Admin subgroups inherit from the XYZ package solely because this package is not assigned.

Scenario 2: If the assignment was made at the parent package level, as well as at that of the sub-package, the latter retrieves its own assignments alone. The conditions are:

  • The XYZ package is assigned to the ABC group.
  • The Marketing, R&D, and Admin sub-packages are assigned to the ABC.Marketing, ABC.RD, and ABC.Admin subgroups, respectively.

The result is that the ABC.Marketing, ABC.RD and ABC.Admin subgroups do not inherit from the XYZ package.

Note: You can restrict the deployment of a package to a subset of devices within the selected user group, by defining rules.