The following DPC identifiers (EMM tokens) can be used during Android Enterprise fully managed (work-managed) provisioning.
To use them, follow the setup wizard on the Android device until a Google account is requested. In place of a Google account, type the DPC identifier beginning with afw#. Check out Android Enterprise provisioning guides for a visual guide (search for DPC identifier).
DPC identifiers
Use Ctrl + F or your device equivalent to search for your EMM solution as it may take some time to scroll through the below tokens line by line.
MobileIron Core
afw#mobileiron.core
MobileIron Cloud
afw#mobileiron.cloud
SOTI Mobicontrol
afw#mobicontrol
IBM MaaS360
afw#maas360
Citrix XenMobile
afw#xenmobile
VMware WS1 UEM
afw#hub
Cisco Meraki
afw#meraki
Shoonya
afw#shoonya
MobileIron Core Telekom
afw#telekom.mi
Knox Manage
afw#knoxmanage
BlackBerry UEM
afw#blackberry
Microsoft Intune
afw#setup
Codeproof EMM
afw#codeproof
Codeproof EMM
afw#codeproof.lg
Codeproof EMM
afw#codeproof.samsung
Android Management API
afw#setup
Test DPC
afw#testdpc
ZENworks
afw#zenworks
SureMDM
afw#suremdm
KACE Cloud MDM
afw#kace
TinyMDM
afw#tinymdm
Manage Engine MDM
afw#memdm
Miradore
afw#miradore
Wizy EMM
afw#wizyemm
Pulse One
afw#pulse
Sophos Mobile
afw#sophos
Fusion EMM
afw#fusionemm
FAMOC
afw#famoc
MobiLock Pro
afw#mobilock
MobileIron Cloud AtWork
afw#mobileiron.atwork
VMware Workspace One
afw#workspaceone
Submit a DPC identifier
If you’d like to see a DPC identifier added to this list, please fill out this form or comment below.
Request a DPC identifier from Google
If your EMM doesn’t have a DPC identifier today and you’d like to request one, fill out this form in the EMM community (EMM community access required).
@jason just found out that the Airwatch DPC Identifier changed from afw#airwatch to afw#hub This was on yesterday 4/3/2019 as far as I can tell. Thanks for all your great work !
Already changed
If you’re still seeing #airwatch please Ctrl+Shift+R or
+Shift+R
afw#workspaceone seems to be valid as well
Also notice inTune has afw#setup listed. I’m guessing that’s a typo?
Hi Team,
Requesting your assistance on one of the opportunity I am working with a customer who is having Lenovo Yoga Book – YB1-X90L . As per their requirement I have done the POC on one device, where all the features they have asked for have been achieved successfully. The POC which I have done, the device is same model, but the OS version was 6.0, however customer have tried to enrol some more devices of same model but on a different OS version i.e. 7.1.1 and they are facing issues on enrolling the devices on AE. After factory resetting the device when they enter the AFW# token, they are getting an error ”Couldn’t find your Google account”. I have tried to hard factory reset the device by getting into the root level, but still the device throwing the same error message.
As per the discussion with the customer that these devices were procured a year back and all the box pack device.
As per the device model I have checked that the device is listed on AE website Android Enterprise Solutions Directory. Please find the link with the video which customer has shared along with the device details.
Any suggestion to fix for this issue.
Nope, Intune is Android Management API
I’ll add ws1. Thanks!
Yeah. I found out about intune just after I posted that. Thanks for the info as always!
Hi @Suman_Chakraborty
Sorry for the delay. The Yoga Book is not an enterprise recommended device despite it sitting in the solutions directory, moreover Lenovo until as of late have been pretty poor supporting Android Enterprise, so it doesn’t surprise me to see you’re facing issues.
With 7.1.1 have you considered trying QR code enrolment (if supported, 6 taps on the welcome screen) or it lieu of that, NFC?
There’s no video link, but I know what you’re seeing.