- 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.12 release notes
Background push updates now permitted
This enhancement enables an IT admin or system integrator to push an updated profile or application to Samsung Gear wearable devices without any related UI displaying on the target device. This enables the wearable device user to continue to use their device without interruption, as profile or application updates occur in the background.
Frictionless Customization
Currently, when an error occurs during wearable device enrollment, the enrollment process stops, regardless of the error type, and a failure is reported to KC server. Additionally, the current messaging is inadequate to properly define the scope and severity of the problem that halted enrollment.
Watch face alteration and deletion prevention
This feature addresses requests by IT admins who need a dynamic profile restriction policy option that prevents wearable device users from changing their device’s watch face, once it is configured and set on the device.
Disallow application uninstall
This feature enables an IT admin to configure a list of applications that cannot be uninstalled by the device user post enrollment and deployment. Removing an application from the disallow uninstall app list removes the uninstall restriction, and provides the device user the capability to remove the application from their device. If utilizing a setup edition profile, just a single application is permitted in the uninstall prevention list.
Dynamic profile updates and management
This enhancement enables an IT admin to assign a new profile to devices already having an assigned profile. If a device is configured with an old profile, a push notification for a profile update is delivered and the device can updated with a new profile. The device’s status updates to "Update pushed" and then moves to "Configured" once the updated configuration is applied to the device. The transition from the old profile to the new profile is seamless. If the new profile has different profile information (company, email, and phone number etc.), it should be processed on the target device without disruption. Additionally, if the old profile is utilizing a ProKiosk mode setting, the device exits ProKiosk mode and is re-configured based on the settings of the new profile.
Application deployment improvements
To date, if an application does not support a Gear S3LTE (R765) model wearable device, the wearable Knox Configure back-end returns an invalid package error. To broaden the list of supported wearable devices the Gear S3 BT or Gear Sports are now also included, so an IT admin can add a wearable application for those devices as well.
New profile push policies supported
To date, if a wearable device's assigned profile is changed, a profile push update occurs regardless of the profile's edition. New rules are now in place to restrict setup edition profiles from receiving a push update. A dynamic profile can still push update another dynamic edition profile, and a setup edition profile can push update a dynamic edition profile. However, a setup edition profile can no longer update another setup edition profile, nor can a dynamic edition profile push update a setup edition profile.