Android deployment just got easier, maybe. Those familiar with setting up Android devices in supervised mode (a necessity to remove previous users Google Accounts), will know that previously both Android Zero Touch (AZT), and Knox Mobile Enrollment (KME) were required if a mix of Android manufacturers was utilized. Samsung would not work with AZT, and no other Android would work with KME. The latter is still true, but fortunately the former has changed. Samsung devices can now be deployed with AZT.
You may only need AZT to deploy all Android devices. In most circumstances we recommend it. We have found that companies who have both KME and AZT connected to their resellers consistently have issues where their Samsung devices are added to both programs – causing a critical enrollment issue. Devices must go through only one program, they cannot be in both and enroll successfully.
LINQ Recommends:
“Let AZT be your main program
& keep KME for the one-offs.”
Is there a catch to stop using KME? There are not a whole lot of differentiators between the two, but there is one stand out feature of KME. How do I add devices purchased elsewhere from a 3rd party that cannot be connected as a reseller (Amazon, eBay, Best Buy, etc)? There is no method with AZT, but KME does have a feature to do so: the Knox Deployment Application. If your company sources devices from unorthodox locations, you may consider holding onto KME. There is a combination approach where you keep KME essentially just for the Knox Deployment Application but we recommend refraining from connecting it to any resellers. Let AZT be your main program and keep KME for the one-offs.
Unless Samsung adds new critical functionality we expect most folks to let KME go due to admin convenience. Why deal with an extra token to maintain, an extra credential to manage, or the chance that a reseller will add a device to both (causing an issue), when AZT can handle Samsung devices? The Knox Deployment Application may be reason enough, but as of now we do not see a whole lot of reason to automate both.
In summary, Android Zero Touch (AZT) has made multi-manufacturer deployments smoother by accommodating Samsung devices, reducing the need for Knox Mobile Enrollment (KME) in most cases. While KME still has value for specific use cases, like adding devices from third-party sources, AZT now offers a more streamlined solution for most deployment needs. If you’re ready to simplify your Android deployment strategy and cut down on management hassles, LINQ can help you optimize your setup. Visit our main site to explore how our managed mobility services take the complexity out of mobile management, so you can focus on what really matters.