- *BASICS*
- The Knox Ecosystem
- White Paper
- Samsung Knox Portal
- Knox Cloud Services
- General Knox Support
- Knox Licenses
- *FOR IT ADMINS*
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- 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
- Introduction
- How-to videos
- Get started
- Features
- Register resellers
- Add an admin
- Create profiles
- Google device owner support
- MDM compatibility matrices
- Device users
- Activity log
- Enroll and unenroll devices
- Configure devices
- Provide KME feedback
- Use the Knox Deployment App (KDA)
- Recover Google FRP locked devices using KME
- Role-based access control (RBAC)
- Release notes
- FAQs
- Troubleshoot
- KBAs
- On-Premise
- Knox Configure
- Mobile
- Wearables
- Shared Device
- 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
- FAQs
- Troubleshoot
- Knox Asset Intelligence
- Knox Manage
- Introduction
- How-to videos
- Get started
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- FAQs
- KBAs
- Knox E-FOTA
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQs
- KBAs
- Troubleshoot
- Legacy Knox E-FOTA products
- Samsung Care+ for Business
- *FOR RESELLERS*
- Knox Deployment Program
- *FOR MANAGED SERVICE PROVIDERS*
- Knox MSP Program
For a full list of all features, visit the product page for Knox E-FOTA.
February 16, 2020—Feature update
Knox E-FOTA Advanced portal updates
Version: SWM-v11.2.0.35-Samsung1.28.1 (Plugin samsung-b2b-dmflow-plugin-1.0.1.6)
No feature updates.
Knox E-FOTA Advanced client updates
Version: vdm-11.2-samsungb2b-1.1.0.67
No feature updates.
Solved issues
Knox E-FOTA Advanced portal
- Resource does not exist—If a device operation was created in a root domain, and a user attempted to expand it in the subdomain, that user would get the error Error - Resource does not exist. This has been fixed; the user is now able to expand the device operation in the subdomain.
- Deleting subdomains—A bug fix has been applied to ensure that subdomains are deleted from the list whenever they are removed from the domain.
- Auto-selection of devices with the same friendly name—A bug fix has been applied to ensure that devices with the same friendly name are now automatically selected during campaign creation.
- Creating device groups under a subdomain—Previously, when a subdomain-level user created a device group, they were unable to view that device group even if they were able to successfully create it. This has been fixed; a user who creates a device group under a subdomain can now instantly view that device group.
- Applying a factory reset policy on a subdomain—Previously, when a user executed a device profile on a subdomain to allow or disallow factory resets, and the Allow new devices to be added option was enabled, operations were created for all devices in the domain, not just the subdomain selected. This has been fixed; a user can now apply a factory reset policy at the subdomain level even if the Allow new devices to be added option is enabled.
- Registering SM-Default devices—A bug fix has been applied to ensure that devices are registered successfully with the device model SM-Default through the admin portal and through API calls.
- Export Devices with Inventories—A bug fix has been applied to ensure that the Export Devices with Inventories report will always display the inventory versions of devices.
