Distribute Android Enterprise apps 编辑

XenMobile manages apps deployed to devices. You can organize and deploy the following types of Android Enterprise apps.

• Managed app store apps: These apps include free apps available in the managed Google Play Store. For example, GoToMeeting.
• MDX: Apps prepared with the MAM SDK or wrapped with the MDX Toolkit. These apps include MDX policies. You get MDX apps from internal sources and public stores. Deploy Citrix mobile productivity apps as MDX apps.
• Enterprise: Private apps you develop or obtain from another source. You provide these apps to your users through the managed Google Play Store. The managed Google Play Store is the Google enterprise app store.
• MDX-enabled private apps: Enterprise apps prepared with the MAM SDK or wrapped with the MDX Toolkit.

You can add enterprise apps and MDX-enabled private apps two different ways.

• Add the apps to the XenMobile console as enterprise apps, as described in the Enterprise apps and MDX-enabled private apps sections in this article.
• Publish the apps directly to the managed Google Play Store using your Google developer account. Then add the apps to the XenMobile console as managed app store apps. See Managed app store apps.

If you publish apps using your Google developer account and then switch to using the XenMobile console, the ownership of the apps differs. Manage your apps in both locations, in this case. Citrix recommends adding your apps using one method or the other.

If you need to remove self-managed apps from the managed Google Play Store, open a ticket with Google. Developers can disable, but not delete, apps from the managed Google Play Store.

The following sections provide more in depth information for Android Enterprise app configuration. For information about distributing apps, see Add Apps. That article includes:

• The general workflows for adding web and SaaS apps or web links
• The required app workflow for enterprise and public store apps
• How to deliver enterprise apps from the Citrix Content Delivery Network (CDN) for Enterprise Apps

Managed app store apps

You can add free apps available on the managed Google Play Store to XenMobile.

Note:

To make all apps in the Google Play store accessible from managed Google Play, use the Access all apps in the managed Google Play store server property. See Server properties. Setting this property to true allows all Android Enterprise users to access public Google Play store apps. You can then use the Restrictions device policy to control access to these apps.

Step 1: Add and configure apps

1. In the XenMobile console, navigate to Configure > Apps. Click Add.

2. Click Public App Store.

   

3. In the App Information pane, type the following information:

   • Name: Type a descriptive name for the app. The name appears under App Name on the Apps table.
   • Description: Type an optional description of the app.
   • App category: Optionally, in the list, click the category to which you want to add the app. For more information about app categories, see About app categories.

4. Select Android Enterprise as the platform.

5. Type the app name or package ID in the search box and click Search. You can locate the package ID in the Google Play store. The ID is in the URL of the app. For example, com.Slack is the package ID in https://play.google.com/store/apps/details?id=com.Slack&hl=en_US.

   

6. Apps matching the search criteria appear. Click the desired app then click Approve.

   

7. Click Approve again.

8. Select Keep approved when app requests new permissions. Click Save.

   

9. Click the app icon and configure the app Name and Description.

   

10. Assign any delivery groups to the app and click Save. For information, see Deploy resources.

Step 2: Configure app deployment

1. Navigate to Configure > Delivery Groups and select the delivery group you configured. Click Edit.
2. In the Apps section, drag the desired apps to the Required Apps box.
3. On the Summary page, click Save.
4. On the Delivery Groups page, select the delivery group and click Deploy.

MDX apps

Add MDX files to XenMobile and configure app details and policy settings. To configure Citrix mobile productivity apps for Android Enterprise, add them as MDX apps. For information about the app policies that are available for each device platform type, see:

• MAM SDK overview
• MDX Policies at a Glance

Step 1: Add and configure apps

1. For Citrix mobile productivity apps, download the public-store MDX files: Go to https://www.citrix.com/downloads. Navigate to Citrix Endpoint Management (XenMobile) > Citrix Endpoint Management Productivity Apps.

   For other types of MDX apps, obtain the MDX file.

2. In the XenMobile console, click Configure > Apps. Click Add. The Add App dialog box appears.

   

3. Click MDX. The MDX App Information page appears. In the App Information pane, type the following information:

   • Name: Type a descriptive name for the app. The name appears under App Name on the Apps table.
   • Description: Type an optional description of the app.
   • App category: Optionally, in the list, click the category to which you want to add the app. For more information about app categories, see About app categories.

4. Select Android Enterprise as the platform.

