This article provides an overview of Supported Enterprise Mobility Management providers (EMMs) along with FAQs and resources
Starting with RealWear’s Release 11 Firmware for HMT (released Feb 2020), RealWear’s HMT and now also Navigator 500 product lines support modern Device Owner, Fully Work Managed enrollment leveraging Android Enterprise management APIs. You can now easily enroll devices with most EMM (Enterprise Mobility Management) systems via use of an enrollment QR code.
For customers using an EMM that does not support Device Owner management of AOSP (Android Open-Source Project) devices, legacy Device Administrator is still available. However, Device Administrator APIs are being deprecated in the most recent releases of Google’s Android OS and modern Device Owner management provides significantly greater security and capability to administrators.
Non-GMS (Google Mobile Services), AOSP Devices
For a device to be GMS certified, the device must first comply with Google’s Android Compatibility Definition Document (CDD).
RealWear (and other Android head-worn wearables) are an innovative new class of edge devices which are on the leading edge of mobile computing. There is no category in Google’s Android CDD for head-worn wearable computers.
RealWear is motivated to establish an industry category or profile for GMS compliance for head-worn devices for hands-free use cases. While RealWear is beginning dialog with Google on this subject, nothing can yet be announced, and Google is in full control of its platform.
Frequently Asked Questions
Q: What if I am using Device Administrator (often called “Device Admin”), to manage my RealWear devices? Isn’t Device Admin deprecated in Android 10 which is incorporated into RealWear’s Release 12?
Google has announced that some device admin APIs are deprecated in Android 10 and recommends that customers work with their Enterprise Mobility Management (EMM) solution provider to migrate to Device Owner management.
For customers also using RealWear Cloud to manage RealWear devices: Of the four Google management APIs deprecated in Android 10, only PIN complexity control is implemented in RealWear Cloud. This functionality has been reimplemented for RealWear Cloud console management of Android 10 devices. This means that RealWear Cloud customers can continue to control the complexity of their RealWear device PINs without any change in functionality with Android 10 & 11.
For customers using a third-party EMM provider that does not support Device Owner management of RealWear devices: Contact your EMM provider to formally request Device Owner management of RealWear devices. Request a plan on how to effectively manage your RealWear devices with Device Admin until Device Owner is available.
If you would like to use RealWear Cloud to manage your PIN complexity, contact your RealWear Cloud IT admin or sign up for RealWear Cloud here.
If for whatever reason customers feel they need additional time to execute their upgrade plans, they can exercise all options outlined in RealWear’s Firmware Update and Support policy. Regardless of the management situation, RealWear recommends working closely with your company’s EMM IT administrator, your EMM solution provider and your dedicated RealWear contacts on your RealWear device management plan moving forward.
Q: Is Microsoft Intune compatible with RealWear devices?
Yes! Microsoft Intune (a part of Microsoft Endpoint Manager) offers support for AOSP (Android Open Source Program) device management. This enables enterprises to provision, configure, and secure RealWear devices. Enterprises are increasingly using Intune with Microsoft Teams to enable remote collaboration with frontline workers on the job. See here for the full FAQ
In most cases, enrollment is simple:
- Generate a Device Owner QR code from your EMM system, vendor provided staging application, or one that’s custom generated
- Scan the QR code on a brand new or factory reset HMT or Navigator device
- Follow the enrollment prompts
For specific instructions or more detailed information, please contact your EMM admin or EMM provider or review the enrollment guides below. RealWear has tested and worked with many of the most common EMM providers. The following providers are certified by RealWear to work with the HMT:
Devices can be enrolled in one of two styles of management – Device Owner (Modern Android Enterprise Management) or Device Administrator (Legacy Android management). RealWear recommends modern Device Owner-based management where supported, as it allows for greater control and enables more enterprise features for the administrator(s) and user(s), We also allow Device Administrator based management where required and supported within your enterprise environment.
To use either device management style, HMT devices such as the HMT-1 and HMT-1Z1 must be running at least Release 10.5 (Device Admin only), and it is recommended to be running at least Release 12.x firmware. (Android Enterprise or Device Admin). For more information on Release 12.x, please visit our firmware Release Notes page. Navigator 500 series devices will all run the minimum firmware requirements out of box.
Microsoft Intune AOSP
Microsoft has now added support for the distribution of both SCEP and PKCS Identity Certificates, as well as Trusted Root Certificates, to Android Open-Source Project (AOSP) devices like the RealWear HMT-1®/HMT-1Z1® and Navigator® 500 series devices. This now allows Intune customers to take full advantage of modern Android management with AOSP devices.
What should I do?
With this new functionality through Intune, your deployment is even easier to manage than ever. Immediately contact your appropriate department and alert them that Intune now supports distribution of identity certificates for use with Wi-Fi configurations to RealWear devices such as RealWear HMT-1®, HMT-1Z1®, and RealWear Navigator® 500 series.
- Android Enterprise Guide(requires Release 10.5.x).
- SOTI MobiControl Enrollment Guide for Android Enterprise Based Management
- SOTI MobiControl Enrollment Guide for Device Admin Based Management
VMware Workspace ONE (AirWatch)
Note: VMware has announced upcoming changes to Android management using device administrator.
- VMware Workspace ONE (AirWatch) Configuration Guide for RealWear HMT-1 & HMT-1Z1 (For Device Admin Based Management)
- VMware Workspace ONE (AirWatch) Enrollment Guide for RealWear HMT-1 & HMT-1Z1 (For Android Enterprise, Managed Device Enrollment)
- VMware Workspace ONE: Android Enterprise High Level Configuration Guide
Other Enrollment Guides
The adoption of Android Enterprise Standards means that other EMM providers are also supported to a lesser extent – at this time in Device Admin mode only. As support for these providers expands, we will make additional guides available. Device Admin based management requires the HMT to be running at least Release 10.5.x.
- IBM MaaS360– Device Administrator Enrollment Guide
- Microsoft Intune – Device Administrator Enrollment Guide
- MobileIron Cloud (now Ivanti Neurons) – Device Administrator Enrollment Guide
- MobileIron Core (on-prem) – Device Administrator Enrollment Guide