MobiControl[productSupport]
To support new functionality mentioned herein, SOTI MobiControl's minimum system requirements have been updated to .NET Core 3.1, Windows Server 2016 and Microsoft SQL Server 2016 SP2 CU12.
We strongly recommend following the standard IT change control practices and testing of product upgrades in pre-production environments.
Contact SOTI's Professional Services and Support Team or visit the product documentation for information on proceeding with your upgrade.
SOTI MobiControl now supports Corporately Owned, Personally Enabled (COPE) deployments with Android Corporate Personal device management. This type of Android Enterprise device management lets organizations apply a work profile to a fully managed device. Work apps remain entirely separate from the employee’s personal apps and content. Since the device is fully managed, administrators can enforce device policies and restrictions that keep the device connected to SOTI MobiControl, even if the employee disables the work profile. On the personal side, employees can create their own accounts and choose which apps to install from the Google Play Store without that information being reported to SOTI MobiControl.
Generally, Corporate Personal devices support the same features as Android Enterprise Work Managed devices. Some differences include the new Corporate Personal enrollment option and a dedicated set of profile configurations for Corporate Personal devices. Corporate Personal is available on devices running Android 8.0 or later.
SOTI MobiControl now communicates with the modern Apple Push Notification Service (APNS) endpoint for the enrollment and management of Apple devices. Modern APNS promises greater efficiency and security than the legacy APNS endpoint it replaces. The move to modern APNS includes several updates to minimum system requirements for SOTI MobiControl. Administrators should consult the APNS Changes Impacting SOTI MobiControl Customers article on SOTI Central for more information on the new system and security requirements.
Companies can now establish secure communication between enterprise services within their network and SOTI MobiControl cloud instances without opening an inbound port. The latest version of SOTI Cloud Link agent, v3.0, facilitates communication to enterprise services through an outbound port and initiates all application requests from the SOTI Cloud Link agent.
SOTI MobiControl v15.2 is not compatible with previous versions of the SOTI Cloud Link agent. Administrators will have to upgrade the agent component on their local server. They will also need to contact technical support to prepare their SOTI MobiControl cloud instance for the transition.
In the next generation console, context menus can now be opened by right-clicking on components in the user interface. Right-click replaces the vertical three-dot button that previously appeared throughout the console. Right-click anywhere on a row in the Devices grid to select the device and open its Device Actions menu at the same time. Right-click is also supported on device groups and on the Profiles, Compliance Policies and Packages grids.
The three-dot button remains in sub-level modal and dialog windows.
The following REST APIs were introduced in SOTI MobiControl 15.2.0:
| MC‑100636 | The server side script feature in File Sync rules was made read-only for on-premises instances and removed entirely for cloud instances. Users can use this feature by contacting SOTI Support. |
| MCMR‑21327 | Importing packages was not successful due to the case sensitivity issues in the package content |
| MCMR‑22018 | The console sent false notifications of database maintenance failure |
| MCMR‑22160 | Server upgrade from 13.4 to 15.1.1 was unsuccessful due to long running database operation timeout |
| MCMR‑22185 | Some Android devices reappeared in the console after unenrollment and deletion |
| MCMR‑22409 | Improved Japanese translation for Windows Modern Feature Control |
| MCMR‑22455 | Incorrect OEMConfig values for the Ascom application were sent to devices |
| MCMR‑22551 | Editing previously assigned Windows CE/Mobile and Desktop Classic Lockdown profiles was failing |
| MCMR‑22566 | Clicking the “Default” button did not clear the fields in the Advanced Configuration portion of an Application Catalog Rule |
| MCMR‑22590 | Management service attempted to retrieve certificate expiration information from deleted deployment servers |
| MCMR‑22711 | Deletion of saved scripts was blocked if a Windows CE lockdown profile configuration existed where speed control was not configured |
| MCMR‑22747 | Managed Google Play applications did not synchronize with server |
| MCMR‑22759 | Delete was unsuccessful for device groups containing “+”in the group name |
| MCMR‑22770 | The “Allow Sharing between Work and Personal” feature control option was not enforced correctly |
| MCMR‑22892 | Windows XP agent stopped responding when installing a profile in self-serve mode |
| MCMR‑22941 MCMR‑23220 | Added missing MNC code for Webbing Hong Kong Ltd |
| MCMR‑23016 | Upgrade from 15.0.2 to 15.1.1 was unsuccessful due to a database related error |
