- 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
Service provider update interrupts the KME enrollment process
Environment
- Knox Mobile Enrollment (KME)
- True Single SKU (TSS) devices
Overview
New True Single SKU devices require a one-time restart to finish the setup process. Customers using these devices in conjunction with KME have reported experiencing an issue where the enrollment data entered in KME is not passed to their chosen MDM after the restart. Due to this behavior, manual end-user intervention is required.
Cause
Due to the mandatory service provider update restart during the setup process of TSS devices, the seamless KME enrollment process is interrupted and KME fails to pass vital enrollment data to the MDM.
Resolution
A few short-term fixes are being released, please see the workaround section. The Samsung team is working on a more permanent solution. Please check back for updates on the release.
Workaround
For Android 11+, LTE 5G devices, a short-term fix will be released that allows you to temporarily postpone the service provider update in order to complete the enrollment process.
The schedule of the release depends on the specific device model and service provider.
For devices Android 10 or lower:
- The IT admin will need to unassign the device from the KME profile to allow the end-user to complete the service provider update.
- Once the device has completed the service provider update, the IT admin can then re-assign the device to the KME profile.
- The end-user will either need to:
- Factory Reset the device, which will then take them through the regular KME enrollment process.
- Using a browser on the device, navigate to me.samsungknox.com and click next to trigger the KME enrollment.
What is True Single SKU?
When you purchase a new Galaxy device it will come pre-loaded with network-specific features and services, depending on where the device has been purchased from. This is because most devices have a specific service provider or SKU that indicates which network they are connected to. With True Single SKU, new devices have a common service provider. This means that when the device is set up, it will determine what service provider is being used and apply the specific service provider SKU.
True Single SKU devices will connect to a server during the initial setup to get information about the service provider. After setup has finished, the device will restart to apply the network specific features and services.
Service Provider Update pop-up
To finish setting up your True Single SKU device with all of the appropriate services and features, your device will need to perform a one time restart. This restart may change the apps and layout of your device, depending on the service provider being applied.