- *BASICS*
- The Knox Ecosystem
- Samsung Knox Portal
- Knox Cloud Services
- General Knox Support
- Knox Licenses
- *FOR IT ADMINS*
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- White paper
- 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
- 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
- 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 Manage
- Introduction
- How-to videos
- Get started
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- FAQs
- KBAs
- Knox E-FOTA
- Introduction
- White paper
- Knox E-FOTA One
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQs
- Troubleshoot
- KBAs
- Migrate from Knox E-FOTA Advanced to Knox E-FOTA One
- Knox E-FOTA Advanced
- Knox E-FOTA on MDM
- Samsung Care+ for Business
- *FOR RESELLERS*
- Knox Deployment Program
- *FOR MANAGED SERVICE PROVIDERS*
- Knox MSP Program
MDM enrollment methods
Fully managed device (DO) MDM enrollment matrix
The table below displays DO enrollment methods utilized by KME supported MDMs that allow the device to be fully managed by the enterprise. A device owner (DO) is a privilege assigned to an MDM to apply policies to a device during setup, as part of Android Enterprise enrollment. Using Knox Mobile Enrollment, IT admins and end users can create an MDM profile and let the EMM agent install as a DO (Fully Managed Device) on devices running Knox 2.8 or later.
For information on supported DO MDM partners and how to access their own partner support documentation directly from their Websites, go to: Android Enterprise device owner. For information configuring a DO supported KME enrollment profile, go to: create a profile.
The feature descriptions for listed MDMs are as follows:
-
End user credential entry – A KME admin can associate both a username and password/secret with device(s) in the KME portal. If no pass through is supported for a particular MDM, the device user may be prompted to enter credentials directly. However, these are associated with user info stored by the MDM, and not KME.
-
Username pass through – The username assigned to the device(s) in KME is automatically passed through to the MDM. The MDM may still prompt the device user for a password/secret for validation, depending on how it has been configured.
-
Full credential pass through – Both the username and password/secret assigned to the device(s) in KME are automatically passed through to the MDM. There is no need for the device user to be prompted for credentials (use name and password/secret) to be validated.
Legacy Device admin (DA) MDM enrollment matrix
The table below displays DA enrollment methods utilized by KME supported MDMs. Keep in mind, Device admin (DA) enrollment has been rendered as legacy, and is not recommended unless your device does not support Android Enterprise.
For information configuring a DA supported KME enrollment profile, go to: create a profile.
The feature descriptions for listed MDMs are as follows:
-
End user credential entry – A KME admin can associate both a username and password/secret with device(s) in the KME portal. If no pass through is supported for a particular MDM, the device user may be prompted to enter credentials directly. However, these are associated with user info stored by the MDM, and not KME.
-
Username pass through – The username assigned to the device(s) in KME is automatically passed through to the MDM. The MDM may still prompt the device user for a password/secret for validation, depending on how it has been configured.
-
Full credential pass through – Both the username and password/secret assigned to the device(s) in KME are automatically passed through to the MDM. There is no need for the device user to be prompted for credentials (use name and password/secret) to be validated.
