- Basics
- The Knox Ecosystem
- White Paper
- Samsung Knox Portal
- Knox Cloud Services
- General Knox Support
- Knox Licenses
- 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
- 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
- Samsung Care+ for Business
- For Knox Partners
- Knox Deployment Program
- Knox MSP Program
"Workspace License Expired" error appears without any change to the UEM, Knox Workspace/Android Enterprise profile type, or license key
Environment
- Knox Platform for Enterprise (KPE)
- Android Enterprise (AE) Device Owner (DO) mode with a Knox License Management (KLM) and Enterprise License Management (ELM) key activated
- No changes to the UEM, Knox Workspace/Android Enterprise (AE) profile type, or license key on the device
Overview
Some users are encountering an issue where their device is locked with a "Workspace License Expired" error. User actions are limited to powering the device on and off or factory resetting it.
Cause
When a device is enrolled into a UEM, a KLM key and ELM key are activated for AE DO Premium deployments. This license activation process creates an association between the device and the license key, granting the device a specific set of permissions. The KLM key grants Knox Premium permissions for creating a fully-managed device.
Periodic checks are made between the device and Knox license server to verify that its assigned seat is still in use. If the device does not check in to the server for 180 days or more, its seat is automatically released and all permissions previously granted to the device are revoked.
After the automatic seat release is triggered, the device is flagged as 'deactivated' in the Knox server. If it is then rebooted, a server check attempts to validate the KLM and ELM license keys associated with the device. However, due to a network timing issue, these validation processes are out-of-sync. As a result, the device is given Knox standard permissions rather than Knox Premium permissions, which locks the workspace container.
Resolution
The Samsung Knox team has identified a fix for the validation logic, to be released in upcoming Android P and Q firmware updates.
Workaround
For Android 10 (Q OS) Workspace-only devices:
Please keep the device connected to a power source and network for at least 24 hours, allowing the device to revalidate the license key to the Knox license server.
For Android 9 (P OS) and earlier Workspace-only devices:
- On the device, reboot until the device password screen appears.
- Enter the device password, after which the "Workspace License Expired" error appears.
- Wait approximately 10 minutes to establish a connection to the Knox licensing server.
- If the device is not unlocked, repeat Steps 1-3.
If you require further support after completing these workaround steps, please submit a ticket through your Knox dashboard that lists the IMEIs of your impacted devices.
Additional information
- To learn more about the KLM/ELM license key validation process, see What is a Knox automatic license seat release?
- If you have recently migrated from a Knox Workspace container to an AE work profile and are experiencing the "Workspace License Expired" error, see Device is locked with "Workspace License Expired" error after migrating from a Knox Workspace to an Android Enterprise profile.