Skip to main content
KevinICT
Level 1.5: Cupcake
March 19, 2026
Question

Wifi only devices not enrolling into Intune

  • March 19, 2026
  • 1 reply
  • 99 views

Hi there,

I have a couple of Lenovo K11 wifi only models and the reseller has uploaded the serial number into our AZT account, the device has been assigned a configuration profile which is the same used for mobile phones.

Problem i have is the tablets setup like a personal device and not a corporate owned, i’ve reset the tablet and had the reseller upload the serial number but still the same outcome.

Intune isnt connected to our AZT account and i don’t know how else to troubleshoot this.
 

The following “DPC extras” is what i used for the tablet setup

{
    "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_ADMIN_EXTRAS_BUNDLE": {
        "com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKEN": "#########"
    }
}

 

does someone know what i have done wrong or point me in the right direction please?

kevin

1 reply

Michel
Level 4.0: Ice cream sandwich
March 20, 2026

Hi Kevin, welcome!

 

Couple of things that come to mind when reading this. The code seems to be copied from the Intune learn docs so that should be working, but the following could also cause issues: 

  • the token you use, is that existing in one of the enrollment profiles in Intune?
  • If so, is there a configuration connected to a device group or user in Intune? I’ve had cases a few years ago where the enrollment profile was ignored because there was no other policy. I think thats fixed now, but might be worth testing
  • You are not using the intune bulk enrollment integration if I understand correctly? You have created a profile in ZT and assigned that to the device you are testing with, correct? 
  • Did you try testing over a hotspot? There could be some limitations at work on your wfi network that prevent access to ZTE. By enrolling via hotspot you can rule that out since there is hardly any security / firewall filters active on a mobile hotspot. If a device cannot connect to ZTE it will skip that part and roll out as unmanaged. 

 

Hope this helps a bit, if not let us know what you’ve already tried to rule out problems. 

 

Michel

 

KevinICT
KevinICTAuthor
Level 1.5: Cupcake
March 20, 2026

Hi and thanks Michel for the welcome greeting.

so the point you have address i dont have any issue with them but will explain the best regarding your suggestions;

  1. the token is an existing one within Intune
  2. the token is from a configuration withing the “Corporate-owned, fully managed user devices” and it doesnt direct it to any specific regarding the “Assignment - Grousp” or “Scope Tags”
  3. Bulk enrollment not been configured and ZT is assigning the deployment to test android tablet.
  4. Setup it at home and still the same outcome.

note that the existing token is used for our mobile phones works and it is the same one used for the new tablets. The default deployment configuration works mobile phone via a WIFI connection and pretty sure for an old tablet that has sim card slot. (i’ll reconfirn this)

Only think difference this time is that these tablet is purely WIFI models, Lenovo k11 gen 2 ( TB336FU )

 

kevin

 

Michel
Level 4.0: Ice cream sandwich
March 20, 2026

As shown in the Android directory (https://androidenterprisepartners.withgoogle.com/device/#!/kKn6s3zT7WnPhmrcncMZ) the device should be supported so that should not be the issue. 

 

What happens if you try and scan the QR code, skipping the ZTE part? Does it enroll in Intune correctly? 

 

Its been a while since i’ve connected ZTE to Intune, but I used the following code. Could you try this one? Its copied directly from a working ZTE config profile. I can’t see a difference, but it might help. If this does not work either, I think you should reach out to your device reseller and let them ask for support via partner support. 

 

 

{
"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_ADMIN_EXTRAS_BUNDLE": {
"com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKEN": "YOURCODEHERE"
}
}