- 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 Configure for Wearables 1.25 release notes
Booting animation enhancements
Currently, when deselecting the Set a custom booting animation option on a profile, the existing booting animation and sound are not cleared as expected from the wearable device when an update is pushed to the device.
The same expectation should occur when deselecting the Set a custom shutdown animation option on a profile: The shutdown animation and sound should be cleared when an update is pushed to the device.
To date, WKC checks if an existing animation was set by a previous WKC profile, and will not remove the animation if it was set for a previous profile. To remedy this, users now have the ability to remove booting or shutdown animation separately when pushing an update.
Enrollment improvements
To date, when a profile is assigned and a wearable device has 15% power or less remaining, enrollment stops during the authentication stage after accepting the End User License Agreement (EULA).
Once the wearable device is charged and rebooted, the device is expected to resume enrollment. However, enrollment doesn't resume if Power Saving mode is enabled, even if it was disabled just before license activation.
To prevent enrollment disruptions, Power Saving mode is now automatically disabled at the start of enrollment and enabled again after license activation.
Auto select newly uploaded apps
To date, in order to deploy an app that's been recently uploaded into a profile, you would need to select the app manually from the app list after it's been uploaded.
As part of this release, newly uploaded apps are now auto selected to enhance the app deployment work flow.
Dashboard widget UI enhancements
As part of a UI enhancement in this release, when an account has no profiles, the dashboard displays a Create profile button instead of the profile widgets. Selecting it starts the profile creation screen flow.
If there are profiles in the account, a Select profile to pin here button is displayed. Selecting enables the user to pin profiles for quick access from the dashboard.
Enhanced console string responses
Included in this release are updates to the console response strings, which include error and success messages.
Updated strings have been enhanced to include meaningful messages to assist with troubleshooting. For example, if an event has an error log entry associated with it, the log will include a link with additional information.
Unable to select KDA licenses before activation date
Currently, during profile creation, you won't be able to select the Knox Deployment App (KDA) license key is entered if the date of entry is before the set activation date.
As part of an update in this release, the license drop-down menu will now include applicable licenses: Both active with remaining seats, as well as licenses that have yet to start.
If a user tries to use KDA to enroll a device with a license prior to the activation date, a license error code is displayed for the device user.