SOTI MobiControl now separates Remote Control access from web console access, allowing administrators to grant users access to Remote Control without providing access to the web console. Organizations can use this capability to enable support teams or external systems to launch Remote Control sessions through secure, one-time signed URIs limited to a single session.
| MCMR‑35305 | In some cases, Android device agents remained offline for extended periods before reconnecting. |
| MCMR‑39635 | During Windows Modern Remote Control sessions with multiple monitors, the mouse cursor and clicks were misaligned due to incorrect monitor coordinates. |
| MCMR‑39788 | Terms and conditions uploaded as an HTML file did not display correctly during Android Enterprise COPE enrollment. |
| MCMR‑39887 | BYOD device enrollment failed during Microsoft Entra ID authentication. |
| MCMR‑40064 | The System Health page displayed a false error indicating that the Management Server was unable to communicate with SOTI Search. |
| MCMR‑41150 | Database maintenance failed and displayed an error notification in the SOTI MobiControl web console. |
| MCMR‑41344 | Some Active Directory users intermittently received an XML error when logging in to the SOTI MobiControl web console. |
| MCMR‑41394 | On iOS shared devices, login failed because existing profiles were not completely removed during relocation. |
| MCMR‑41418 | Failed to use scripts to reset passwords on Impinj (Linux) devices. |
| MCMR‑41419 | Data Collection policies did not capture all incoming, outgoing, and missed calls from Android devices within the configured intervals. |
| MCMR‑41540 | Large-scale app policy deployments caused high memory usage that made the Management Service and SOTI MobiControl web console temporarily inaccessible. |
| MCMR‑41817 | On Android devices, Unlock Device and Set Passcode actions sent through the Push Notification Service (PNS) failed to work. |
| MCMR‑41938 | Virtual groups with applied filters did not update automatically and required a manual refresh. |
| MCMR‑42034 | Signal policies configured to run at specific local times executed according to UTC instead. |
| MCMR‑42153 | Wipe Program Data actions did not appear in the Android Classic device logs, even though the actions completed successfully. |
| MCMR‑42335 | On Windows Classic devices, profiles failed to install and remained in a Pending Install state. |
| MCMR‑42408 | On macOS devices, an extra scroll bar appeared next to the side menu in the SOTI MobiControl web console. |
| MCMR‑42471 | Failed to delete empty device groups when a legacy Alert policy did not migrate to Signal and continued to be referenced. |
| MCMR‑42575 | Profiles were missing from the SOTI MobiControl web console. |
| MCMR‑42711 | Android devices did not reconnect to SOTI XTreme Hub within the configured retry interval. |
| MCMR‑42739 MCMR‑42835 | Signal policies relocated devices even if the configured out-of-contact criteria were not met. |
| MCMR‑42820 | SOTI Search integrity degraded continuously, dropping below the healthy state on a daily basis. |
| MCMR‑42993 | An action pop-up bar blocked the last device in the device list, preventing it from being selected or managed. |
| MCMR‑43003 | Failed to wipe Windows Modern devices using an Out of Contact profile because the configured script did not execute. |
| MCMR‑43246 | An Android Enterprise application repeatedly synced to SOTI XTreme Hubs from the Deployment Server even when the application file had not changed. |
| MCMR‑43321 | Phone Number and ICCID values for iOS devices alternated between Unknown and the correct value on each device check-in. |
| MCMR‑43371 | Post-file-sync PowerShell scripts ran in legacy mode and failed when executed through SOTI XTreme Hub on Windows Modern devices. |
| MCMR‑43377 | After a firmware upgrade, JavaScript code used to adjust device settings stopped working on certain Lenovo tablets running Android 15. |
| MCMR‑43440 | Newer APK versions of an enterprise application failed to upload to an Android App Policy. |
| MCMR‑43478 | When device relocation to a new group was blocked by permissions, the web console displayed a false confirmation message. |
| MCMR‑43488 | SOTI Search integrity intermittently reported a Failed status even if synchronization completed successfully. |
| MCMR‑43507 MCMR‑43510 MCMR‑43560 | Addressed multiple issues with Syslog logging. |
| MCMR‑43521 | Bluetooth printer device mapping failed due to a mismatch in the Android ID displayed in the console and the Android ID reported by SOTI Connect. |
| MCMR‑43538 | On Android devices, application entries added to the antivirus whitelist were reclassified as a file, causing repeated false-positive malware notifications. |
| MCMR‑43559 | The Astrakhan/Ulyanovsk (UTC+4) time zone configured in the Advanced Configurations tab incorrectly applied the Volgograd (UTC+3) time. |
| MCMR‑43604 | Some Samsung devices intermittently stopped reporting antivirus data, such as last scan date, scan result, and antivirus version, to the SOTI MobiControl web console. |
| MCMR‑43650 | An approved application could not be removed from Managed Google Play, returning an error stating that the application was still installed on a device. |
| MCMR‑43672 | Failed to save a new value for the Idle Time Allowed Before Display Turns Off setting in the Microsoft Security Baseline profile. |
| MCMR‑43807 | Certain Windows Modern devices failed to reconnect and remained offline. |
| MCMR‑43887 | Failed to download the Agent Debug Report due to the generation of an invalid download URL when the console language was set to Japanese. |
| MCMR‑43944 | Viewing the Collected Data tab in the device information panel incorrectly required the Manage Notes permission. |
| MCMR‑44006 | Failed to add certain applications to an App Policy from Managed Google Play because they did not appear in the search results. |
| MCMR‑44073 | On newly enrolled Windows CE devices, a Device Certificate Status Check Failed error caused multiple certificates to be pushed to the device. |
| MCMR‑44075 | Managed app configurations failed to save in an Android App Policy. |
| MCMR‑44082 | Failed to modify custom data values due to the error message: “Value cannot be null”. |
| MCMR‑44203 | Refreshing the Packages page cleared the active search filter and displayed the full list of packages even though the search term remained. |
| MCMR‑44258 | Failed to select a configuration option in the Samsung OEMConfig profile due to misalignment in the UI. |
| MCMR‑44280 | An automated browser-based monitoring tool failed to authenticate with the SOTI MobiControl web console. |
| MCMR‑44340 | On Android devices with small screens, some configuration options in the SOTI MobiControl Settings Manager were out of reach due to the absence of a scroll bar. |
| MCMR‑44366 | Devices did not reconnect to the server. |
| MCMR‑44495 | Web Clip icons were removed from Web Clip profiles, causing affected iOS devices to display default icons. |
| MCMR‑44555 | Stella failed to install and launch due to a database connection error. |
| MCMR‑44977 | Existing Signal policies present in the database were not displayed in the SOTI MobiControl web console. |
| MCMR‑45101 | A server upgrade from an earlier version failed with errors. |
