Google Staff

As individual tools, both Android zero-touch enrollment and dual-SIM devices offer a wealth of business benefits. But until recently, the two IMEI numbers - one for each SIM card - in a dual-SIM device meant integrating dual-SIM with zero-touch was unreliable and dependent on SIM configuration.


The good news: we’ve enhanced dual-SIM support in zero-touch, improving the reliability of dual-SIM enrollment, and simplifying management.


What does this mean? 


This improved integration is a step forward, and addresses the known issues some users have previously experienced when provisioning dual-SIM devices with zero-touch. It means dual-SIM devices don’t need to be registered as two separate devices to be reliably managed. It also minimises the risk of devices being missed during provisioning and getting stuck in a reset loop, or randomly undergoing factory reset. 


There is no action required to activate this fix, and you’ll only be visibly impacted if you’ve experienced the issues above. Otherwise, we’d recommend you continue to follow the steps below as best practice.  


Going forward, we’ll be looking to streamline the process of registering dual-SIM devices further, but for now...


Here's how it works:

  1. Lead with the lowest IMEI:

For zero-touch to recognise and configure both SIM profiles, the device initially needs to be registered with the numerically lowest IMEI. For example, if the two IMEI numbers are 000000000000001 and 00000000 0000002, you would register the first. 

  1. Two-Step Setup:

Once the device is powered-on and set up it will download the latest Google Play services. Zero-touch will then detect the device, register its serial number, and prompt a factory reset.

  1. Complete compatibility:

The next time you set up your device, both SIM profiles will be provisioned through zero-touch, applying your pre-configured settings and apps. Cue smooth sailing.


Tips for a smooth two-step

  • Communicate with your reseller: Make sure they understand the importance of registering with the lowest IMEI for dual-SIM devices. 
  • Test, test, test:  When integrating dual-SIM devices with zero-touch, begin with a test batch to identify and troubleshoot any hiccups. You may also wish to check this documentation for any known issues.
  • Documentation is key: Clearly document the specific steps for dual-SIM zero-touch deployment so users know what to expect when setting up, especially as a device factory reset is currently required. 


For more details including prerequisites, configurations and a getting started guide, check out this zero-touch enrollment for IT admins article.


Now, it's your turn to share your thoughts. Do you currently use a dual-SIM device? If so, how do you use it? Was it provisioned through zero-touch? 


Let's keep the conversation going in the comments below!



*Edited on 12 Feb 2024 to add further context on fix

Level 3.0: Honeycomb

I gave this a go this evening - dual SIM device with two IMEIs running Android 10.


I registered the first (lower) and it was detected by ZT fine. It enrolled, pulled down Google Play Services and.. nothing? 


I see no additional data in ZT, be that as a customer or reseller, so I'm not sure what to expect here now. It's been over an hour so far with no further prompts.


I'm hoping I'm misunderstanding this and the two factory resets implied isn't actually a thing. I couldn't imagine making the current registration experience any worse for customers who are already at the mercy of resellers to do something [registration] customers themselves can do with near every other OOBE solution but that would certainly top it. 

Level 3.0: Honeycomb

Hi @Rose,

thanks for letting us know and welcome here in the community.

I wonder if this change was already implemented as i would expect that both numbers needs to be claimed and that for example the batch for uploading/changing configuration assignements will change so we can add IMEI1 and IMEI2 in two seperate fields for the same device but can't see such a change.

Google Community Manager
Google Community Manager

Thanks so much for your comments and feedback here @Moombas and @jasonbayton


Based on your questions, we've updated some of the original text above just to make it a bit clearer what we are referring to here. This is a fix for some devices that were experiencing issues previously, if you weren't impacted there is no change here. 😀


I hope this helps to clarify things. 


Thanks again (and I hope you both had a great weekend). Speak soon.


Level 3.0: Honeycomb

Appreciate it @Lizzie, is there an ETA or vague outlook on something a little more permanent a fix?

Google Community Manager
Google Community Manager

Thanks @jasonbayton. As far as I'm aware there isn't an ETA on updates regarding this at the moment.


But, I do think if there are specifics you would like to be considered related to this, it would be great to share them here in the community. I will gather them up and feed them back to the team working on dual SIM, which will be super helpful as they develop this further. 


Thanks so much,