We are excited to announce our most recent updates to KACE Cloud.
In our latest release, we are introducing the following features:
We are thrilled to announce a feature preview for our upcoming Scripting functionality in KACE Cloud. While not all potential capabilities will be available in this upcoming preview, this new feature will give you a taste of how to automate tasks, streamline workflows, and enhance your productivity like never before.
How to Participate:
To ensure this feature meets your needs, we invite you to share your use cases for Scripting. Your feedback is invaluable to us! We will review the use cases carefully to check if you qualify for access to this exclusive preview.
Interested in Joining?
If you are interested in participating in the Scripting feature preview, send an email to KACE_BETA@quest.comwith your use cases and details on how you plan to utilize this feature.
We look forward to hearing from you and working together to make KACE Cloud even better!
In our latest release, we have made the following enhancements:
KACE Cloud now offers more flexibility in device restarts triggered by patch installations. Users can snooze the restart according to rules set by the admin.
Enhancements to Patching Rules to improve flexibility for setting the rules. The changes are as follows:
Users can now preview the restart notifications that Windows and macOS users get when prompted for installing updates.
For more information refer to Configure patching rules and client notification options
Admins can now remotely restart Windows and macOS registered devices, similar to MDM-enrolled Windows devices.
Optimized Patch reporting to improve reporting efficiency, reduce load on the database, and enhance scalability for large patch datasets.
KACE Cloud now supports key Android 15 restrictions for work profiles and COPE devices, improving security and usability.
KACE Cloud now allows Android Management API (AMAPI) devices to authenticate with a Google Managed account (work profile only).
To integrate with AMAPI, KACE Cloud must be configured with a Google Workspace admin account. If AMAPI was not initially set up with a Google-managed account, devices must be unenrolled, and a new enterprise created, as existing enterprises cannot merge with Google Workspace. For more information refer AMAPI: Enable Google Managed Authentication
The result is seamless authentication for AMAPI devices, simplified setup without recreating Google Console projects, and better device management with improved Google Workspace integration.
Try the beta version of our new policy editor, which makes it easier to understand the content of the policy and easier to configure it. Feedback is welcome!
Please submit your feedback for this feature to kace_beta@quest.com
For more information, visit the KACE Cloud Help Center, where you can also find the full set of Release Notes, which includes the most recent list of resolved issues.
Be sure to check out the KACE Cloud Product Support page to find knowledge base articles, notifications, video tutorials, and a product user forum.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center