Samsung S22 Knox Mobile Enrollment fails with Enterprise Edition profileSolved

Hi @wyatt_simmons ,

This behavior usually points to a Samsung Knox SKU/licensing mismatch rather than a Hexnode compatibility issue.

Samsung Galaxy S22 devices with the same model number can still be treated differently by Samsung Knox depending on how they were uploaded or registered in Samsung’s systems. If a Knox Mobile Enrollment profile has the Enterprise Edition option enabled, Samsung validates whether the device is recognized as an Enterprise Edition device. If the device was uploaded as a standard retail SKU, Samsung can block enrollment through that Enterprise Edition KME profile even though the hardware model is otherwise compatible.

Since the affected devices do not appear under Enterprise Edition device licensing in the Samsung Knox portal, they are likely registered as standard SKU devices.

You have three practical options:

1. Use a separate non-Enterprise Edition KME profile

   Create another Knox Mobile Enrollment profile with the same Hexnode enrollment configuration, but without Enterprise Edition enabled. Assign only the affected devices to this profile.

2. Enroll using Android Enterprise QR code

   This bypasses Knox Mobile Enrollment entirely and provisions the device directly into Hexnode as an Android Enterprise Device Owner device. In Hexnode UEM, go to Enroll > Android > Android Enterprise > QR code. Factory reset the device, tap the Welcome screen 6 times to open the QR scanner, then scan the QR code and complete setup.

3. Contact the reseller

   If the devices were sold as Samsung Enterprise Edition devices, the reseller should correct the device upload/registration through the Samsung Knox reseller workflow so Samsung recognizes them as Enterprise Edition devices. Once corrected, they should work with the Enterprise Edition KME profile.

Adding DPC extras can help pass the right Hexnode enrollment configuration through Knox, but it will not bypass Samsung’s Enterprise Edition eligibility check.

Regards,
Isabel Lora
Hexnode UEM

So if I use a non-Enterprise Edition KME profile or Android Enterprise QR enrollment, does that mean the phones lose Hexnode management features? That’s the part I’m worried about.

Using a non-Enterprise Edition KME profile or Android Enterprise QR enrollment does not make the device unmanaged or reduce normal Android Enterprise Device Owner management in Hexnode.

The Enterprise Edition setting in the Samsung Knox portal is related to Samsung’s Enterprise Edition commercial bundle and Samsung-side entitlements. Hexnode can still manage the device through Android Enterprise Device Owner enrollment, including policy deployment, app management, restrictions, and other standard Android management actions supported for that device.

However, if your organization specifically depends on Samsung Enterprise Edition bundle entitlements or Samsung Knox Suite licensing that comes with EE SKUs, those entitlements must come from Samsung/reseller-side registration. Hexnode cannot convert a standard Samsung SKU into an Enterprise Edition SKU.

Regards,
Isabel Lora
Hexnode UEM