Device Owner with afw#maas360 Enrollment Checklist

Content

Device owner with afw#maas360 enrollment

• Review documentation Android Enterprise Deployment Guide
• Ensure your devices meet the Android Enterprise prerequisites
  • Recommendation: Try the afw#maas360 enrollment on a few of your devices with varying OS and manufacturer to confirm your set up
• Set up MaaS360 with Android Enterprise Solution Set in Setup > Services using Managed Google Play
  • Managed Google Play (uses a free Google Account)

Note: Managed Google domain integrations do not work with afw#maas360 token enrollments because a google account is automatically created on each device. If you are using a Managed Google domain, then you use your Google account and password instead of the afw#maas360 token

• Make sure you have decided on the type of user authentication you want to use for devices that are enrolling with token afw#maas360
  • Configure Settings > Device Enrollment Settings > Select Default User Authentication Mode
  • Choose the enrollment authentication type you plan to use
    • Corporate credentials – you must configure Cloud Extender or Azure integration for user authentication
    • Local users – you must add local users to the MaaS360 user directory with a local password
      • Hint: You can generate a password and send it to users, or manually add the password when creating the local user.
    • Unique passcode – user and password is not required, a unique passcode is generated as part of the enrollment request
• Configure Deployment Settings
  • Settings > Device Enrollment Settings > Default new Device Addition Mode for Self Enrollment. Ensure the Ownership, Account Type, and OS Versions are selected that you want to default to Android Enterprise enrollment.
• Prepare the MaaS360 Android policy with Android Enterprise settings
• Set the Android policy as the default or assign it to a group
• Create device group(s) or user group(s) to distribute AE approved apps or distribute to all Android devices.
• Approve Apps and configure App settings to be pushed to Android Enterprise (AE) devices
  • Configure policy settings for each app
  • Configure App Config settings for each app as needed
• Distribute approved Apps to a group or all devices
• Start the enrollment process:  Android devices must be new/out of the box, or must be factory reset to start the afw#maas360 enrollment process
• If you are using the unique passcode for enrollment authentication, generate an enrollment request in the portal using Add Device and send the passcode to the person enrolling the device. If the administrator is enrolling the device, you can start the enrollment on the device immediately using the unique passcode, or generate multiple requests and access the requests with passcode later in Devices > Enrollments. Hint: Add the Passcode column to the Enrollments view to view the passcodes.
• Power up the device/factory reset the device, and enter afw#mas360 when prompted for the Google account. The user/administrator is guided through downloading the MaaS360 app and enrolling the device.
  • User/Administrator is prompted for their Corporate ID and Email address
    • The corporate identifier, email, and domain are sent to the user with the enrollment request
  • If you are using unique passcode for enrollment authentication, you are prompted for the unique passcode from the enrollment request
  • If you are using corporate or local credentials, you are prompted for the username and password. 
• The set up is completed, the Android policy and Maas360 App catalog with apps are pushed to the device.
  • If you selected Instant Install, apps are installed automatically