Hi there,
Just so I understand, could you elaborate on what you're trying to achieve with the Google account you used with zero-touch?
You can add the new Google account to your enterprise bind for management by logging in to Play admin settings with the original account and adding the new one there.
If you're trying to link these up to add your existing devices in, this won't work. You'll need to work with a device reseller to add devices into zero-touch.
If I'm not catching on to what you're trying to do please elaborate 🙂
Hi there,
Just so I understand, could you elaborate on what you're trying to achieve with the Google account you used with zero-touch?
You can add the new Google account to your enterprise bind for management by logging in to Play admin settings with the original account and adding the new one there.
If you're trying to link these up to add your existing devices in, this won't work. You'll need to work with a device reseller to add devices into zero-touch.
If I'm not catching on to what you're trying to do please elaborate 🙂
Hi there
Ok, per my above -
You can add the new Google account to your enterprise bind for management by logging in to Play admin settings with the original account and adding the new one there. (Link is in my above comment).
You'll need to perform account recovery on the original account to gain access to add a secondary account. No way around that normally.
Just to highlight also, bind management isn't supported by Google Workspace accounts at the moment, so if you created a new account with "an existing email address" that's fine, if you used a new GW account that won't work.
To your other comments, there is absolutely nothing stopping you from purchasing devices right now. Once you have a customer account for ZT and have created configs that point to your MDM you're set.
You don't even need to link ZT to your EMM through iframe integration, but if you needed to do that you can do with any Google account.
Hi there,
No, they're two wholly different systems. Zero-touch does no device management, rather it directs devices in to an EMM solution for enrolment.
ZT effectively ends when the DPC is downloaded and picks up the enrolment token passed to it via ZT config. Devices are then enrolled into the enterprise created with the Google account used to bind to the EMM and the EMM takes care of everything.
Google accounts associated with ZT are literally there for management of the ZT console only, they don't go near the devices themselves.
No relation. The EMM handles app deployment once enrolled. All apps, policies, and devices are associated with the enterprise ID created when doing the bind with the EMM.
ZT just sends the devices to that EMM.
