Setting up Ivanti EPMM 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 Ivanti EPMM version 11.0.0.0 and later, supports a new mode of deployment:

• Integrated deployment (GMS/Non-GMS) - the entire Ivanti EPMM 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 or supported newer versions.

Ivanti recommends administrators set the device ownership for AOSP devices. This can be done at: Settings > System Settings > Users & Devices > Device Registration.

• In the Ownership Settings section, in the "Default Ownership of Android devices using Google ZT or Samsung KME or non-GMS (AOSP) mode" field, select Company ownedor Employee owned.

• If you want the Terms of Service to be displayed, select the Show Terms of Service check box. Otherwise, the Terms of Service will not display (default.) (To create a Terms of Service, see Configuring an end user Terms of Service agreement.)

Devices that are non-GMS will be identified and reported to the Device Details page. Administrators can view individual devices and run a search for "Non GMS Device."

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 144.  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:

1. Enabling a closed network / AOSP deployment in Ivanti EPMM.

2. Creating a new Android Enterprise configuration.

3. Provisioning the Android device.

4. Managing the closed network / AOSP devices.

Once you have AOSP deployment in place, you can disable AOSP.

Next steps 

Enabling a closed network / AOSP deployment in Ivanti EPMM