Back to top

Knox Mobile Enrollment Direct 1.7 release notes

Last updated July 26th, 2023

Knox Mobile Enrollment Direct 1.7 is scheduled to go live on July 26, 2023 and includes the following changes.

Disable captive portal detection

Previously, during enrollment for fully managed devices, if the device was connected to a network using a private SIM card, it couldn’t validate with the servers, causing enrollment to fail.

With the 1.7 release, devices running Android 14 or higher with Knox 3.10 can use the captive portal mode in device deployment profiles to disable the detection of captive portals and, therefore, skip network validation.

Moreover, you can set the captive portal mode to function in one of the two following ways:

  • Don’t attempt to detect captive portals — Captive portals are ignored during enrollment. Used for Android Enterprise enrollment in closed networks by default.
  • If detected, prompts the user to sign in — When a captive portal is detected, a notification prompts the device user to sign in.

To apply this feature, the device user must reboot their device, then scan the enrollment QR code using a plus sign (+) gesture again.

captive portal mode

Self-update of the Knox Enrollment Service agent within closed network

Starting with the 1.7 release, you can now update the Knox Enrollment Service agent from the locally-hosted relay server within closed network environments. This update behavior means that new features that are intended only for newer Knox Enrollment Service agent versions are available whenever a new version of the Knox Enrollment Service agent is released, without the need to wait for device OS updates.

Expert mode in device configuration

With the 1.7 release, you can now create device configuration profiles in Expert mode, which allows you to directly extract, configure, and upload the device configuration XML file derived from the Knox Service Plugin schema.

The Expert mode relies on the Java Runtime Environment (JRE) to unpack the Knox Service Plugin APK file and extract the device configuration XML file. Hence, if JRE 1.8 isn’t installed, a dialog informs you that Java is necessary for the Expert mode functionality.

expert mode

Is this page helpful?