Skip to Content
avatar image
Former Member

Afaria Email Access Control, BYOD and Generic Android Devices

Hello everyone,

We are presently in the process of expanding Afaria to personally owned mobile devices (BYOD) and implementing Local Email Access Controls via the Exchange Powershell Cmdlets available in Afaria 7 SP3. From an MS Exchange Perspective, we are implementing by creating Device Access Rules based on Device Type to quarantine devices and allow Afaria to determine which devices should have access to Email.

This is working very well for iOS based devices and Samsung AES capable devices. However, for the more generic device types like HTC, Huawei, LG and Sony, the Access Policy State shows "Blocked" although the Device Compliance State shows "Compliant".

As we continue to implement the Device Access Rules in Exchange, I fear these generic devices will be blocked from receiving email even through the compliance state is "Compliant" because the Access Policy is incorrectly being set to Blocked.

Has anyone attempted implementing local access control for Email using the Powershell Cmdlets for generic android devices where the Access Policy State was properly set to "Allowed"? Again, this works as expected for iOS and Samsung AES devices.

Thanks,

Justin

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Feb 03, 2014 at 12:57 PM

    Hi,

    I am not sure but what i think, According to me ISAPI filter will not work on generic android device it will work only for AES2 and IOS device.

    For Generic device Active sync cannot be managed by Afaria .

    In that case for generic device if you want to manage with ISAPI filter you need to install NITRODESK Client on Generic device and later it will be managed by ISAPI filter.

    After installing the Nitrodesk on generic device. device will get register on device.xml and mail will received on device

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 03, 2014 at 12:22 PM

    Hi Justin,

    We do see the same for non-AES Android devices...

    Do you have any luck in solving this ?

    Peter

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Peter,

      We still have not found any "resolution" though a workaround using Nitrodesk Touchdown may be an alternative. We have not fully explored the capabilities of touchdown as we prefer to stick with the native apps that our user base is used to, so I'm not sure how viable this option would be for us.

      I'm curious - are you using the ISAPI implementation or using the MS Exchange 365 configuration with the PowerShell Cmdlets?

      Justin

  • Feb 17, 2014 at 07:41 PM

    Hi,

    Afaria can apply access policy on the devices where it has setup the email policy. That is the devices email config should have been pushed by Afaria, in that case you can take control of blocking and unblocking using Afaria.

    If the device doesn't have the required MDM API's in case of many non-Samsung devices then you would need a third party app to configure email on those devices. Nitrodesk Touchdown is one of the app which can be used to configure email using Afaria on non-Samsung devices.

    Regards,

    Praveen

    Add comment
    10|10000 characters needed characters exceeded