Product Documentation

Connection scheduling device policies

Jun 23, 2015

You create connection scheduling policies to control how and when users' Android and Symbian devices connect to XenMobile. You can specify that users connect their devices manually, that devices stay connected permanently, or that devices connect within a defined time frame.

  1. In the XenMobile console, click Configure > Device Policies. The Device Policies page appears.


    Device policies page

  2. Click Add to add a new policy. The Add New Policy dialog box appears.


    Select connection scheduling

  3. Click Scheduling. The Connection Scheduling Policy information page appears.
  4. In the Policy Information pane, enter the following information:
    1. Policy Name: Type a descriptive name for the policy.
    2. Description: Type an optional description of the policy.
  5. Click Next. The Policy Platforms page appears.
    Note: When the Policy Platforms page appears, both platforms are selected and you see the Android platform configuration panel first.
  6. Under Platforms, select the platforms you want to add.
  7. Configure the following settings for each of the platforms you selected: Require devices to connect: Click the option you want to set for this schedule.
    • Always: Keep the connection alive permanently. XenMobile on the user's device attempts to reconnect to the XenMobile server after a network connection loss and will monitor the connection by transmitting control packets at regular intervals.

      This option is not recommended as it drains battery power and generates a lot of network traffic.

    • Never: Connect manually. Users must initiate the connection from XenMobile on their devices.
    • Every: Connect at the designated interval. Devices automatically connect after a defined number of minutes.

      When you select this option, the Connect every N minutes field appears where you must enter the number of minutes after which the device must reconnect. The default is 20.

    • Define schedule: XenMobile on the user's device attempts to reconnect to the XenMobile server after a network connection loss and will monitor the connection by transmitting control packets at regular intervals within the time frame you define. The following section describes how to define a connection time frame.

      To define a connection time frame

      When you enable the following options, a timeline appears where you can define the time frames you want. You can enable either or both options to require a permanent connection during specific hours or to require a connection within certain time frames. Each square in the timeline is 30 minutes, so if you want a connection between 8:00 AM and 9:00 AM every weekday, you click the two squares on the timeline between 8 AM and 9 AM every weekday.

      For example, the two timelines in the following figure require a permanent connection between 8:00 AM and 9:00 AM every weekday, a permanent connection between 12:00 AM Saturday and 1:00 AM Sunday, and at least one connection every weekday between 5:00 AM and 8:00 AM or between 10:00 AM and 11:00 PM.


      Connection scheduling timeline

      Maintain permanent connection during these hours: Users' devices must be connected for the defined time frame.

      Require a connection within each of these ranges: Users' devices must be connected at least once in any of the defined time frames.

      Use local device time rather than UTC: Synchronize the defined time frames to local device time rather than Coordinated Universal Time (UTC).

  8. Expand Deployment Rules and then configure the following settings: The Base tab appears by default.


    Deployment rules

    1. In the lists, click options to determine when the policy should be deployed.
      1. You can choose to deploy the policy when all conditions are met or when any conditions are met. The default option is All.
      2. Click New Rule to define the conditions.
      3. In the lists, click the conditions, such as Device ownership and BYOD, as shown in the preceding figure.
      4. Click New Rule again if you want to add more conditions. You can add as many conditions as you would like.
    2. Click the Advanced tab to combine the rules with Boolean options.


      Advanced deployment rules with base rules

      The conditions you chose on the Base tab appear.
    3. You can use more advanced Boolean logic to combine, edit, or add rules.
      1. Click AND, OR, or NOT.
      2. In the lists that appear, choose the conditions that you want to add to the rule and then click the Plus sign (+) on the right-hand side to add the condition to the rule.

        At any time, you can click to select a condition and then click EDIT to change the condition or Delete to remove the condition.

      3. Click New Rule again if you want to add more conditions.

        In this example, the device ownership must be BYOD, the device local encryption must be True, and the device mobile country code cannot be only Andorra.

        Advanced deployment rules complete

  9. Click Next. The Connection Scheduling Policy assignment page appears.
  10. Next to Choose delivery groups, type to find a delivery group or select a group or groups in the list to which you want to assign the policy. The groups you select appear in the right-hand Delivery groups to receive app assignment list.
  11. Expand Deployment Schedule and then configure the following settings:
    1. Next to Deploy, click ON to schedule deployment or click OFF to prevent deployment. The default option is ON. If you choose OFF, no other options need to be configured.
    2. Next to Deployment schedule, click Now or Later. The default option is Now.
    3. If you click Later, click the calendar icon and then select the date and time for deployment.
    4. Next to Deployment condition, click On every connection or click Only when previous deployment has failed. The default option is On every connection.
    5. Next to Deploy for always-on connection, click ON or OFF. The default option is OFF.
      Note: This option applies when you have configured the scheduling background deployment key in Settings > Server Properties. The always-on option is not available for iOS devices.
    Note: The deployment schedule you configure is the same for all platforms. Any changes you make apply to all platforms, except for Deploy for always on connection, which does not apply to iOS.


    Deployment schedule

  12. Click Save to save the policy.