Why Zero Touch enrollment not start automatically?

mhfaruk
Level 2.0: Eclair

4 weeks ago

 When linking through my actually I am doing

  • First, link customer account successfully through my EMM console.
  • for linking account I have used zero touch iframe 
  • use dpcextra -  {"server":"","enterprise":"enterprises/enterprises_id"}
     
  • after all doing this , when setting up the device the devcie ask for a qr code for enrollment.if I scan qr code enrollment start successfully

My query was

  • Is zero enrollment not start automatically?
  • if start automatically then what the thing that I am missing?

 When linking through zero touch customer portal

  • To add configuration ,I have select DPC Android Device Policy.
  • Add DPC Extra -

{
"android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.google.android.apps.work.clouddpc/.receivers.CloudDpcDeviceAdminReceiver",
"android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE": {
"enterpriseEnrollmentToken": "TTTFDFFKKJKKJJFJFF"
},
"android.app.extra.PROVISIONING_WIFI_SSID": "XXXXXX",
"android.app.extra.PROVISIONING_WIFI_PASSWORD": "XXXXX",
"android.app.extra.PROVISIONING_WIFI_SECURITY_TYPE": "WPA2",
"android.app.extra.PROVISIONING_SKIP_ENCRYPTION": true,
"android.app.extra.PROVISIONING_SKIP_USER_CONSENT": true,
"android.app.extra.PROVISIONING_KEEP_SCREEN_ON": true
}

In both approach enrolllment not start automatically. What I am missing here?

0 Kudos
1 REPLY 1

jasonbayton
Level 4.0: Ice Cream Sandwich

3 weeks ago

Hey, are you devices assigned to a configuration? If ZT initiates ("device is managed by your organisation" message pops up), but asks for a QR code at the very end, it's a misconfiguration of the config.

 

I can't tell offhand which platform you're using, but the referenced config seems to be two different platforms.

0 Kudos