Considerations when migrating from device administrator to Android enterprise

(Jason Bayton) #1

Originally published at:

What is Android enterprise? For information regarding Android enterprise, including what it is, the deployment scenarios stated below and how it can benefit organisations, have a read of What is Android enterprise and why is it used? Android enterprise vs device administrator (legacy) enrolment Unsure of the differences between Android enterprise and device administrator enrolment? Check out Android enterprise vs device administrator (legacy) enrolment. A majority of organisations looking at Android enterprise today will very likely already have a mature Android management process in place centred around the legacy device administrator enrolment model. With this model being deprecated partially with Android P and fully in Android Q, now is the time to start thinking about planning a migration. It is important, therefore, to understand the implications of a migration from a device administrator deployment to one (or more) of the deployment scenarios available with Android enterprise; depending on the deployment scenario chosen it could be very disruptive, but steps can be taken to reduce this. The key to undertaking any migration is communication, planning and as much testing as is necessary to understand every possible challenge an organisation may face when making a fundamental change to how devices are managed. With those in mind, the following must also be taken into consideration for Android enterprise. G Suite or managed Google Play accounts Organisations leveraging G Suite may find it easier to integrate directly with their EMM platform in order to make use of G Suite accounts and authentication when enrolling…