- Basics
- About Knox
- Knox licenses
- Knox white paper
- Sign up for Samsung Knox
- Latest release notes
- General Knox FAQ
- General Knox KBAs
- Submit a support ticket
- User Acceptance Testing
- 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
- Knox Configure
- Mobile
- Wearables
- Shared Device
- FAQ
- 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
- FAQ
- KBAs
- 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
- Create a new profile
- Assign profiles to groups and organizations
- Enroll devices
- Shared Android device quickstart
- Non-shared Android device enrollment quickstart
- Android Management API device enrollment quickstart
- Apple User Enrollment quickstart
- View device information
- Apply profiles to organizations
- 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
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Knox Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- Features
- FAQ
- KBAs
- Knox E-FOTA
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQ
- 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
- Device management
- Accept or reject devices
- Upload devices
- Delete devices
- Complete device management
- Send notifications
- 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
- FAQ
- KBAs
- Support
- Knox Guard REST API
- Samsung Care+ for Business
- For Knox Partners
- Knox Deployment Program
- Knox MSP Program
Knox Mobile Enrollment 1.32 release notes
Root and intermediate certificate installation
Certain customers require both root and intermediate certificates be installed on devices prior to EMM enrollment. However, Samsung devices do not have these certificates pre-installed, resulting in additional enrollment steps, and a more complex setup.
To address such certificate requirements, customers can now add additional certificates with KME. Certificates can now be downloaded and installed after KME enrollment profile creation, but prior to EMM connectivity which may require root certificates to proceed.
The following certificate types are supported: .cer, .pem, .crt, .der, and .ca-bundle (either inside the ZIP file or applied directly), while .p7b, .p7s, .p12, and .pfx file types are not supported.
With Android 9, root/intermediate certificates are installed in the device default keystore. With Android 10 and greater, root/intermediate certificates are installed in the VPN and App keystores, as well as the device default keystore.
Customer now able to let EMM access their data using KME API
This feature allows customers to authorize those EMMs who have integrated via KME APIs to access their data.
The customer super admin must enter unique ID of the EMM in KME. A valid ID is associated with an EMM partner for access permission verification. Once the ID is matched, the name of the EMM displays in a success dialog to provide confirmation to the customer.
Once authorized by the customer, the KME APIs can be used by their EMM to access their customer data (https://docs.samsungknox.com/devref/knox-mobile-enrollment/index.htm). If not authorized, the KME APIs cannot be used. The super admin can revoke permission at any time by deleting or editing the ID.
Proget and Chimpa added to list of supported EMMs in the KME-DO dropdown list
With this release, both Proget and Chimpa were added to the list of supported EMMs. Specifically, Proget and Chimpa were added to the Pick your MDM drop-down menu when selecting an EMM to assign the device owner privilege.
South Korea added as a KME supported country
South Korea has been added a KME supported country in the EU region.
Going forward, South Korea will be available within the KME samsungknox.com drop-down during signup.