t must be possible to enrol devices running Android for Work (v1) against a BES12 server.
Details:
- activation profiles / procedures should be updated so that is matches attached table
- a corresponding device policy client (DPC) application must be made available, preferably the BES12 Client should act as DPC
- an activated Android for Work device must be visible as such in the BES console
- for "AfW App" based devices the installation/provisioning of the app should be seamless
- provisioning flows should adhere to flows recommended by Google
Use Case:
An enterprise wants to enable their device users to use Android for Work and use BES as their EMM service.
Business Justification:
- Android for Work is expected to be the unified approach to EMM on Android devices (based on information from Google)
- BlackBerry needs to support AfW to stay relevant as an EMM vendor for Android and provide true multi-platform EMM
A user must have the ability to enroll and Android for Work (v2) device against a BES server in *Corporate-only* mode
- the administrator must be able to specify that a device user can activate an Android for Work (v2) device in Corporate only mode
- a corresponding device policy client (DPC) application must be made available on Google Play
- an activated Android for Work (v2) device must be visible in the BES console and the enrollment mode must be provided
Use Case:
An enterprise wants to enable their device users to use Android for Work on Android-L AfW certified devices and use BES as their EMM service.
Business Justification:
Android for Work is expected to be the unified approach to EMM on Android devices. BlackBerry needs to support AfW to remain relevant as an EMM vendor for Android.
A user must have the ability to enroll and Android for Work (v2) device against a BES server in BYOD/Mixed-use mode
- the administrator must be able to specify that a device user can activate an Android for Work (v2) device in BYOD/Mixed-Use mode
- a corresponding device policy client (DPC) application must be made available on Google Play
- an activated Android for Work (v2) device must be visible in the BES console and the enrollment mode must be provided
Use Case:
An enterprise wants to enable their device users to use Android for Work on Android-L AfW certified devices and use BES as their EMM service.
Business Justification:
Android for Work is expected to be the unified approach to EMM on Android devices. BlackBerry needs to support AfW to remain relevant as an EMM vendor for Android.