Starting Android 7+, majority of the Rugged OEM manufacturer have met Android Enterprise requirements for their devices. Android Enterprise EnrollmentĪndroid devices can be either enrolled as Android Legacy or Android Enterprise. With Android enterprise, Google has moved away from using OEM service which in the past required EMM to create OEM service for each OEM framework. As soon as OEM releases a new feature, we can add the respective app config value in our assignment page on the UEM console to configure the device. This enables zero-day support from EMMs on any new capability offered by an OEM. Zebra has published their OEMconfig app called ‘Zebra OEMConfig powered by MX’. For example, Samsung has published OEMconfig app called ‘Knox Service plugin’ in the play store. In addition to this, OEM specific capabilities can be set by leveraging App configuration (key-value pairs) on an “OEMconfig” app, published by their respective OEMs on the play store. Profiles, applications and products are installed on the device using the native Android APIs.If using relay server, only Application components and File/Action components are delivered by a Relay Server. Products can be delivered from either Device Services server or Relay server, depending on whether or not a Relay Server is active at the OG the device is enrolled. Hub downloads the profiles and applications, pushed as Apps&Books, only from device service server. Hub is the management client on the device and is required to be installed in order to manage Android devices.The retry interval value to make active connection to AWCM is two minutes by default in the HUB agent. In case of no activity or connectivity issue, AWCM can become disconnected. ![]() Note, when set to always running, Hub maintains a constant connection with the AWCM server outbound. Settings are found on the console under Settings > Devices & Users > Android > Hub setting. We recommend using AWCM for our deployments. Communication methods: Real-time communication between the console and device happens over either the AWCM (AirWatch Cloud Messaging) or Google’s FCM (Firebase Cloud Messaging) service.This document only covers most commonly seen use cases and scenarios in the industry today. Note: Since all environments and use cases are unique, please use your best judgement. This can be leveraged by partners and industry experts to successfully deploy Rugged Android devices. This blog addresses specific use cases and deployment considerations for Android Enterprise Rugged device deployment in enterprises.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |