Skip to Content
avatar image
Former Member

Afaria 6.6 - Android Configuration Manager Channel questions

Hi experts,

We have a couple questions regarding the Configuration Manager Channel for Android devices:

  1. Is it possible to permanently disable the bluetooth connections (as long as the Afaria device admin is in charge): On our test device (Samsung Galaxy Gio) we run a this configuration manager channel and when bluetooth is turned on, this channel will turn it off. But the user is still able to turn it on afterwards. Isn't it possible to turn this completely off so that the user can't turn this on afterwards?
  2. Is it possible to disable the camera functionality? For this we use a test phone with the Afaria AES2 app. And we have set the Enable camera item on "NO" in the Samsung Miscellaneous policy. But the user is still able to use his camera even when this channel has ran on his device?
  3. We can do a wipe for a device from the Afaria Administrator, but is it also possible to do a partial wipe? Because now this does a Factory Reset of the device? Shouldn't it just wipe all the data from the moment that the Afaria App was installed and the device was enrolled? So that the user does not have company data, but has still his own data when he leaves the company for example?

Thanks in advance

Kind Regards,

Robin

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Aug 13, 2012 at 07:12 PM

    Hi Robin,

    Regarding your bluetooth question, did you check KB 8152 on Frontline? Following is the header:

    FAQ: How does the Bluetooth settings work for Android devices?

    Check the following out for your question:

    If the "Enable Bluetooth" is checked with radio button "No" selected under "Samusung ->Miscellaneous" policy, then the Bluetooth setting on device will get disabled and grayed out. Users will not be able to make any changes.


    If the "Enable Bluetooth" is checked with radio button "No" selected under Android and and "Enable Bluetooth" with radio button "No" selected under "Samsung ->Miscellaneous" policy then Samsung's bluetooth will take precedes over the Android on the device when delivered. In this particular scenario, the bluetooth setting on device will be gray out and user won't be able to make any changes on the device.

    Same goes with the camera. Check if the channel has run properly and connectivity is still established after the channel has run. Try to pull out the device logs at the time of synchronization.

    Regarding your third question, you need to remove the control for the device and remove Afaria from Android devices by deactivating the device administration privilege and uninstall the client.

    Regards,

    Shival


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 18, 2013 at 08:13 AM

    Bluetooth and camera can be restricted but it depends on which device you are using. Restriction on bluetooth and camera is possible on certain Android devices. Like Bluetooth can be restricted on Samsung devices, where as Camera can only be restricted for certain devices.

    For your third query, Afaria has provided various functionality for eg. if you want to remove certain applications. For Android, You can create configuration policy and in Application policy. Yo can select install/update/remove and give package name and select remove. In this way you can remove certain applications from devices.(Possible in case of samsung)

    For removing files, you can create session manager channel and remove files from devices.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Okie.. Let me clear more

      Afaria for Android are into two part AES2 ,AES 1 and NON AES ..

      AES are samsung device ( Note : not all samsung device are AES device ,you can check with MDM checker )

      Samsung device which are non aes will have the same features for rest of non aes device.

      Bluetooth can be manually on if the device is non aes.

      For camera restriction : Android OS 4.0 x and above or AES device can apply the policy.