White Papers
Abstract
Profile owner with manual enrollment
Content
Profile owner with manual enrollment
- Review documentation: Android Enterprise Deployment Guide
- Ensure your devices meet the Android Enterprise prerequisites
- Recommendation: Try the manual enrollment on a few of your devices to confirm your set up
- Set up MaaS360 with Android Enterprise Solution Set in Setup > Services, choose one of the following.
- Managed Google Play (uses a free Google Account)
- Managed Google domain (uses a Google Admin account, usually for GSuite clients)
- Make sure you have decided on the type of user authentication you want to use for devices that are manual enrolling
- 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:
- If you are using the unique passcode for enrollment authentication, generate an enrollment request in the portal using Add Device and send the enrollment request with passcode to the person enrolling the device via sms or email.
- Publish the self service enrollment url to all your users by placing it in an internal location with instructions for enrolling or you can also generate individual enrollment requests using Add Device and send the self-service url via sms or email
- Users can type the self service url or the url from the sms text/email generated in the enrollment request in the browser on their device. They can also use the QR code sent in the enrollment request.
- The user downloads and installs the MaaS360 App
- User 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 google account will be automatically created if you selected the Android Enterprise integration using a Managed Play account. If you enabled the integration with a Managed Google Domain, the user is prompted to enter their Google username and password.
- The setup is completed, a work profile is created on the device. The Android policy and Maas360 App catalog with apps are pushed to the device work profile.
- Apps with the "Install Automatically" box checked off in the portal will begin to install with no user interaction required.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSXX","label":"IBM MaaS360"},"ARM Category":[{"code":"a8m0z000000070xAAA","label":"ENROLLMENTS"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
28 April 2020
UID
ibm16202549