5. Click Upload and navigate to the MDX file. Android Enterprise only supports apps prepared with the MAM SDK or MDX Toolkit.

   • The UI notifies you if the attached application requires approval from the managed Google Play Store. To approve the application without leaving the XenMobile console, click Yes.

     

     After the managed Google Play Store opens, follow the instructions to approve and save the app.

     

     When you successfully add the app, the App details page appears.

6. Configure these settings:

   • File name: Type the file name associated with the app.
   • App Description: Type a description for the app.
   • App version: Optionally, type the app version number.
   • Package ID: Type the package ID for the app, obtained from the managed Google Play Store.
   • Minimum OS version: Optionally, type the oldest operating system version that the device can run to use the app.
   • Maximum OS version: Optionally, type the most recent operating system that the device must run to use the app.
   • Excluded devices: Optionally, type the manufacturer or models of devices that cannot run the app.

7. Configure the MDX Policies. MDX policies vary by platform and include options for policy areas, including authentication, device security, and app restrictions. In the console, each of the policies has a tooltip that describes the policy. For information about the app policies that are available for each device platform type, see:

   • MAM SDK overview
   • MDX Policies at a Glance

8. Configure the deployment rules and store configuration.

9. Assign any delivery groups to the app and click Save. For information, see Deploy resources.

Step 2: Configure app deployment

1. Navigate to Configure > Delivery Groups and select the delivery group you configured. Click Edit.

2. In the Apps section, drag the desired apps to the Required Apps box.

   

3. On the Summary page, click Save.

4. On the Delivery Groups page, select the delivery group and click Deploy.

Enterprise apps

Enterprise apps represent private apps that are not prepared with the MAM SDK or MDX Toolkit. You develop these apps yourself or obtain them directly from other sources. To add an enterprise app, you need the APK file associated with the app. Ensure that you follow Google Best practices for private apps.

Step 1: Add and configure apps

Add the app one of two ways:

• Publish the app directly to the managed Google Play Store and add it to the XenMobile console as a Managed play store app. Follow the Google documentation on how to Publish private apps, and then follow the steps in the Managed app store apps section.
• Add the app to the XenMobile console as an enterprise app. Perform the following steps:

1. In the XenMobile console, click Configure > Apps. Click Add. The Add App dialog box appears.

   

2. Click Enterprise. In the App Information pane, type the following information:

   • Name: Type a descriptive name for the app. This name is listed under App Name on the Apps table.
   • Description: Type an optional description of the app.
   • App category: Optionally, in the list, click the category to which you want to add the app. For more information about app categories, see About app categories.

3. Select Android Enterprise as the platform.

4. The Upload button opens the managed Google Play Store. You do not need to register for a developer account to publish a private app. Click the Plus icon in the lower right corner to continue.

   

   1. Type the name for your app and upload the .apk file. When finished, click Create. It might take up to 10 minutes for your private app to publish.

      

   2. Enter an email address to get updates about your apps.

      

   3. After your application is published, click the icon for the private app. If you want to add an app description, change the app icon, and other actions, click Make advanced edits. Otherwise, click Select to open the app information page.

      

5. Click Next. The app information page for the platform appears.

6. Configure the settings for the platform type, such as:

   • File name: Optionally, type a new name for the app.
   • App description: Optionally, type a new description for the app.
   • App version: You can’t change this field.
   • Package ID: Unique identifier of your app.
   • Minimum OS version: Optionally, type the oldest operating system version that the device can run to use the app.
   • Maximum OS version: Optionally, type the most recent operating system that the device must run to use the app.
   • Excluded devices: Optionally, type the manufacturer or models of devices that cannot run the app.

7. Configure the deployment rules and store configuration.

8. Assign any delivery groups to the app and click Save. For information, see Deploy resources.

Step 2: Configure app deployment

1. Navigate to Configure > Delivery Groups and select the delivery group you configured. Click Edit.

2. In the Apps section, drag the desired apps to the Required Apps box.

   

3. On the Summary page, click Save.

4. On the Delivery Groups page, select the delivery group and click Deploy.

MDX-enabled private apps

To add Android Enterprise apps as MDX-enabled enterprise apps:

1. Create a private Android Enterprise app and MDX-enable the app.
2. Add the app to the XenMobile console.
   • Host and publish the app on the managed Google Play Store.
   • Add the app to the XenMobile console as an Enterprise app.
3. Add the MDX file to XenMobile.

