On June 26, 2025, we released an update to the Miradore client on Android. Shortly after release, we discovered a bug that affected a small number of devices, so we reverted to the previous version while we worked on a fix.

We’re happy to let you know that a corrected version is rolling out today and we are updating the Miradore client to version 2.17.2 (Build 451). If the app is not automatically updated on your managed devices, we recommend you update it as soon as possible.

Thank you for your patience and understanding. If you experience any issues, please let us know by contacting our support team.

The EID of eSIMs is now available for iOS and iPadOS devices on the individual device page in the SIM table under the Inventory tab.

For more information on all the information that is available under the Inventory tab for iOS and iPadOS devices, see Collected iOS inventory.

If you have a LogMeIn Resolve MDM trial account and would like to upgrade to full access, you can now easily purchase a license through GoTo Admin.

For detailed information, see LogMeIn Resolve MDM trial and Manage my product licenses in the admin portal.

You can now use LogMeIn Resolve MDM to configure and deploy Wi-Fi settings to macOS devices. Simplify network setup and ensure consistent connectivity for your managed devices with our new Wi-Fi configuration profile.

For detailed information, see Configure Wi-Fi settings for macOS devices.

We have addressed an issue related to Android app deployment that might lead to deployment loops in certain scenarios.

When creating a Wi-Fi configuration profile for iOS devices, you can now select WPA3 as the security mode for the connection. Currently, the WPA3 security mode can only be used for personal networks.

WPA3 is supported on iPhone 7 and later models, and iPad 5th generation and later models.

We have simplified our Windows enrollment process, making it easier than ever for users to start managing their devices with our streamlined, intuitive enrollment wizard.

On the device end, we updated the Actions dialog in the Android Custom Launcher to let users synchronize their devices with the MDM server manually.

For detailed information on the Android Launcher and Home screen & kiosk mode configuration profile, see Android Custom Launcher.

We also updated our Add configuration profile wizard. We refined the UI, updated the descriptions and requirements of each configuration profile for clarity, and included helpful tutorial videos to make it easier to manage your mobile devices with LogMeIn Resolve MDM.

We released the Android Custom Launcher feature that introduces a new configuration profile called Home screen & kiosk mode. This configuration profile allows you to set the visibility of specific applications on a device's home screen and configure kiosk mode for the device, giving you more power to define the user experience compared to the regular Kiosk mode configuration. With this configuration profile, you can configure a device's home screen settings and set the device into kiosk mode with one or multiple apps available from the home screen without the risk of device users reorganizing their apps.

See Android Custom Launcher for more information.

We are introducing the Editor role for LogMeIn Resolve MDM. Editors have limited access to a specific LogMeIn Resolve MDM site. See User roles in LogMeIn Resolve MDM for more information.

The LogMeIn Resolve MDM Editor role appears as Member role in GoTo Admin. This means that the Editor role can be assigned to users by assigning them a Member role in GoTo Admin. For more information on roles and permissions in GoTo Admin, see What is the difference between a role and a permission?.

You can assign specific device tags to specific users that have an Editor role in LogMeIn Resolve MDM. This way, Editors that have specific tags assigned to them can only see devices with those tags. Tags for Editors can be managed through the new Permissions view, available under the System menu.

See Tags for Editors for more information.

We have updated the name of our product to LogMeIn Resolve MDM to be in line with our other remote support solutions, but your experience with LogMeIn Resolve MDM remains unchanged. For more information, visit our website.

You can now connect Google Workspace and Microsoft Entra ID to your LogMeIn Resolve MDM site to automate user management. Integrating Google Workspace and Microsoft Entra ID with LogMeIn Resolve MDM lets you achieve near real-time synchronization for your device users' data, saving time and effort spent on manual updates.

See Application integrations with LogMeIn Resolve MDM for more information.

The latest LogMeIn Resolve MDM release introduces the following improvements and fixes to Android and Windows device management:

• Windows policy Configuration Service Provider (CSP) information is updated with the latest data provided by Microsoft. See Custom policy configurations for Windows 10 and 11 for more information.
• Fixed an issue where the local IP addresses weren't correctly displayed in Android device inventory data.
• In some cases, the QR code for Android work profile enrollment failed to direct the user to the enrollment page.

The reset passcode action is now supported in Android Direct Boot mode. This mode enables MDM to perform limited actions when a device is powered on but on the lock screen.

This feature is useful especially if the user forgets the passcode for a device. When the device is booted without Direct Boot mode enabled, its management is lost, and the passcode can't be reset from MDM.

For more information, see Android Direct Boot mode.

Ending support for Android 6

As announced earlier, we end the support for enrolling devices running Android 6.

We will continue to support a wide range of Android, iOS, macOS, and Windows OS versions, and our product team is currently preparing for new, upcoming operating systems, including Android 15.

We always recommend using the latest operating system for increased security and a better user experience.

Return to Service

The release fine-tunes our iOS Return to Service feature. In addition, to small UI enhancements, the Return to Service action is available via API v2.

Learn more about the Return to Service for iOS and iPadOS.

The Apple DEP device list now shows the assignment status of the enrollment profile correctly.

Return to Service is a feature that enables IT admins to wipe and re-enroll iPhones/iPads with a single command without physically touching the devices. Along with the action, the previously selected settings for language, region, and Wi-Fi profile are sent to the device. Previously, these unskippable user selections had to be performed each time a device was wiped and re-enrolled. Being able to send a wipe command to a device and make it set itself back up again, optimizes and speeds up the process of returning a device to service.

The feature is available for devices running iOS/iPadOS 17 or above.

Learn more on how to use Return to Service for iOS and iPadOS.

Fetching Android Services info is now possible with the Report Builder and API. The attribute InvAndroidServices was added for the Device item.

Apple introduces support for third-party app stores, the alternative app marketplaces, for the EU markets. From iOS version 17.4 onwards, iPhone supports app downloads from these platforms. However, this ability might raise some security concerns, which is why this product release brings a new configuration profile to deny the marketplace app installation.

To add a new iOS configuration, go to Management > Configuration profiles. Choose Restrictions and select the Device functionality tab from there.

• Fixed an issue with the patch management where, on some occasions, the update to macOS version 14.3.1 failed.
• Finetuned the design of the Subscription plan page.
• The Devices by category widget on Dashboard now supports more category values.

The release fixes the following Android-related issues:

• Work profile creation failed, and a device was set to legacy management mode when enrolling the device with the client downloaded from the Google Play Store.
• The device serial number information in the Miradore client's UI wasn't shown properly on Samsung devices.
• Failed Knox restriction deployments for COPE devices got stuck in the Waiting status instead of Failed with an error description. This was an issue especially with Samsung devices.

The latest releases include a fix to a bug that caused issues in iOS Custom configurations when using certain variables.

Starting from this release, enrolling devices for the Device Admin management is not possible. We don't support the management of these devices but the existing Device Admin devices can be managed in MDM until the end of their lifecycle.

API keys now show the creation dates in Infrastructure diagram.

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.

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.

Learn more about FileVault disk encryption for macOS.

• 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.

Read more about the issue with management of Android 14 devices.

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.

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 Applications > Add > macOS application > Script > , we have corrected a validation error.

LogMeIn 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 LogMeIn 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.