This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Android Tablet setting up exchange email - HELP

Hi all,

I wonder if anyone can assist me as I have called technical support and chatted with them for over 3 hours with no solution.

I am attempting to provision an android tablet to include an exchange email address through sophos. I have succesfully done this for all mobile devices with no issue, however below is an explanation of the issue with an Android tablet:

Per sophos instructions, as the tablets can not be provisioned like a phone as it can not receive a text message each device needs to be added manually to the system and the tablet must already have an email account in order to be provisioned. We have been using a gmail account to do this and are successfully provisioning the device. However as the device is not connected to an active directory user account we can not figure out how to set up each for for access to exchange email through sophos.

If anyone could shed some light it would be greatly appreciated.



This thread was automatically locked due to age.
  • The tablets are all samsung tablets running 5.0.2
  • Hi Craig,

    this seems to be a Sophos Mobile Control issue instead of Sophos Mobile Security.

    For Android devices, you may have different so called Exchange ActiveSync IDs which are used to identify email clients. Sophos Mobile Control doesn't accept all ActiveSync ID but instead tries to resolve the ActiveSync ID to a user name.

    During a synchronization request the user name is included, therefore, the SMC server searches for a device having the exact user name configured for the "sAMAccountName" property. See also knowledgebase article 121360 for an example / more detailed description.

    So if you want to grant access to that device, you should either link the corresponding LDAP user to it or add a new property called "sAMAccountName" with the corresponding user name configured on the device. See also article 128888.

    Hope this helps.

    Best regards
    Stefan.