SOTI MobiControl

2024.1.1

·

Build 1058

·

August 26, 2024

Note:

SOTI MobiControl 2024.1.1 Build 1058 replaces the previous build (1053) posted on August 19, 2024.

New Features and Improvements

System Administration

Automated Compliance Partner Creation

Administrators can now automatically add SOTI MobiControl as a third-party compliance partner in Microsoft Intune. For customers doing a fresh install, they can simply add credentials in Global Settings. Customers upgrading to 2024.1.1 need to accept the pending permissions in Global Settings.

Execute Scripts on Device Upon Shared Device Logout

Administrators can now execute custom device scripts when users log out of shared devices, ensuring that all personal information and application log data are effectively removed. This functionality will apply only to the Android platform.

SOTI MobiControl administrators can now assign Android profiles and policies using the Microsoft single sign-on application connection created in Global Settings. This connection can also be used in device search.

Set Device Custom Attribute Values with Signal

Custom attributes can now automatically be set on devices by Signal policies. This empowers administrators to take full advantage of the automation and filtering already possible with custom attributes today by incorporating them into other workflows using Signal.

Log Out Shared Device Users with Signal

Administrators may now configure Signal policies that automatically log out shared device users when certain conditions are met. This allows for increased automation of shared device workflows, further improving the cost-saving potential of implementing shared devices into a device fleet.

Device-Side Evaluation of Charging Status through Signal

Building on the device-side evaluation feature for Signal, administrators can now use Signal policies to evaluate the charging status on the device at a set evaluation frequency rather than relying on device check-in. This capability enables administrators to automate device actions when end-users pick up or cradle their devices.

Apple

SHA-2 Support for Certificate Signing Requests (CSR)

CSRs generated by MobiControl will now use SHA-2 for hashing. This update ensures enhanced security and optimal compatibility with Apple’s services. As part of this update, refreshing and retrieving new Apple Push Notification Service (APNs) certificates will use SHA-2 CSRs.

SOTI Settings Manager

Manage Device Language

Administrators can enable users to manage their device language. Users will have the ability to change their device language from Settings Manager. This capability will only be available for Samsung ELM and Bluebird HF550 devices.

Upgrade Considerations

To continue using the Legacy Remote Control Plugin, Customers must uninstall the current version from their local systems and re-install the plugin via the link present in the 2024.1.1 SOTI MobiControl Web Console. SOTI MobiControl versions 15.6.6 and later will support the new 2024.1.1 remote control plugin, while earlier versions of SOTI MobiControl will not be compatible. Remote Control via SOTI XSight is not affected.

Resolved Issues

MCMR‑31132 Managed App Configuration default values were not being delivered to devices when editing App policies.
MCMR‑32003 The “device plugin outdated” message was appearing with every check-in post upgrade.
MCMR‑33898 Date values were incorrect when exporting custom date attributes on devices.
MCMR‑34091 When the SD card is removed from a device, the SD card information was continuing to be displayed on the web console.
MCMR‑34359 End users were able to turn off app permissions from Google Maps.
MCMR‑34643 Windows CE devices disconnected from servers where additional ports for SHA-1 and SHA-2 certificates were enabled immediately upon enrollment.
MCMR‑34871 The user was not able to manually move shared devices between groups.
MCMR‑35061 Devices failed to retrieve packages/files after SOTI XTreme Hub relocation to another group.
MCMR‑35151 Scheduled profile deployment edit UI was pulling outdated configurations.
MCMR‑35200 Managed app configurations were being displayed inconsistently.
MCMR‑35348 The user was not able to create a Windows Mobile Agent.
MCMR‑35424 Lockdown profile configurations would appear to have no home screen items on the web console after the upgrade despite functioning normally on the device.
MCMR‑35442 Deployment server queue length was showing some discrepancy.
MCMR‑35485 Unable to delete lockdown templates.
MCMR‑35618 The file manager did not allow Japanese input.
MCMR‑35637 iOS and macOS custom profiles page not loading.
MCMR‑35711 Data truncation and archival setting were not working as expected for application feedback logs, leading to growing database tables.
MCMR‑35894 The user was not able to create a new Windows CE/Classic Agents.
MCMR‑35961 Unable to install Entrust certificate.
MCMR‑35967 Changes to user permissions did not take effect immediately after changing user groups.
MCMR‑35988 Path column data disappears when selecting the refresh button.
MCMR‑36008 Windows Modern profiles were continuously reinstalling when assigned with a filter based on a registry value.
MCMR‑36037 "Execute Script Only if Files Transmitted" toggle in file sync policies was disabled upon upgrade.
MCMR‑36094 Searching for devices produced inconsistent results.
MCMR‑36098 File sync policies were missing after upgrade.
MCMR‑36130 The user was not able to update or edit profiles with certificate and Wi-Fi payloads.
MCMR‑36135 File sync policies could not be removed from the web console.
MCMR‑36214 Searching by app name did not produce expected results.
MCMR‑36222 The copy device group permissions window was not displaying correctly.
MCMR‑36238 Pre-saved scripts were unable to be removed from the web console.
MCMR‑36298 The updated legacy remote-control plugin version was not compatible with older versions of SOTI MobiControl.
MCMR‑36334 The export device list action was not working correctly when custom attributes were included in the column view.
MCMR‑36433 Database maintenance was failing due to logs not truncating correctly.
MCMR‑36132 Printers were appearing offline after upgrade.