- *BASICS*
- The Knox Ecosystem
- White Paper
- Samsung Knox Portal
- Knox Cloud Services
- General Knox Support
- Knox Licenses
- *FOR IT ADMINS*
- Knox Admin Portal
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- How-to videos
- Before you begin
- Get started with UEMs
- Introduction
- Blackberry UEM
- Citrix Endpoint Management
- FAMOC
- IBM MaaS360
- Microsoft Intune
- MobileIron Cloud
- MobileIron Core
- Samsung Knox Manage
- SOTI MobiControl
- VMware Workspace ONE UEM
- Knox Service Plugin
- Release notes
- Migrate to Android 11
- FAQs
- Troubleshoot
- KBAs
- Knox Mobile Enrollment
- Introduction
- How-to videos
- Get started
- Features
- Register resellers
- Add an admin
- Create profiles
- Google device owner support
- MDM compatibility matrices
- Device users
- Activity log
- Enroll and unenroll devices
- Configure devices
- Provide KME feedback
- Use the Knox Deployment App (KDA)
- Recover Google FRP locked devices using KME
- Role-based access control (RBAC)
- Release notes
- FAQs
- Troubleshoot
- KBAs
- On-Premise
- Knox Configure
- Mobile
- Wearables
- Shared Device
- KBAs
- Knox Capture
- Introduction
- How it works
- How-to videos
- IT admins: Get started
- Getting started with Knox Capture
- Step 1: Launch Knox Capture
- Step 2: Create a scanning profile
- Step 3: Select apps and activities
- Step 4: Configure the scanner
- Step 5: Set keystroke output rules
- Step 6: Test apps in your configuration
- Step 7: Share your configuration
- Step 8: Deploy Knox Capture in Managed mode
- End users: Get started
- Features
- Release notes
- FAQs
- Troubleshoot
- Knox Asset Intelligence
- Knox Manage
- Introduction
- How-to videos
- Get started
- Video: Getting started with Knox Manage
- Integration with Managed Service Provider
- Access Knox Manage
- Configure basic environments
- Create user accounts
- Create groups
- Create organization
- Set up devices and profiles
- Set up Knox Manage deployment with a Knox Suite license
- Manage Chromebooks
- Manage Android devices with the Android Management API
- Manage Shared iPads
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- View applications
- Add applications
- Introduction
- Add internal Android and iOS applications
- Add internal Windows applications
- Add public applications using Google Play Store
- Add public applications using iOS App Store
- Add public applications using Managed Google Play
- Add public applications using Managed Google Play Private
- Add public applications using Managed Google Play Store Private Web
- Add public applications using Microsoft Store
- Add Chrome OS applications
- Assign applications
- Introduction
- Assign internal Android and iOS apps
- Assign iOS App Store applications
- Assign Google Play applications
- Assign Managed Google Play applications
- Assign Managed Google Play Private applications
- Assign Managed Google Play public web apps
- Assign Windows applications
- Assign Chrome OS applications
- Manage applications
- Volume Purchase Program for iOS
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Knox Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- Features
- FAQs
- KBAs
- Knox E-FOTA
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQs
- KBAs
- Troubleshoot
- Knox E-FOTA On-Premises
- Legacy Knox E-FOTA products
- Knox Guard
- Introduction
- How-to video
- Get started
- Using Knox Guard
- Dashboard
- Manage devices
- Introduction
- Accept or reject devices
- Upload devices
- Delete devices
- Complete payment
- Send payment overdue notification
- Enable or disable SIM control
- Download devices as CSV
- View device log
- View device deletion log
- Start and stop blinking reminder
- Lock and unlock devices
- Update lock message
- Send relock timestamp
- Turn on/off relock reminder
- Manage policies
- Manage licenses
- Manage resellers
- Manage admins and roles
- Activity log
- Knox Deployment App
- Release notes
- FAQs
- KBAs
- Support
- Samsung Care+ for Business
- *FOR RESELLERS*
- Knox Deployment Program
- *FOR MANAGED SERVICE PROVIDERS*
- Knox MSP Program
Knowledge base articles
This section outlines any rare issues you may 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—
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 |
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 | KSP is currently able to restrict operations on the second SIM but is unable to hide the second SIM's UI on the device. | No resolution. The current implementation does not block the UI, however, it restricts calls, SMS, MMS, and data connections using internal radio layer APIs on the second SIM's internal. |