- 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 Guard 20.11 release notes
SIM lock for PAYG
This update introduces a SIM 'Lock' function for the PAYG model. This feature allows customers to prevent devices being resold to other countries by locking the device if a blocklisted SIM is inserted.
Additionally, a submenu called 'Network registration verification' checks if the inserted SIM (even for allowlisted SIM) is an active one
Overdue message over lock screen
Devices get locked for various reasons and end-users try to unlock it through various methods. However, if a user does not know how to unlock, then they call the customer care center for assistance. This may increase call volume from the customer's perspective and take more time to resolve the issue.
This feature can help customers by guiding them on how to unlock their devices or how to make a payment if needed. Through these messages, customers can save time and resolve their issues without having to call customer support.
New lockscreen concept for R OS
From R OS, the following changes have been made to optimize the screen for the customer's benefit:
- Customer app is placed at the main lockscreen (the App icon is extracted from the apk and its title text can be customized by the customer)
- More space is available for the lock message by changing the buttons into icons.
R OS lockscreen will have the following GUI characteristics:
- Normal user lockscreen look and feel as much as possible
- Vivid background
- Call/Email button to the options screen to simplify main lock screen
- Wi-Fi and mobile data icon button
- Flexible Lock message area (with min & max height)
Remove applied policies once completing
Currently, some policies are applied to devices at the 'completing' status, which leads to issues if the device is locked due to the policy. 'Completing' is the prior step to complete which means the customer has made full payment and is waiting for the device to be released from KG control.
The policies have been removed once the device has made its payment. The removed policies include:
- SIM policy
- Notices such as Enrollment and SIM card change
- Relock timestamp
- Offline lock
PIN is not supported for Blink Reminder
Currently, users can clear the 'Blink reminder' with a PIN code, but it is not necessarily required given that this reminder can be dismissed with an 'OK button'.
The PIN input for the Blink reminder is not supported from KG 1.36 and onward
New option for enrollment message
Customers may worry about their device being resold to someone else, so a message that indicates the device is currently under a finance program is implemented.
- KG Console: there is a new option for displaying an enrollment notification (e.g. 'Always display the notification once KG enrolled')
- Client: if the customer selects to display the enrollment notice to always show on the notification panel, it should be registered on the notification panel once the device is enrolled. This notification cannot be cleared until the device itself is deleted