Knox Configure (KC) is a cloud-based service that empowers enterprises to customize and automate the enrollment of Samsung devices purchased from authorized Samsung resellers.
Knox Configure simplifies the out-of-box experience and enables a large range of configuration options.
This document is intended for:
- IT Admins — Admins create profiles with the device settings, restrictions, apps, and other content to deploy to groups of devices. After devices have been successfully enrolled into the enterprise, they receive the KC device profile via a Wi-Fi or mobile data connection.
- Resellers — Resellers bulk upload devices on behalf of requesting customers.
Try the solution
Promote and embed company branding, including animated boot screens and personalized business apps. Use this guide to apply data access restrictions as needed based on your organization's application update, notification and URL requirementsSTART TUTORIAL
About Knox Configure
KC is available in separate editions: Setup and Dynamic editions.
Setup edition supports one-time configuration of enrolled devices and settings. To change a device configuration after initial policies are set, devices must be factory resettled and new policies must be re-applied. Setup edition includes a select subset of the policies and settings available in the Dynamic edition's normal mode.
Following prerequisites must be satisfied to use Knox Configure:
- Supported phones, tablets or wearable devices purchased from a participating reseller in the Knox Deployment Program. If you are not sure whether your reseller is participating in the program, contact the reseller or a Samsung Sales Representative for more information.
- The appropriate Knox licenses purchased from a Knox Reseller (for commercial deployment).
- A Knox Portal account. For more information, go to Sign up for Knox Configure.
- The correct firewall exemptions needed to extend beyond your local and protected network domain and securely connect to the Knox Configure server. For more information, go to KC Firewall exceptions.
- A supported browser (Internet Explorer, Firefox, or Chrome). Internet Explorer is not recommended if using an on-premise MDM.
The deployment process
Using a web-based console, IT admins create profiles with the device settings, restrictions, apps, and other content to be deployed to groups of devices. After devices have been successfully enrolled into the enterprise, they receive device profiles via Wi-Fi or mobile data. This image below outlines the Knox Configure deployment process flow:
Once a profile is configured, it can be assigned to specific Knox Configure managed devices. Device assignment is the final step in the configuration process, though devices can be locked by carriers and resellers post deployment. For more information, go to Assign and deploy a profile to device.
Devices are submitted into Knox Configure progress through the following states when assigned profiles and configurations are pushed to the device:
- Unassigned — The device is uploaded into Knox Configure, but there are no profiles yet assigned.
- Profile assigned — A profile was assigned to the device, but the device is yet to be configured. For example, the device may not have been powered on since a profile has been assigned.
- In progress — A device profile assignment has been made and the subsequent device configuration is in progress and pending completion.
- Error — A problem was encountered during device configuration rendering. For more information, go to Configuration errors.
- Cancelled by user — The end user has skipped the device profile configuration. It must be restarted to configure the device.
- Configured — The device has successfully received Knox Configure profile or the profile update has been pushed successfully.
- Failed to configure — Device has failed to receive the profile, or a profile update was not successfully pushed.
- Updates pushed — A profile update has been pushed to the device, but the device is still processing the update.
- Locked — The device is locked in Knox Configure. Either IT admin can unlock the device or the device end user can input the provided password. Locked devices remain in their locked state even after the device's profile is unassigned.
- Exchanging — The device had its device ID swapped. This device needs its profile re-assigned and updated back to an Assigned state.
- Deactivated temporarily — The device has been temporarily deactivated by the IT admin to review and assess an issue before the device is activated again.
KME + DO with KC
Samsung Knox Mobile Enrollment (KME) added support for Android Enterprise managed device mode in Knox 2.8 (on S8 and higher device platforms). Additionally, Samsung has completed work for supporting KC + KME + Android Enterprise Managed device mode to increase opportunities for KC. KC can be launched from a KME enrolled device, by either selecting the device’s back key, or from a displayed device notification.