DPC Identifier enrollment allows customers to initiate Android Enterprise managed provisioning with no additional external requirements, such as a QR code, NFC tag, or pre-setup with zero-touch. DPC identifier provisioning is simple; at the point where an end user would usually enter their Google account details, a DPC identifier will be entered instead, in the format of afw#identifername. After entering the identifier, the device will download the corresponding Device Policy controller application from the Google Play Store. Managed provisioning will then initiate and EMM enrollment will take over shortly after using the enrollment credentials provided by the respective EMM vendor.
Steps to enroll the device via DPC identifier:
-
Turn on the device from a boxed state, or factory reset the unit if not fresh from the box. You'll must be greeted by the welcome screen.
-
Tap to start the Setup Wizard and connect to a network (Wi-Fi or cellular).
-
Proceed through the Wizard to Google Sign in screen.
-
Enter the DPC identifier of your respective EMM vendor in place of a Google account.
-
The device will identify the DPC app required and start downloading, you may be prompted to approve this.
-
Once downloaded, the DPC will install and setup will complete, moving automatically over to the EMM vendor enrollment flow.
-
Enter the enrollment credentials supplied by the EMM vendor.
-
Proceed with the instructions on screen and complete the enrollment.
Your device is now enrolled and setup is complete.
Contact your EMM vendor for the respective DPC identifier.
Should you wish to manually check for updates, do as follows:
-
Open Settings
-
Either swipe up from the home screen to display the app drawer, and select settings, or
-
Swipe down from the notification area and tap the settings icon present in the notification panel.
-
-
Tap System
-
Tap Check for updates
-
Follow any prompts provided should an update be available
You may note an update is already showing as available or in progress. There are multiple reasons an update may be available but not actively downloading, one of them being the device is not considered idle (which if you're checking for updates, would be accurate).
If you find you must regularly manually check for updates, consider the following requirements for an update to happen:
- The device must be connected to WIFI
- The device must be idle
- The device should be connected to power
Other such factors may impact the ability to download an update for your RHINO device, including enterprise management policies. If your device is managed by your organization, reach out to them for clarity on any/all policies applied pertaining to update management.
