|Pages layout corrupted after Sophos Mobile update
Some pages of Sophos Mobile Admin might look corrupted after you’ve updated
your installation of Sophos Mobile.
Workaround: Clear your browser cache and reload the page.
|Synchronizing an Android device with an Exchange server
The Sophos Mobile EAS proxy automatically recognizes Android devices enrolled
by the user in the Self Service Portal. When you enroll the device in Sophos
Mobile Admin, you must enter the sAMAccountName value in
the respective property of the device details view to allow ActiveSync
This isn’t required for devices registered with a Microsoft Active Directory
account and the Self Service Portal or when Sophos Mobile knows the device’s
Active Sync ID. The latter applies to devices using Sophos Secure Email or
|Admin console might look corrupted in Internet Explorer
Internet Explorer might classify the Sophos Mobile Admin console as an
intranet site. As a result, the compatibility mode is turned on by default,
resulting in a corrupted view and erroneous behavior.
Solution: To turn off compatibility mode, clear the Display intranet sites in Compatibility View
check box in the Compatibility View settings
of Internet Explorer.
|Plain Exchange ActiveSync traffic is no longer supported using the internal EAS
||Exchange ActiveSync traffic without encryption (SSL/TLS) is no longer supported
by the internal EAS proxy.
|Customers having Apple Device Enrollment Program can’t be deleted
The deletion of customers with Apple DEP profiles configured fails.
Solution: To delete those customers, delete the Apple DEP
profiles before deleting the customer.
|Task bundle tasks for profile removal don’t list the current profile names in
||When you rename profiles, removal tasks might show the old profile name.
|Detecting deactivated Defender on Windows 10 computers doesn’t work in some
||In some cases, Windows 10 computers might be reported as compliant even if
Windows Defender is turned off. This is because the compliance rule Defender activated can only check if the Defender
service is running. It doesn’t check if real-time protection is turned on.
|Removing duplicated Android profiles using a task bundle doesn’t work
||An Android profile that has been created by using the Duplicate command in an older version of Sophos
Mobile can't be removed from devices using a task bundle.
|Some Windows 10 devices don’t register correctly for push notifications
Some Windows 10 computers don’t register correctly for the Windows
Notification Service (WNS). There’s a time-out of their push registration
after 30 days, and the devices fail to renew the registration automatically.
Although the Sophos Mobile server enforces the renewal, some devices send the
old, invalid push registration information to the Sophos Mobile server when
they re-register. As a result, the Sophos Mobile server can't send push
notifications to these devices to synchronize the built-in MDM agent.
This is a known issue in Windows 10.
|Accurate server time required to set up Android Enterprise
||If the system time of your Sophos Mobile server deviates by more than 15 minutes
from accurate time, you can’t set up Android Enterprise using the Managed Google
Play Account scenario. This is because the Sophos service that manages Android
Enterprise communication classifies the request from your Sophos Mobile server
as malicious and rejects it.
|Number of users invited to Apple VPP at the same time is limited
||When you invite too many users to the Apple Volume Purchase Program (VPP) at
once, Apple might reject further requests for a few minutes.
We will fix this
issue in a future version of Sophos Mobile.
Workaround: Reduce the number of users included in the
|Android zero-touch enrollment and Samsung Knox Mobile Enrollment not possible
with self-signed certificate
If you use a self-signed SSL/TLS certificate for your Sophos Mobile server,
you can’t use Android zero-touch enrollment or Samsung Knox Mobile
Solution: Use a certificate issued by a globally trusted
certificate authority (CA) instead.
|Not possible to save HTML-formatted text
In some cases, you get an Text contains forbidden HTML
elements error when you try to save SSP enrollment texts or
system messages that contain HTML formatting, although the text you’ve
entered is valid.
This issue is caused by an error in the HTML parser library.
Workaround: Change the font size of underlined text and
delete any styling attributes.