Level 2.0: Eclair

Solved

Intune - Zebra Scanners - not recognized as company devices in ZTP

Forum|Forum|17 days ago
February 16, 2026
3 replies
1 view

Hi, we are using MS Intune and Google Zero Touch Portal, and a large number of Zebra scanners.

We created several profiles in ZTP with DPC extras (JSON) to link the devices to the corresponding Intune enrollment profiles.

However, when the scanners are set up and connected to wifi, they will not identify as company devices, but continue setup in "private" mode.

I assume there is a problem in our JSON config, but I could not find it. I already checked some other discussions in this forum, but could not yet find a solution.

Apologies, if this problem should already be resolved, then I am happy if you point me in the right direction. :)

Thanks very much and best regards

Tobias

Best answer by Moombas

I don't see an issue in the JSON, as said, i think more of a problem the devices recognizing the ZTP (or even other way around).

So, did you check what i asked for?

check behavior from an fully open, unrestricted Wifi
- Optional but recommend: use a stagenow ZT Barcode to provide it to your device
check if the serialnumber (or IMEI if available) in ZTP are claimed correctly
- here sometimes it helped to unassign the configuration from an issuing device and then assign it back again

And as said above already: Please reach out to your reseller who uploaded the devices to your ZTP so they can reach out to Google via the partner portal to look into this issue deeper as we can.

M

Moombas

Level 4.4: KitKat

This issue should be apart from Intune, correct me if I'm wrong here.

Often the detection is the problem. I'm not responsible for Zebra devices on our end anymore but from the past i had 2 topics:

check behavior from an fully open, unrestricted Wifi
check if the serialnumber (or IMEI if available) in ZTP are claimed correctly
- here sometimes it helped to unassign the configuration from an issuing device and then assign it back again

The JSON config comes in place after the detection was successfull, so i guess that's not the case yet.

And i already know @mattdermody will recommend to use stagenow instead of ZTP if possible but maybe has some experience here woth to add.

Otherwise please reach out to your reseller so they can reach out to Google via the partner portal to look into this issue deeper as we can.

M

mattdermody

Level 3.0: Honeycomb

That's correct. I would never under any circumstances recommend using ZTE or Intune to manage mission critical dedicated Android devices, like those from Zebra. I do not envy any admin stuck having to make these components work together.

M

Michel

Level 4.0: Ice cream sandwich

Could you share your JSON code here (without the tag)? That might help with troubleshooting.

And are you using the bulk enrollment integration with Intune or not?

T

TReinholdAuthor

Level 2.0: Eclair

Hi, pls see here an example of one of our config profiles JSON code:

{
"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": "<TOKEN>"
}
}

and yes, we do use bulk enrollment integration with Intune.

Thanks

Tobias

M

MoombasAnswer

Level 4.4: KitKat

I don't see an issue in the JSON, as said, i think more of a problem the devices recognizing the ZTP (or even other way around).

So, did you check what i asked for?

check behavior from an fully open, unrestricted Wifi
- Optional but recommend: use a stagenow ZT Barcode to provide it to your device
check if the serialnumber (or IMEI if available) in ZTP are claimed correctly
- here sometimes it helped to unassign the configuration from an issuing device and then assign it back again

And as said above already: Please reach out to your reseller who uploaded the devices to your ZTP so they can reach out to Google via the partner portal to look into this issue deeper as we can.

Emilie_B

Community Manager

Hello @TReinhold

I just wanted to reach out and see if you had made any progress - I think you've received some great advice from @Michel, @mattdermody and @Moombas 🤩

Have you contacted your reseller? If so, what did they say?

While we wait for your update, I'll mark @Moombas' latest comment as a reply.

T

TReinholdAuthor

Level 2.0: Eclair

Hi, thanks for all your advice... yes, I reached out to our reseller and they are now investigating, I am waiting for them to come back to me.

We will do further testing today for enrollment with ZTE and simultaneously having network team checking inbound and outbound traffic, to see if there might be any blocks.

Regarding StageNow als alternative solution for Zebras, instead of ZTE: I'm not really convinced, as this means our admins would still have to scan barcodes for scanner enrollments; and we want to get rid of those. Moreover, we see the solution with ZTE working for many scanners, so it is basically working, and there must be a reason for those devices where it's not.

Will keep you posted about further results. Meanwhile, thank you for your support.

Best regards, Tobias

Emilie_B

Community Manager

Thanks for the update @TReinhold!

Please keep us posted and don't hesitate to let us know if you need anything else 🙂

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded