- 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 1.2 release notes
Knox Guard service APIs available
Knox Guard service APIs can now be generated on behalf of a requesting company's system. A developer generates an API key from Knox Guard Console and embeds the key in calls to the API. Data from the API is secured by whitelisting a specified IP address. If the API's active key is lost or compromised, a new key can be regenerated and the old key deleted. Knox Guard APIs support device uploads, device acceptance, subscription payment overdue messaging and blink reminders, device lock/unlock, and licensing.
To use the API, a dedicated account requires creation by the Samsung Knox Guard team on behalf of the integrating customer. For more information, contact your Samsung Knox Guard representative.
Auto-refresh enhancements
To date, the data displayed within the console was not refreshing in real-time and consistently amongst all screens as data was updating, resulting in customer confusion as to what data is current and what requires a refresh. With this enhancement, console data is consistently auto-refreshed as data is changed or updated.
Contact resource flexibility added
With this release, a device user's blink reminder and device lock contact resource can be provided as a phone number or E-mail address. Either a phone number or E-mail address is required, but now it is optional which subscriber contact type is used.
Completing status cancellation period added
If a device is marked as Payment Complete, its status changes to Completing… and remains this way for 2 days. The user has 2 days to cancel it while in the Completing… state, which reverts the device back to an Active state. If no action is taken after 2 days, the status changes to Payment complete and the Knox Guard application is uninstalled permanently. The device however is not automatically deleted from the server, and must be removed manually.
Device deletion improved
A Knox Guard admin can delete a device from the Knox Guard console when the device is in a payment complete or rejected state. When a device is deleted from Knox Guard, the device is removed from the server and the Knox Guard client is uninstalled. When deleted, all of the device's information and history are removed.
