Zero-touch enables simple, out of box enrolment for Android devices. The following resources may help you to get started.
What is zero-touch enrolment?
Zero-touch enrolment allows IT adm...
Updated 2 years ago
Version 4.0
Blog Post
My current client uses KNOX for this functionality today. But Samsung is only 90% of there deployment so I would like to implement ZTE. I have a few questions if you could help me out.
- Would it be best to use ZTE for all devices once it is in place? Or use Samsung KNOX where possible and ZTE otherwise? I assume the capabilities are the same - so I am inclined to think moving everything to ZTE would be best - but please advise.
- My client buys devices from multiple resellers. I realize we would need to reach out to each of them. But will there be one ZTE portal for this client and the first reseller we contact would set it up - then the second would add to that? Just want to make sure I understand how this will be implemented. I assume once the company's ZTE portal is set up its simple to add integration to their environments [I assume like ABM MDM_server config].
For 1 I think that's a mix of preference, and willingness of your reseller/partners to undertake. Resellers won't often onboard devices - even with proof of purchase - into ZT retrospectively, particularly if you didn't buy them from said reseller. It's worth a conversation in any case. Obviously it's easier to manage everything from one pane of glass, but do you want to migrate 90% of the estate to ZT if it's already working fine in KME? I'm not sure I would for the handful of times you'll need to log in and change something (typically).
For 2 yes for ZT the first reseller would create the customer account. Within the customer account is the customer number you'd provide to the next reseller, and so on. Be sure to approve resellers ahead of attempting registration from the customer account also. And yes, super easy. Here's a guide.
Awesome. Thanks for the quick reply.
KNOX works just fine so we can keep that as-is. I will try to get the resellers to retro add any non-Samsung devices to ZT - that's the primary goal here anyways.
Thanks again.
KME provides more services on the background then ZT, you might want to keep that in mind.
Every Samsung phone comes with a warranty bit, a one time efuse that checks wether a custom kernel has been loaded to the device or not. When that happens, the fuse will change value permanently. KME checks that fuse, so if there was ever any tampering with a device, it will not enroll trough KME. It gives you some peace of mind knowing that devices contain the original hardware.
Besides that, I believe that KME also checks other firmware related stuff and blocks enrollment when it doesnt trust it.
They perform these checks in the free version as well, you don't need to pay for the advanced KME features.
I advise customers to use both in these kind of scenarios. One platform would be better in most cases, but this security check is worth the extra platform in my opinion.
Thank you for the great information. We will definitely stick with KME for the Samsung devices and use KT for the non-Samsung. From the device side their is no difference which is great. Just need to make all admins aware of both portals.