If you decide to host and publish apps through the Google Play Store, don’t opt in for Google certificate signing. Sign the app with the same certificate used to MDX-enable the app. For more information on publishing apps, see Google documentation on Publishing your app and Signing your app. The MAM SDK doesn’t wrap apps, so it doesn’t require a certificate other than the one used to develop the app.

For more information about publishing private apps through the Google Play Console, see the Google documentation on how to Publish private apps from the Play Console.

To publish an app through XenMobile, see the following sections.

Prepare a private Android Enterprise app

When you create a private Android Enterprise app, ensure that you follow Google Best practices for private apps.

After you create a private Android Enterprise app, integrate the MAM SDK with the app or wrap the app by using the MDX Toolkit. Then, add the resulting files to XenMobile.

You can update the app by uploading an updated.apk file. The following steps cover app wrapping with the MDX Toolkit.

1. Create your private Android Enterprise app and generate a signed .apk file.

2. The following sample file contains all known policies, some of which might not be applicable for your environment. Any unusable settings are ignored. Create an XML file with the following parameters:

   <?xml version="1.0" encoding="UTF-8"?>
   <MobileAppPolicies>
       <PolicySchemaVersion>
           1.0
       </PolicySchemaVersion>
       <Policies>
           <DevicePasscode>false</DevicePasscode>
           <AppPasscode>false</AppPasscode>
           <MaxOfflinePeriod>72</MaxOfflinePeriod>
           <StepupAuthAddress/>
           <RequireUserEntropy>false</RequireUserEntropy>
           <BlockRootedDevices>true</BlockRootedDevices>
           <BlockDebuggerAccess>false</BlockDebuggerAccess>
           <RequireDeviceLock>false</RequireDeviceLock>
           <NonCompliantDeviceBehavior>AllowAppAfterWarning</NonCompliantDeviceBehavior>
           <WifiOnly>false</WifiOnly>
           <RequireInternalNetwork>false</RequireInternalNetwork>
           <InternalWifiNetworks/>
           <AllowedWifiNetworks/>
           <UpgradeGracePeriod>168</UpgradeGracePeriod>
           <WipeDataOnAppLock>false</WipeDataOnAppLock>
           <ActivePollPeriod>60</ActivePollPeriod>
           <PublicFileAccessLimitsList/>
           <CutAndCopy>Unrestricted</CutAndCopy>
           <Paste>Unrestricted</Paste>
           <DocumentExchange>Unrestricted</DocumentExchange>
           <OpenInExclusionList/>
           <InboundDocumentExchange>Unrestricted</InboundDocumentExchange>
           <InboundDocumentExchangeWhitelist/>
           <connectionSecurityLevel>TLS</connectionSecurityLevel>
           <DisableCamera>false</DisableCamera>
           <DisableGallery>false</DisableGallery>
           <DisableMicrophone>false</DisableMicrophone>
           <DisableLocation>false</DisableLocation>
           <DisableSms>false</DisableSms>
           <DisableScreenCapture>false</DisableScreenCapture>
           <DisableSensor>false</DisableSensor>
           <DisableNFC>false</DisableNFC>
           <BlockLogs>false</BlockLogs>
           <DisablePrinting>false</DisablePrinting>
           <MvpnNetworkAccess>MvpnNetworkAccessUnrestricted</MvpnNetworkAccess>
           <MvpnSessionRequired>False</MvpnSessionRequired>
           <NetworkAccess>NetworkAccessUnrestricted</NetworkAccess>
           <DisableLocalhostConnections>false</DisableLocalhostConnections>
           <CertificateLabel/>
           <DefaultLoggerOutput>file,console</DefaultLoggerOutput>
           <DefaultLoggerLevel>15</DefaultLoggerLevel>
           <MaxLogFiles>2</MaxLogFiles>
           <MaxLogFileSize>2</MaxLogFileSize>
           <RedirectSystemLogs>false</RedirectSystemLogs>
           <EncryptLogs>false</EncryptLogs>
           <GeofenceLongitude>0</GeofenceLongitude>
           <GeofenceLatitude>0</GeofenceLatitude>
           <GeofenceRadius>0</GeofenceRadius>
           <EnableGoogleAnalytics>false</EnableGoogleAnalytics>
           <Authentication>OfflineAccessOnly</Authentication>
           <ReauthenticationPeriod>480</ReauthenticationPeriod>
           <AuthFailuresBeforeLock>5</AuthFailuresBeforeLock>
       </Policies>
   </MobileAppPolicies>
   <!--NeedCopy-->