Back to top

Issues related to specific deployments

Last updated April 10th, 2024


This section outlines issues you might encounter with specific deployments.

Settings Problem Resolution
Dual DAR Dual DAR is not working on my devices.

You must meet the following requirements to use Dual DAR.

- Devices should support Dual DAR 1.1 version or higher (check by going to Device Settings > About phone > Software information > Knox version)

- Only works for fully managed device with a work profile deployments for the encryption of Work Profiles within the managed devices

- You must use Knox Mobile Enrollment(KME) 1.23 or higher version to enroll the devices. See the following release notes for more information setting up Dual DAR with KME.

NOTE: KSP does not initiate Dual DAR, it only helps activate a KPE Premium Dual DAR license. You configure the parameters after it is setup during enrollment by KME.

Devices set up with File Based Encryption (FBE)

KSP does not receive policies pushed to devices that are set up with File-based encryption (FBE)

This can occur only if a device is rebooted and has not yet been unlocked.

The user must unlock the mobile device with their chosen authentication in order to decrypt it. Once this is done, the KSP policies are pushed to the device.
Device restrictions or advanced restrictions

Native UEM policies should take precedence over KSP policies.

If your UEM console natively supports a policy. You should use it instead of the KSP equivalent. This can help avoid unpredictable behavior on the device.

If a KSP policy is used, the value may be overridden by your UEM in future deployment, depending on how you have set up your deployment schedule.

Example: if your UEM console supports disable NFC and KSP also supports disable NFC, use the native UEM console policy.

Multifactor authentication (2FA) and biometrics

A conflict between multifactor authentication (2FA) and Biometric policies can cause a device to become "Admin locked." When this occurs, the user can't unlock the device without admin assistance.

This can occur if you turn off biometric unlock before you turn off 2FA.

To avoid Admin Lock:

  • When you activate 2FA on a device, turn on your biometric policy first (iris or fingerprint).
  • While 2FA is enabled and running on a device, do not independently disable your biometric policy (iris or fingerprint).
  • When you are turning off 2FA, make sure you follow this order of logic.

    1. Disable 2FA
    2. Disable biometric unlock

We also strongly recommend you disable One Lock on devices where 2FA is used for Work Profile authentication. One Lock policies are supported by your native UEM console and outside the scope of KSP.

NOTE: 2FA only works with Iris and Fingerprint (FP) only. Face recognition is independent and is not linked to 2FA.

DeX Customization features not working DeX Customization error messages are not showing up in debug mode.

Many DeX Customization features do not return errors (regardless of debug mode or normal operation). If your device has correct OS and DeX version then these will be applied, if not they will be ignored.

To see the debug messages, use a device with a version of Knox that supports the DeX features you are using.

Knox built-in VPN (Strong Swan) Certificate based authentication with a Device Owner (DO) does not work with Knox built-in VPN (Strong Swan). No resolution. Knox built-in VPN (Strong Swan) does not support certificate based authentication when deployed to a DO device.
Dual SIM

On devices running One UI 6.0 and lower, you can disable the second SIM but not hide its UI.

On devices running One UI 6.1 and higher, you can't disable the secondary physical SIM.

On supported devices, when the secondary physical SIM is blocked, there's no way to restrict the user from being able to access the SIM UI. However, the policy restricts calls, SMS, MMS, and data connections on the secondary SIM as intended.

Is this page helpful?