Release Notes

May 2020

What's New

In our May release, we’re introducing two new features and two usability enhancements.

Our new System Apps for Android feature lets administrators control the visibility of manufacturer-specific (OEM) apps in the work profile of personal Android devices. It allows an OEM app to be treated just like managed Play Store apps, which means data is stored in the work profile and automatically removed when the device is unenrolled.

The new Web Apps feature provides a seamless way to connect end users with key company websites. Admins can create and configure iOS and Android Web app shortcuts that can be assigned to devices and used in the same way as standard apps.

And as part of our ongoing effort to improve the end user experience, we’re releasing new maintenance window notifications in the product UI, as well as an updated user experience when adding Android apps from the Google Managed Play Store to KACE Cloud MDM.


Features

System Apps for Android

The System Apps for Android feature was built for admins who need to be able to make an OEM built-in app available in a work profile. Any built-in app included by a device manufacturer can be turned on by default, appearing the same way other company-approved apps do on devices.

We do advise checking the Google Play Store for the system app first. If the app is there, downloading through the Play Store will enable updating and/or managed configuration. When adding a system app through KACE Cloud, an admin will need to locate a package name for a specific app. We recommend starting at the device manufacturer’s website.

Learn more about System Apps for Android.

Web Apps

Admins can now create iOS and Android web apps in KACE Cloud MDM. Our new feature lets an admin set the URL, icon, and display mode features for a new user-facing web app. The apps are then saved in the App Library in KACE Cloud and can be deployed to any devices. Note that Web apps are not yet supported for macOS or tvOS.

Learn more about Android and iOS App Management.

Usability Enhancements

Google Play Store Update

We’ve created a simplified workflow with a cleaner look and feel that makes adding Android apps a smoother experience for our end users. In one linear process, you can choose the Google Play Store, choose your app(s), configure permissions, then approve and import.

Learn more about App Management Functionality.

Maintenance Notifications in UI

New maintenance notifications will appear in the product UI at a 7-day and 1-hour interval leading up to our monthly maintenance and release. We want to ensure that our end users are never caught off guard due to a maintenance window and can plan accordingly for a brief period of downtime. Each of the notifications is a one-time alert and can be easily dismissed.

Learn more about Alerts and Notifications.


Resolved Issues

Issue Description Status
ESMCL- 4041 Incorrect device history when installing apps across different operating systems When device history shows an "installing application" record for the app, no additional history is included. FIXED
ESMCL- 4031 App list when importing to device does not show app configs The list of apps available for adding includes one item for every App + App Config combination. FIXED
ESMCL- 3852 Clearing search filter on users page does not update results The user list updates to show all users and not just the ones that match the search. FIXED
ESMCL- 3507 Device History does not show the installation of Android Options Device History screen shows the installation of the android options configuration FIXED

Known Issues

Issue Description Status
3514 - iOS update command does not display status feedback. iOS command to update OS uses default action that will typically download but not install. Fix to display status feedback. Open
3286 - Apparent mismatch between device compliance and individual entity compliance. Occasionally the policy details for a device may show success even if the entity in question did not successfully install. Open
3108 - Auto-deployed Android restrictions don't appear in the device restrictions list If auto-deployed restrictions for Android are sent to the device, the database may not be properly updated. Open
3070 - System attempts to remove policy configs when unassigned device is assigned to a user During reassignment of a device to a user, removal of previous configurations may fail. If this happens, it may be possible to work around this by first unenrolling the device. Open
Android - Role Management and SSO Configuration If user role assignment is set to Automatic during SSO Configuration, a manual attempt to update an individual user's role via the Users > Edit User path may appear possible, but will be overwritten by the original SSO Configuration. To resolve, the configuration setting can be changed to Manual, which will then enable editing of individual user roles. Open
Android - Restrictions Restrictions that are configured to deploy upon enrollment may not immediately appear in the inventory for impacted devices; however, the restrictions will be enforced on the device. Open
Android - Device Owner Setup When using the Device Owner enrollment flow (afw#kace), the enrollment flow may not complete if the Google Play services on the factory default image of the device are out of date. This a known issue with the Android operating system, caused by the enrollment process timing out before the update of the Play Services on the device can complete. You will know that this situation occurred if you are never asked for your subdomain name during the enrollment process. If you end up back at the device home screen, locate and launch the KACE Cloud MDM agent app on the device and click the 'Enroll Device' button to complete the setup process. Open
Android - Gmail App Android devices require the Gmail app to be installed in order to use the email account configurations. Open
Android - Set and Clear Passcode Commands The set and clear passcode functions are different in Android 7.0 and later. On versions prior to 7.0, an administrator could set or clear the passcode as desired. On Android 7.0 and later, the passcode can only be set on devices that do not already have a passcode set, and passcodes cannot be cleared. The user interface does not currently warn users who are attempting to set or clear a passcode on Android 7.0 and later, but an error message will appear. Note that attempting to clear a passcode will also fail if there is a policy in place that requires use of a passcode to do so. Open
iOS - Factory Reset: Apple iOS iCloud Account Lock When resetting an Apple iOS device back to factory defaults, the device will remain locked to the associated iCloud account. To prevent this from happening, before resetting the device, manually turn off the 'Find my phone' feature on the iPhone. Open
macOS - macOS 10.15 Account Configuration During enrollment, if the ‘Prevent Primary Account Changes’ option is checked and DEP authentication is enabled, the primary account will be created automatically using the DEP authentication token as the account password. While still in the enrollment process, the password cannot be changed. However, once enrollment is complete, the account password can be changed as normal. Open

Additional Resources

Getting Started Guide

Admin Guide


© 2020 Quest Software Inc.

ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept.

4 Polaris Way

Aliso Viejo, CA 92656

Refer to our website (www.quest.com) for regional and international office information.

Patents

Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at www.quest.com/legal.

Trademarks

Quest and the Quest logo are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at www.quest.com/legal. All other trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective owners.