Android Enterprise is a secure workspace available on Android devices. The workspace isolates business accounts, apps, and data from personal accounts, apps, and data.
In XenMobile, you manage your bring your own device (BYOD) and company-owned Android devices by having users create a separate work profile on their devices. By combining hardware encryption and the policies that you deploy, you securely separate the corporate and personal areas on a device. You can remotely manage or wipe all corporate policies, apps, and data without affecting the personal area of the user. For more information about supported Android devices, see the Google Android Enterprise website.
Managed Google Play combines the familiar user experience and app store features of Google Play with a set of management capabilities designed specifically for enterprises. You use managed Google Play to add, buy, and approve apps for deployment to the Android Enterprise workspace on a device. You can use Google Play to deploy your private Android apps, in addition to public and third-party apps. When you add a paid public app store app to XenMobile for Android Enterprise, you can review the Bulk Purchase licensing status. That status is the total number of licenses available, the number now in use, and the email address of each user consuming the licenses. For details about adding an app to XenMobile, see Add a public app store app.
On managed devices, managed Google Play is the user’s enterprise app store. The interface is similar to Google Play. Users can browse apps, view app details, and install them. Unlike the public version of Google Play, users can only install apps from managed Google Play that you make available for them.
Managed Google Play or G Suite
You can use either managed Google Play or G Suite to register Citrix as your enterprise mobility management (EMM) provider.
If your organization does not use G Suite, you can use managed Google Play to register G Suite as your EMM. If you use managed Google Play, you provision managed Google Play Accounts for devices and end users. Managed Google Play Accounts provide access to managed Google Play, allowing users to install and use work apps you make available. If your organization uses a third-party identity service, you can link managed Google Play Accounts with your existing identity accounts.
Because this type of enterprise is not tied to a domain, you can create more than one enterprise for a single organization. For example, each department or region within an organization can enroll as a different enterprise to manage separate sets of devices and apps.
If your organization already uses G Suite to provide users access to Google apps, you can use G Suite to register Citrix as your EMM. If your organization uses G Suite, it has an existing enterprise ID and existing Google Accounts for users. To use XenMobile with G Suite, you sync with your LDAP directory and retrieve Google Account information from Google using the Google Directory API. Because this type of enterprise is tied to an existing domain, each domain can only create one enterprise. To enroll a device in XenMobile, each user must manually sign in with their existing Google Account. The account gives them access to managed Google Play in addition to any other Google services provided by your G Suite plan.
Set up Android Enterprise with managed Google Play
XenMobile provides a simple way to set up Android Enterprise for your organization. Using XenMobile Management Tools, you bind XenMobile as your enterprise mobility management provider through Google Play and create an enterprise for Android Enterprise.
G Suite customers, see Legacy Android Enterprise for G Suite customers, which includes a table of related policy information.
- Your Citrix account credentials to sign in to XenMobile Tools
- You corporate Google ID credentials to sign in to Google Play
In the XenMobile console, click the gear icon in the upper-right corner. The Settings page appears.
On the Settings page, click Android Enterprise.
On the Android Enterprise page in XenMobile Settings, click Go to XenMobile Tools.
- Sign in to your Citrix account if prompted.
In the Android Enterprise page in XenMobile Tools Management, click Go to Google Play.
In Google Play, register Citrix as your organization enterprise mobility management:
- Enter your organization name.
- Ensure that Citrix is shown as your enterprise mobility management.
- Accept the terms and then click Confirm.
- In the page that appears, click Complete Registration.
That step creates a file for you to download and then upload to XenMobile.
- In the Android Enterprise page in XenMobile Tools Management, click Download.
Create a password for file encryption. Make a note about the password for reference when you upload the file and need to enter the password.
- Click Go back to XenMobile.
In Android Enterprise page in XenMobile Settings, click Upload file.
Browse to the file you downloaded and then enter the password you created. Click Upload.
An enterprise ID is added for Android Enterprise. To enable Android of Work, slide Enable Android Enterprise to Yes.
Publish mobile productivity apps for Android Enterprise
In order to publish mobile productivity apps for Android Enterprise, follow the steps below.
- In your managed Google Play Store account, publish the apps you want your users to have. You can manage your Google Play account at https://play.google.com/work.
In your XenMobile console, publish the same apps as the following:
Unenrolling an Android Enterprise enterprise
You can unenroll an Android Enterprise enterprise using the XenMobile Server console and XenMobile Tools.
When you perform this task, the XenMobile Server opens a popup window for XenMobile Tools. Before you begin, ensure that the XenMobile Server has permission to open popup windows in the browser you are using. Some browsers, such as Google Chrome, require you to disable popup blocking and add the address of the XenMobile site to the popup block whitelist.
After an enterprise is unenrolled, Android Enterprise apps on devices already enrolled through it are reset to their default states. The devices will no longer be managed by Google. Re-enrolling them in an Android Enterprise enterprise may not restore previous functionality without further configuration.
After the Android Enterprise enterprise is unenrolled:
- Devices and users enrolled through the enterprise have the Android Enterprise apps reset to their default state. Android Enterprise App Permissions and Android Enterprise App Restrictions policies previously applied no longer have an effect.
- Devices enrolled through the enterprise are managed by XenMobile, but are unmanaged from Google perspective. No new Android Enterprise apps can be added. No Android Enterprise App Permissions or Android Enterprise App Restrictions policies can be applied. Other policies, such as Scheduling, Password, and Restrictions can still be applied to these devices.
- If you attempt to enroll devices in Android Enterprise, they are enrolled as Android devices, not Android Enterprise devices.
To unenroll an Android Enterprise enterprise:
In the XenMobile console, click the gear icon in the upper-right corner. The Settings page appears.
On the Settings page, click Android Enterprise.
Click Remove Enterprise.
Specify a password. You’ll need this for the next step to complete the unenrollment. Then click Unenroll.
When the XenMobile Tools page opens, enter the password you created in the previous step.
Configure Android Enterprise device policies
Use these policies to configure how XenMobile interacts with devices running Android Enterprise. This table lists all device policies available for Android Enterprise devices.
|Android Enterprise App Permissions||Android Enterprise App Restrictions||App Uninstall|
Choose the user name type for enrollment
If your device enrollment process requires users to enter a username or user ID, the format accepted depends on how the XenMobile server is configured to search for users by User Principal Name (UPN) or SAM account name.
If the XenMobile server is configured to search for users by UPN, users must enter a UPN in the format:
If the XenMobile server is configured to search for users by SAM users must enter a SAM in one of these formats:
To determine which type of user name your XenMobile server is configured for:
- In the XenMobile server console click the gear icon in the upper-right corner. The Settings page appears.
- Click LDAP to view the configuration of the LDAP connection.
Near the bottom of the page, view the User search by field:
- If it is set to userPrincipalName, XenMobile server is set for UPN.
- If it is set to sAMAccountName, XenMobile server is set for SAM.
Provision fully managed devices Android Enterprise
Only company-owned devices can be enrolled as fully managed devices in Android Enterprise. On fully managed devices the entire device, not just the work profile, in controlled by the company or organization. Fully managed devices are also known as work-managed devices.
XenMobile supports these methods of enrollment for fully managed device:
- afw#xenmobile: With this enrollment method, the user enters the characters “afw#xenmobile” when setting up the device. This token identifies the device as managed by XenMobile and downloads Secure Hub.
- QR code: QR code provisioning is an easy way to provision a distributed fleet of devices that do not support NFC, such as tablets. The QR code enrollment method can be used on fleet devices that have been reset to their factory settings. The QR code enrollment method sets up and configures fully managed devices by scanning a QR code from the setup wizard.
- Near field communication (NFC) bump: The NFC bump enrollment method can be used on fleet devices that have been reset to their factory settings. An NFC bump transfers data through between two devices using near-field communication. Bluetooth, Wi-Fi, and other communication modes are disabled on a factory-reset device. NFC is the only communication protocol that the device can use in this state.
The enrollment method is used after powering on a new or factory reset devices for initial setup. Users enter “afw#xenmobile” when prompted to enter a Google account. This action downloads and installs Secure Hub. Users then follow the Secure Hub set-up prompts to complete the enrollment.
In this enrollment method is recommended for most customers because the latest version of Secure Hub is downloaded from the Google Play store. Unlike with other enrollment methods, you do not provide Secure Hub for download from the XenMobile server.
- Supported on all Android devices running Android 5.0 and above.
To enroll fully managed devices using a QR code, you generate a QR code by creating a JSON and converting the JSON to a QR code. Device cameras scan the QR code to enroll the device.
- Supported on all Android devices running Android 7.0 and above.
Create a QR code from a JSON
Create a JSON with the following fields.
These fields are required:
If Secure Hub is uploaded onto Citrix XenMobile server as an enterprise app, it can be downloaded from
https://<fqdn>:4443/*instanceName*/worxhome.apk. The path to the Secure Hub APK must be accessible over the Wi-Fi connection that the device connects to during provisioning.
These fields are optional:
android.app.extra.PROVISIONING_LOCALE: Enter language and country codes.
The language codes are two-letter lowercase ISO language codes (such as en) as defined by ISO 639-1. The country codes are two-letter uppercase ISO country codes (such as US) as defined by ISO 3166-1. For example, enter en_US for English as spoken in the United States.
android.app.extra.PROVISIONING_TIME_ZONE: The time zone in which the device is running.
Enter an Olson name of the form area/location. For example, America/Los_Angeles for Pacific time. If you don’t enter one, the time zone is automatically populated.
android.app.extra.PROVISIONING_LOCAL_TIME: Time in milliseconds since the Epoch.
The Unix epoch (or Unix time, POSIX time, or Unix timestamp) is the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT). The time doesn’t include leap seconds (in ISO 8601: 1970-01-01T00:00:00Z).
android.app.extra.PROVISIONING_SKIP_ENCRYPTION: Set to true to skip encryption during profile creation. Set to false to force encryption during profile creation.
A typical JSON looks like the following:
This QR code gets scanned by a factory-reset device to enroll the device in work-managed device mode.
To enroll the device
To enroll a device as a fully managed device, the device must be in factory reset state.
- Tap the screen six times on the welcome screen to launch the QR code enrollment flow.
When prompted, connect to Wi-Fi. The download location for Secure Hub in the QR code (encoded in the JSON) is accessible over this Wi-Fi network.
Once the device successfully connects to Wi-Fi, it downloads a QR code reader from Google and launches the camera.
Point the camera to the QR code to scan the code.
Android downloads Secure Hub from the download location in the QR code, validate the signing certificate signature, install Secure Hub and sets it as device owner.
For more information, see this Google guide for Android EMM developers: https://developers.google.com/android/work/prov-devices#qr_code_method.
To enroll a device as a fully managed device using NFC bumps requires two devices: One that is reset to its factory settings and one running the XenMobile Provisioning Tool.
- Supported on all Android devices running Android 5.0, Android 5.1, Android 6.0 and above.
- A XenMobile Server version 10.4 that is enabled for Android Enterprise.
- A new or factory-reset device, provisioned for Android Enterprise in as a fully managed device. You can find steps to complete this prerequisite later in this article.
- Another device with NFC capability, running the configured Provisioning Tool. The Provisioning Tool is available in Secure Hub 10.4 or on the Citrix downloads page.
Each device can have only one Android Enterprise profile, managed by an enterprise mobility management (EMM) app. In XenMobile, Secure Hub is the EMM app. Only one profile is allowed on each device. Attempting to add a second EMM app removes the first EMM app.
Data transferred through the NFC bump
Provisioning a factory-reset device requires you to send the following data through an NFC bump to initialize Android Enterprise:
- Package name of the EMM provider app that acts as device owner (in this case, Secure Hub).
- Intranet/Internet location from which the device can download the EMM provider app.
- SHA1 hash of EMM provider app to verify if the download is successful.
- Wi-Fi connection details so that a factory-reset device can connect and download the EMM provider app. Note: Android now does not support 802.1x Wi-Fi for this step.
- Time zone for the device (optional).
- Geographic location for the device (optional).
When the two devices are bumped, the data from the Provisioning Tool is sent to the factory-reset device. That data is then used to download Secure Hub with administrator settings. If you don’t enter time zone and location values, Android automatically configures the values on the new device.
Configuring the XenMobile Provisioning Tool
Before doing an NFC bump, you must configure the Provisioning Tool. This configuration is then transferred to the factory-reset device during the NFC bump.
You can type data into the required fields or populate them via text file. The steps in the next procedure describe how to configure the text file and contain descriptions for each field. The app doesn’t save information after you type it, so you might want to create a text file to keep the information for future use.
To configure the Provisioning Tool by using a text file
Name the file nfcprovisioning.txt and place the file in the /sdcard/ folder on the SD card of the device. The app can then read the text file and populate the values.
The text file must contain the following data:
This line is the intranet/internet location of the EMM provider app. After the factory-reset device connects to Wi-Fi following the NFC bump, the device must have access to this location for downloading. The URL is a regular URL, with no special formatting required.
This line is the checksum of the EMM provider app. This checksum is used to verify that the download is successful. Steps to obtain the checksum are discussed later in this article.
This line is the connected Wi-Fi SSID of the device on which the Provisioning Tool is running.
android.app.extra.PROVISIONING_WIFI_SECURITY_TYPE=<wifi security type>
Supported values are WEP and WPA2. If the Wi-Fi is unprotected, this field must be empty.
If the Wi-Fi is unprotected, this field must be empty.
Enter language and country codes. The language codes are two-letter lowercase ISO language codes (such as en) as defined by ISO 639-1. The country codes are two-letter uppercase ISO country codes (such as US) as defined by ISO 3166-1. For example, type en_US for English as spoken in the United States. If you don’t type any codes, the country and language are automatically populated.
The time zone in which the device is running. Type an Olson name of the form area/location. For example, America/Los_Angeles for Pacific time. If you don’t enter a name, the time zone is automatically populated.
This data isn’t required, because the value is hardcoded into the app as Secure Hub. It’s mentioned here only for the sake of completion.
If there is a Wi-Fi protected by using WPA2, a completed nfcprovisioning.txt file might look like the following:
If there is an unprotected Wi-Fi, a completed nfcprovisioning.txt file might look like the following:
To get the Secure Hub checksum
To get the checksum of any app, add the app as an enterprise app.
In the XenMobile console, go to Configure > Apps and then click Add.
The Add Apps window appears.
The App information page displays.
Select the following configuration and then click Next.
The Android Enterprise Enterprise App page appears.
Provide the path to the .apk and then click Next to upload the file.
Once the upload is complete, the details of the uploaded package appear.
Click Next to open page to download the JSON file, which you then use to upload to Google Play. For Secure Hub, uploading to Google Play is not required, but you need the JSON file to read the SHA1 value from it.
A typical JSON file looks like the following:
Copy the file_sha1_base64 value and use it in the Hash field in the Provisioning Tool.
The hash must be URL safe.
- Convert any + symbols to -
- Convert any / symbols to _
- Replace the trailing \u003d with =
If you store the hash in the nfcprovisioning.txt file on the SD card of the device, the app does the safety conversion. However, if you opt to type the hash manually, it’s your responsibility to ensure its URL safety.
The Provisioning Tool uses the following libraries in its source code:
v7 appcompat library, Design support library, and v7 Palette library by Google under Apache license 2.0
For information, see Support Library Features Guide.
Butter Knife by Jake Wharton under Apache license 2.0
Provision work profile devices in Android Enterprise
On work profile devices in Android Enterprise, you securely separate the corporate and personal areas on a device. For example, BYOD devices can be work profile devices. The enrollment experience for work profile devices is similar to Android enrollment in XenMobile. Users download Secure Hub from Google Play and enroll their devices.
By default, the USB Debugging and Unknown Sources settings are disabled on work profile devices.
When enrolling devices in Android Enterprise in work profile mode, always go to Google Play. From there, enable Secure Hub to appear in the user’s personal profile.