[ Sophos Mobile Control platforms ] [ What’s new in version 6.1 ] [ Installation ] [ License reporting ] [ Known issues ] [ Technical support ] [ Legal notices ]
Supported platforms |
Detailed version |
Operation system |
Version |
Windows Server 2008 64 bit |
SP 1 |
Windows Server 2008 R2 64 bit |
SP 1 |
Windows Server 2012 (64 bit) |
|
Windows Server 2012 (64 bit) R2 |
|
Java JDK version |
Version |
JDK 8 (delivered with the installer) |
8u92 |
Database version |
Version |
Microsoft SQL Server 2008 (32/64 bit) |
SP 3 |
Microsoft SQL Server 2008 R2 (64 bit) |
SP 2 |
Microsoft SQL Server 2012 (64 bit) |
SP 1 |
Microsoft SQL Server 2014 Express |
SP 1 |
MySQL |
5.6 |
Mobile operation system |
Version |
Apple iOS |
7.x 8.x 9.x 10.x |
Android |
4.0.3 or higher (tablets and smartphones) 5.0 or higher 6.0 or higher |
Windows Phone 8
Windows 10 Mobile |
8.0.x 8.1.x 10.x |
Windows 10 Desktop |
Windows 10 Threshold 2 or higher |
Browser |
Version |
Internet Explorer |
11 |
Edge (Microsoft) |
10 |
Mozilla Firefox |
30 or higher |
Google Chrome |
35 or higher |
Directory servers |
Version |
Microsoft ActiveDirectory |
As included in the Windows Server versions above. Only Active Directory Domain Services, no AD LDS support. |
OpenLDAP |
As provided by the Zimbra server below |
NetIQ eDirectory |
8.8 SP 6 |
IBM Domino |
8.5.3 |
389 Directory Server |
1.3 |
Email systems |
Version |
Microsoft Exchange |
2007 SP3 2010 SP2 2013 2016 |
Lotus Domino Traveler |
9.0 |
Zimbra |
8.0 |
CA server |
Version |
Windows Server 2008 32/64 bit |
SP1 |
Windows Server 2008 R2 64 bit |
SP1 |
Windows Server 2012 64 bit |
Latest SP |
Windows Server 2012 R2 64 bit |
Latest SP |
Note: The multi user feature available on some devices running Android 4.2 is not fully supported. If the 4.2 multi user feature is used on a device, only the first user that is registered in Sophos Mobile Control can be managed.
Note: Sophos supports only official Android versions. Sophos does not guarantee that the SMC Android client is working with all the different custom ROMs available.
For further information, see https://community.sophos.com/kb/123975.
For details on installing the Sophos Mobile Control server, refer to the Sophos Mobile Control installation guide. For details on installing and setting up Sophos Mobile Control on end user devices by using the Sophos Mobile Control Self Service Portal, refer to the Sophos Mobile Control user help. You can download the product documentation at http://www.sophos.com/en-us/support/documentation/mobile-control.aspx.
Sophos Mobile Control 6.1 comes with license reporting. For further information, see http://www.sophos.com/en-us/support/knowledgebase/120127.aspx.
If you are planning to run the update to SMC 5 overnight please disable the scheduled tasks to stop and restart the SMC server (default: 4:00 am and 4:05 am) if those times interfere with the update and migration procedure. You can re-enable them after the update is finished.
If the Sophos Mobile Control license file is placed in a folder with Japanese characters in the name for installation, the installation process fails.
After changing the URL of the server using the Configuration Wizard the SMC standard license needs to be reactivated. To do so, go to Setup>System setup>License, enter your standard license key in the input field and then click “Activate”.
On some SAMSUNG SAFE devices (e.g. seen on a Samsung S3 mini with Android 4.1.2), installing a root certificate via a profile works fine without any issues. If the profile is removed again from the device via the Sophos Mobile Control web console, the devices synchronizes with the server but the certificate itself is not removed from the device. This is an issue of the Samsung API. According to Samsung, the issue will be fixed by the next Android (Kitkat) upgrade of affected devices, e.g. Samsung S3 mini with Android 4.1.2.
On some SAMSUNG SAFE devices (e.g. seen on a Samsung Galaxy S2 with Android 4.0.3), installing a root certificate via a profile does not work. This is an issue of the Samsung API where a call to a Samsung API returns success although the root certificate could not be installed on the device.
On some SAMSUNG SAFE devices (e.g. seen on a Samsung Galaxy S2 with Android 4.0.3), removing a VPN profile via the SMC admin does not work. This is an issue on the Samsung API on the device where removing the profile via a call to the Samsung API succeeds although the VPN profile is actually not removed on the device.
On some SAMSUNG SAFE devices (e.g. seen on a Samsung S3 mini with Android 4.1.2), Wi-Fi configuration are installed correctly but when the user connecting to the Wi-Fi does not work giving the user an error message "Failed to connect to network". This is an issue of the Samsung API. According to Samsung, the issue will be fixed by the next Android (Kitkat) upgrade of affected devices, e.g. Samsung S3 mini with Android 4.1.2
The current Baidu library used by the Sophos Mobile Control client basically does not offer support of Android 6 or higher. Furthermore, Android 6 introduces new features (App-doze and stand-by mode) that impact the receiving of push notifications and that are not supported by the Baidu library.
On Sony devices it is not possible to configure VPN profiles with L2TP/IPSec PSK with some VPN servers (for example Sophos UTM).
Currently due to technical limitations, the Sophos container apps do not support fingerprint for logon. Therefore, the setting in the General payload of a Sophos container policy currently has no effect. With upcoming releases of the Sophos Secure Workspace and Sophos Secure Email, fingerprint will be supported for logon and the SMC payload setting will be applied.
Installing a recommended or required app via an iTunes link on an iOS device requires the use of Safari. If the use of Safari is restricted, recommended and required apps cannot be installed via an iTunes link.
In some cases the silent trigger sent by the SMC server does not result in an automatic background synchronization. In those cases the user can still synchronize the app manually.
When upgrading a Sophos Secure Workspace for iOS app that is already managed by Sophos Mobile Control, it may happen in very rare cases that Sophos Secure Workspace is no more managed on the device. This is caused by an undefined behavior of the Apple iOS mechanism used for managing the app: the managed settings are lost. Installing the profile again for the device through the Sophos Mobile Control web console takes the app under management again.
Updating an iOS Single App Mode profile does not update all contained settings. The "disable…" options are updated correctly. All other options only work on the first installation of the profile. For switching those settings, the profile has to be removed and installed again. This is an issue in Apple iOS.
Windows Phone devices running 8.1 < GDR1 do not use the Exchange account display name as configured. Instead, they just use a numbering scheme. This display issue does not affect the actual synchronization. Newer Windows Phone 8.1 versions use the name as configured.
The “password required” compliance rule does not work correctly for Windows Phone and Windows 10 Mobile devices if no passcode policy is enforced by SMC. The devices do not report a passcode being set if the user does this without being forced to by a policy. This is an issue in Windows Phone and Windows 10 Mobile.
The “encryption required” compliance rule does not work correctly for Windows Phone and Windows 10 Mobile devices if encryption is not enforced by an SMC "Restrictions" policy. The devices do not report a device to be encrypted if the user does this without being forced to by a policy. This is an issue in Windows Phone and Windows 10 Mobile.
The Windows Phone 8.1 restriction “SafeSearch permission” is not working correctly. Due to an issue in Windows Phone 8.1 the restriction is ignored on the device and defaults to “moderate”.
On devices that run Windows 10 Mobile, Sophos Mobile Control cannot check for compliance with the "Data roaming allowed" rule because the operating system does not provide the Sophos Mobile Control app with the relevant information. When you forbid data roaming, a Windows 10 Mobile device with data roaming enabled is still reported as compliant.
Android devices are automatically enabled through the EAS proxy, if the device was registered with the Self Service Portal. If an administrator has added the device to Sophos Mobile Control, it is required to enter the sAMAccountName in the respective property of the device details view to make ActiveSync synchronization possible. If devices are registered with an LDAP entry and SSP, this is not necessary (this only applies to Microsoft ActiveDirectory). It also is not necessary if the device's ActiveSync Id is already known. That is the case when using Sophos Secure Email or Samsung KNOX.
When entering a password, e.g. in an Exchange email configuration, it may happen that the password is cut off and not all asterisks are shown. The user can still enter any password, although the input field does not show the correct amount of characters entered. This is caused by a defect in the web control within the standard framework used by Sophos Mobile Control.
Internet Explorer may classify the Sophos Mobile Control web console as an intranet site. As a result, compatibility mode is activated by default which results in a corrupted view and erroneous behavior. This browser feature can be disabled in the Compatibility View settings of Internet Explorer by unchecking “Display intranet sites in Compatibility View”.
Exchange ActiveSync traffic without encryption (SSL/TLS) is no longer supported by the internal EAS proxy.
Using the context to delete single devices and then cancelling the dialog leads to disabled actions and links in the device list. Reloading the device list enables them again.
The Android restrictions "Allow app install" and "Allow app uninstall" are labelled with "SAFEv2" but should be labelled "SAFEv3".
When creating a Kiosk mode payload for Android with a custom app the app identifier is a required field. However, this is not correctly validated and saved without app identifier anyway.
The deletion of customers having Apple DEP profiles configured fails. To delete those customers, the Apple DEP profiles need to be deleted manually before deleting the customer.
When profiles are installed on devices and then later are renamed the list for profile, removal tasks in task bundles might be confusing. It might list the profile with the old name.
Installing root certificates as part of policies is always reported as successful. The actual list of installed certificates can be checked in the device details.
Assigning empty policies without any settings to a Windows Mobile device does not correctly update the installed policy details displayed in the web console. Instead, settings of previously applied policies might be shown.
The restriction for Copy & Paste on Windows 10 Mobile does not work for some apps. Those apps still allow Copy & Paste actions.
The link to the EAS proxy setup file in the web console (Setup>System setup>EAS proxy) points to an outdated file of the last SMC release. The new setup file can be downloaded from the MySophos portal.
The web service interface for apps has been modified to allow configuring the app category and managed installation flags.
The generic NAC web service interface is deprecated. Customers should switch to the REST web service which offers the same functionality.
The web service resource "appreputation" is deprecated. Customers should use the "appgroups" resource instead.
All web service resources now have additional create and update methods which no longer rely on form data. Instead, they can be used with JSON-formatted data which is easier to produce.
The deprecated interfaces will be removed in a future version.
You can find technical support for Sophos products in any of these ways:
Copyright © 2016 Sophos Limited. All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise unless you are either a valid licensee where the documentation can be reproduced in accordance with the license terms or you otherwise have the prior permission in writing of the copyright owner.
Sophos is a registered trademark of Sophos Limited and Sophos Group. All other product and company names mentioned are trademarks or registered trademarks of their respective owners.