KACE® Cloud Mobile Device Manager
These release notes provide information about the latest KACE Cloud Mobile Device Manager release.
About this release
KACE Cloud Mobile Device Manager allows you to quickly enroll mobile devices, manage their inventory, and to apply required configurations and policies. You can interact with managed devices using a standard set of commands, such as resetting a password or locking a device, as needed. This cloud-based product helps you implement your entire device management solution quickly, and ensuring that managed devices follow your organization guidelines and standards, while protecting your data integrity.
This release contains several new features and a number of resolved issues. See New features.
- Android 5.0+ (Work profile enrollments)
- Android 6.0+ (Fully managed afw#kace enrollments)
- Android 8.0+ (Zero-touch enrollments)
- Android 11.0+ (COPE enrollments)
- iOS 8.0+ (Personal and supervised devices, DEP enrollments)
- iOS 11.0+ (Enrollment using Apple Configurator 2)
- iPadOS 13.0+
- macOS 10.13+ (Enrollments)
- tvOS 10.2+
- Windows 11 Professional, Enterprise, Education
- Windows 10 Professional, Enterprise, Education, 1709 or later
- Autopilot and Azure Domain Joins require Azure AD P2
NOTE: Autopilot and Azure Domain Joins require Azure AD P2.
- Google Chrome 49+
- Microsoft Edge 16+ (Not supported on mobile devices.)
- Mozilla Firefox 45+
- Apple Safari 12+ (Mac only)
System-provided mobile administrative applications are not currently available.
This release does not contain any major features. It includes a number of bug fixes and enhancements.
The following issues are addressed in this release.
Table 1: General resolved issues
|When linking an iOS app to a policy with No Settings for the app settings, the app was getting installed with the Default Settings.
|The Windows Custom Profile editor loaded very slowly when there were hundreds of configuration items.
|Disabling a user account was not preventing them from logging in.
|After unenrolling or deleting a device, some policy records were not removed, resulting in a continual “spinner” in policy history.
|Device detail summary would show KACE Agent for Android as up-to-date when it was not.
|Policy manager was not removing the Default Settings from an app when it was changed to No Settings.
|An Android user could add a private account to the Play Store regardless of restriction.
|Disabling a system admin user could result in errors.
|Library items could accidentally be added to a policy’s pending changes.