Setting up Core with a closed network / AOSP deployment

There are situations where the onboarding, registration and management of devices is limited and requires a different approach. Examples of these kinds of situations are:

In an environment that does not have connectivity to Google mobile services (GMS) due to restrictions in the organization or due to a closed network.
In countries where Google mobile services are not available.
Where devices that do not have Google mobile services but vendors have enabled Android Enterprise AOSP (Android Open Source Project.)

With MobileIron Core version 11.0.0.0, Core supports a new mode of deployment:

Integrated deployment (GMS/Non-GMS) - the entire Core instance serves devices in full Android Enterprise mode (for example, Samsung devices) and also devices that do not have GMS (for example, AR/VR devices.)

This feature applies to Android 6 devices through the latest version as supported by MobileIron.

Use cases

AOSP deployment can work side-by-side with Android Enterprise deployment.

Supported modes of registration supported:

Device Admin mode
Device Owner mode

Below are the possible use cases for this feature.

Table 1. Use cases for Closed network / AOSP deployment
Use Case	Expected Result
Only the AOSP configuration is pushed	AOSP in Device Admin or Device Owner mode.
Both AOSP and Android Enterprise configurations are pushed	Android Enterprise configuration takes priority over AOSP.
Device is registered in AOSP and the Android Enterprise configuration is pushed to the registered device	The registered device retains AOSP mode. Android Enterprise configuration applies only to fresh registrations.

Process of setting up:

Once you have AOSP deployment in place, you can disable AOSP / closed network deployment.

Next steps

Enabling a closed network / AOSP deployment in Core