What's new in GoTo Resolve MDM
4 January, 2024 - User management through REST API v2 and other enhancements
In this release, we added user management operations to REST API v2, we included improvements and fixes for the new Android and macOS client versions, bug fixes, and maintenance-related enhancements.
We support create, read, update, and delete operations for end user items through REST API v2.
- Previously, making patch blocklist changes while macOS was downloading a patch update caused the update to fail and caused issues in subsequent patch updates. We have fixed this issue.
- On the Free plan sites, we fixed a visual bug relating to the Customer Services icon.
14 December, 2023 - FileVault personal recovery key escrowing and other enhancements
This release includes improvements to the FileVault security feature, support for application deployment through REST API v2, improvements and fixes with new Android and macOS client versions, and other enhancements.
It is now possible to enable the escrowing of the FileVault personal recovery key for Mac devices running macOS 10.13 or above. The recovery key used to unlock the encrypted disk is sent to our server and stored in an encrypted format. The administrator can retrieve the personal recovery key from the device inventory information.
- We have improved the restart handling for the macOS patch deployment.
- We have added support for application deployment through REST API v2.
- Due to security concerns, we have removed the option to add the image URL for the macOS PKG applications. The previously submitted images have been replaced with the default icon.
- New Mac devices became suspended if you migrated data from a Mac device to the new Mac device using Time Machine backup or Migration Assistant.
- Issues with Android kiosk mode:
- Disabling the kiosk mode temporarily didn't work properly
- Kiosk mode did not start on the device without a SIM slot
- The Lock device command did not prompt the device lock screen passcode
Google has identified an issue with Android 14 where certain configuration settings on a device are permanently applied. The configurations are impacted if they are deployed before:
- The OS upgrade from Android 13 to Android 14
- The reboot of factory-shipped Android 14 device
We have implemented the workaround solution suggested by Google to prevent the permanent configuration settings when rebooting a device running Android 14.
7 December, 2023 - Android client 2.10.0 and other enhancements
We have released Android client 2.10.0, which now fully supports Android 14. We have widened the enrollment option portfolio for Fully managed with work profile devices, fixed several Android-related bugs, and modified our Free plan.
We have added the following new features:
- We have released Android client 2.10.0, which now fully supports Android 14.
Note: Installing applications that target SDK23 (Android 6), or lower versions, is not supported on Android 14 devices.
- On Fully managed Android devices, administrators can block ultra-wideband communication by adding it to the configuration profile restrictions.
- For Fully managed with work profile (COPE) devices, we have added the Zero touch and Knox Mobile Enrollment (KME) enrollment options.
- We support setting different wallpapers on Android device home and lock screens.
We have fixed the following Android-related bugs:
- Enrolling Work profile management for Android devices was possible only if 'All the time' location access was selected.
- Android system applications that were installed on a device before the device was enrolled could not be managed and the managed configurations did not apply to them.
- If the undeploy operation was started for an app that was embedded in Android firmware, the undeployment did not finish and the status remained 'in progress'.
- The Android client's 'Disable kiosk mode' only worked with Samsung kiosk mode, now it works for generic kiosk mode as well.
- The deployment of an APK the application ID of which contained both upper and lower case letters got stuck in 'in progress' state.
- Previously, when using Zero Touch or KME enrollments, the Android client always enrolled devices in Fully managed mode, even if the Fully managed with work profile mode was selected.
- If font scaling was used on the client user interface, in some cases, the layout was incorrect.
- For COPE devices, deploying a passcode configuration profile for the lock screen with the default passcode failed when both 'Force unlock passcode' and 'Lock screen message' were enabled.
- Some conditions caused Android retirements fail.
27 November, 2023 - Windows enrollment beta improvements and other enhancements
We have implemented improvements for the Windows enrollment beta feature, and released a bug fix for adding macOS applications with scripts.
We have implemented the following updates:
- We have corrected a minor text alignment issue on the UI.
- We have added and updated animation for accordions.
- The selected device users are now sorted alphabetically by the email address.
In, we have corrected a validation error.
2 November, 2023 - GoTo Resolve MDM moved to single domain URL structure and other enhancements
GoTo Resolve MDM has moved to single domain URL structure to be more compliant with the requirements of certain browsers, to improve security, and to provide better service for our customers in the future.
The URL of GoTo Resolve MDM changed to single domain architecture, meaning that all customer sites are now under a single domain: https://mdm.gotoresolve.com.
- We fixed a minor bug in the logic that defines the text displayed on the empty Dashboard.
- We added the option to erase or keep the eSIM when retiring a shared iPad.