Skip to main content
C
ceermotors
Level 1.5: Cupcake
January 21, 2026
Question

ZTE Enrollment Profiles Issue

  • January 21, 2026
  • 2 replies
  • 0 views

 

Greetings everyone! New day, new challenge.

I’ve received a number of Zebra tablets. We already use ZTE, which works fine, but as you know it assigns devices to a single profile based on the serial number.

The issue is:
These tablets (same model) will be used for many different purposes, and I don’t think it’s efficient to take each device out of the box, read the serial number, and manually assign it to a different ZTE profile. I could easily end up managing 200 different profiles.

So my question is:

Is there a way to let the device choose which group or category it should belong to during enrollment?
For example, during setup the device could ask the user which category it belongs to and based on that selection it would automatically join the correct group and receive the appropriate configuration.

Is this possible? Or am I dreaming? 😄
Has anyone faced this issue and found a good solution?

Thanks in advance!

2 replies

Emilie_B
Emilie_B
Community Manager
January 21, 2026

Hello @ceermotors - hope you're doing well!

 

I think @mattdermody should be able to help with your query as he's the designated expert for rugged devices 😉

M
mattdermody
Level 3.0: Honeycomb
January 21, 2026

I don't think ZTE is necessary or even valuable for Zebra devices in this situation. I cover this in my recent article: 

 

[Day 3] Dedicated to Dedicated: Non-negotiables for EMM/MDM in Rugged Android Deployments | Android Enterprise and ChromeOS Customer Communities - 13794

 

I've pulled in the relevant section here:

 

 Enrollment that Fits the Reality of Rugged

  • Use Android Enterprise Device Owner (AEDO) with a barcode-driven process (e.g., Zebra StageNow). It’s fast, repeatable, and minimizes user taps and mis-taps on the floor. Wi-Fi credentials can be encrypted in the barcode rather than shared haphazardly and manually entered by end users into the Setup Wizard. More granular control over initial network connectivity is also afforded as compared with the limited options available through DPC extras if using the designated AEDO QR method.
  • Avoid Zero Touch Enrollment (ZTE) for rugged Wi-Fi-only devices. ZTE is not "Zero Touch" as it realistically pushes many touches (and possible errors) to end users. There is overhead and maintenance to unenroll and re-enroll devices into the portal as they go in and out of repair. Enterprise-grade devices are often covered under repair contracts due to the nature of the environments they’re used in. This means they are going in and out of repair relatively frequently, and ZTE portal management ends up causing more bottlenecks than the steps it’s otherwise designed to free up. StageNow barcode flows are fewer steps and far more reliable for DCs and stores.
    M
    Moombas
    Level 4.4: KitKat
    January 21, 2026

    Yeah can underline that for Zebra devices as well, depending on the frequent of repairs (we had not so many in our use case but this can be very different in a warehouse or somewhere else). Also it always needs the involvement of the reseller after repair to put the devices back to your ZT account and you might also need to reassign the relevant configuration to it.

    So, i also recommend for enrollment and wiping, use a StageNow profile instead everything else i posted below, outside of knowledge of Intune possibilities ;) 

      M
      Moombas
      Level 4.4: KitKat
      January 21, 2026

      Depends on your setup and maybe which MDM you are using.

      I tell you how we made it work in Mobicontrol (semi automatic) not sure if that's what you are looking for or even if something like that is possible in Intune.

       

      All our devices which should be for stores using the same ZTE rule pointing to 1 specific enrollment policy in Mobicontrol.

      They all land in one folder where they get a kiosk screen in which you have to enter some data manually. In our case: Environment, storenumber and devicenumber (as it's done in html/JS you can use free text fields (we do use regex on those) or drop down).

      This data is stored to an ini file on the device and taken by the Mobicontrol agent to the MDM console and will decide then with further device relocation policies where the device will end up.

      Completely independent of the device serial or IMEI.

       

      So, to your question in general: Yes it's possible. To your question in combination with Intune: I don't know (but would wonder).

        Terms & ConditionsCookie settingsAccessibility statement