Product Documentation

To add an Enterprise Hub device policy for Windows Phone 8.1

Jun 24, 2015

An Enterprise Hub device policy for Windows Phone 8.1 lets you distribute apps through the Enterprise Hub Company store.

Before you can create the policy, you need the following:

  • An AET (.aetx) signing certificate from Symantec
  • The Citrix Company Hub app signed by using the Microsoft app signing tool (XapSignTool.exe)
Note: XenMobile supports only one Enterprise Hub policy for one mode of Windows Phone 8.1 Worx Home. For example, to upload Windows Phone 8.1 Worx Home for XenMobile Enterprise Edition, you should not create multiple Enterprise Hub policies with different versions of Work Home for XenMobile Enterprise Edition. You can only deploy the initial Enterprise Hub policy during device enrollment.
  1. In the XenMobile console, click Configure > Device Policies. The Device Policies page appears.


    Select Policies page

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


    Select Enterprise Hub

  3. Click More and then, under XenMobile agent, click Enterprise Hub. The Enterprise Hub Policy page appears.


    Enterpirse hub policy page

  4. In the Policy Information pane, enter the following information:
    1. Policy Name: Enter a descriptive name for the policy.
    2. Description: If desired, enter a description of the policy.
  5. Click Next. The Windows Phone 8.1 platform page appears.


    Enterprie hub policy Windows 8.1 Phone page

  6. Configure the following settings:
    1. Upload .aetx file: Browse to the location of the .aetx file and then select the file.
    2. Upload signed Enterprise Hub app: Browse to the location of the Enterprise Hub app and then select the app.
  7. 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

  8. Click Next. The Enterprise Hub Policy assignment page appears.
  9. 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.


    Policy assignment page

  10. 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

  11. Click Save to save the policy.