Forum Discussion
Zero-Touch-Registration is not available
- 2 years ago
Hello everyone,
I hope you are doing well.
I wanted to come back to you all with some positive news a fix has been implemented for this issue. I've heard from a couple of you that this is now working. If you could all check your impacted devices please to see if this has been resolved and let me know, that would be a great help.
Once again a massive thank you for all the feedback you have shared in this discussion, it has really helped to get this resolved.
Hope to hear from you soon and thanks again.
Lizzie
P.S - I will mark this as resolved and update the service announcement, but do keep me posted if you believe this isn't the case. Thanks.
- 8 months ago
Hey everyone,
I hope you are doing well. As this issue is now resolved and it's quite a long discussion, to avoid confusion with any future comments I'm going to close this topic for new replies now. I hope this is all fine with you.
If you are experiencing something similar or want to discuss something related, please do create a new topic here in the community (here is the direct link to do it) and we can carry on the conversation.
Thanks so much,
Lizzie
Hi Eric,
a provisioning QR looks like this (Example from my QR code generator for Soti as MDM but with that intune expire date added as you use intune, not sure if you need it) but tried to rework it for Intune:
{"qrCodeContent":
{"android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM":"I5YvS0O5hXY46mb01BlRjq4oJJGs2kuUcHvVkAPEXlg",
"android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME":"com.google.android.apps.work.cloudpc/.receivers.CloudDeviceAdminReceiver",
"android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION":"https://play.google.com/managed/downloadManagingApp?identifier=setup",
"android.app.extra.PROVISIONING_WIFI_SSID":"Wifi_SSID",
"android.app.extra.PROVISIONING_WIFI_SECURITY_TYPE":"WPA",
"android.app.extra.PROVISIONING_WIFI_PASSWORD":"WifiPassword",
"android.app.extra.PROVISIONING_USE_MOBILE_DATA":true,
"android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED":true,
"android.app.extra.PROVISIONING_SKIP_ENCRYPTION":true,
"android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE":
{"com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKEN": "YourEnrollmentToken" ,
"PROVISIONING_MODE":"FULLY_MANAGED_DEVICE"}
},
"expirationDate": "2025-12-31T18:29:59.920206Z"}
The bold ones are those i changed because of Intune, the underlined bold one is the extra line you need to add.
Thank you, I had the code in the wrong place, but using the QR Code Tiger online app is yeilding me with an error message: Wrong QR Code Ask your IT admin for the correct code. So I must need to use a better QR code generator? My code that I was able to download from Intune is:
{
"qrCodeContent": {
"android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.google.android.apps.work.clouddpc/.receivers.CloudDeviceAdminReceiver",
"android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM": "I5YvS0O5hXY46mb01BlRjq4oJJGs2kuUcHvVkAPEXlg",
"android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://play.google.com/managed/downloadManagingApp?identifier=setup",
"android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED":true,
"android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE": {
"com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKEN": "NDEBIBNS"
}
},
"expirationDate": "0001-01-01T00:00:00Z"
}
Intune does have a spot that allows you to edit the scope tags of the token but that yields in a no access error message, and I am using the super admin.
- EricW2 years agoLevel 1.6: Donut
Update, I figured out why my new QR codes would not work. I was pasting in an extra line of code that should not be there when creating a new QR code. after I deleted;
{
"qrCodeContent":and generated the code it worked just fine!
- Moombas2 years agoLevel 4.1: Jelly Bean
Hi Eric,
but as far as i know (i don't use Intune) "qrCodeContent" should work but only if you have the "expirationDate" in there as well or your {} are done wrong. But in your case the expiration date looked like wrong, the date must be in the future and maximum 65 years ahead.