Consumer phones are phones we can get from shops.
There are rugged Android devices targeting non-consumer market. Rugged devices are designed specifically for line of business and to be used in places like warehouse, factory and construction site.
For rugged devices which do not come with Google Mobile Service (GMS) or the working environment is isolated with no internet connectivity, Workspace ONE UEM provides AOSP/Closed Network mode as a way to manage Android rugged devices.
You can refer to this list for Android phones come with GMS: https://androidenterprisepartners.withgoogle.com/devices/?
In AOSP mode, devices do not need to get connected to any Google Services such as Google Play and Firebase Cloud Messaging Service to be managed. One of the ways to tell if a device is on AOSP, check the existence of Google Play on a device. AOSP device will use Workspace ONE UEM App catalog for application downloading. The replacement of FCM is Airwatch Cloud Messaging (AWCM). With AWCM, Workspace ONE UEM is able to notify a device by sending AWCM messages.
An AOSP device can be managed very much like an Android for Enterprise device with GMS except
AOSP devices cannot get Apps downloaded from Google Store.
UEM cannot put a restriction to stop user from factory resetting a AOSP device.
It is simple to get AOSP turned on in Workspace ONE UEM. Administrator needs to
Setup Android EMM with a Google ID
Turn on AOSP mode
Please be aware that AOSP cannot be turned off once it is on. So it is highly recommended to have Android Enterprise Mobility Management setup on a parent organisation group (OG) and have AOSP setup on a child OG. In the follow example, AFW is the parent OG and it is where we had Android EMM setup. AOSP was turned on on one of the child OGs: "check-in"
Before EMM is on
After EMM is on
Set up AOSP on a child OG
Make sure you have AWCM enabled for HUB agent. AWCM is for push message sending.
Let’s now look at AOSP device enrollment.
Many of the AOSP devices do not come with a module to enable out of box device enrollment method such as QR code scanning. To get devices enrolled, you will need to have a device connected to a PC running Android Debbug Bridge tool.
This is a KB on how to get ADB running on your PC: https://kb.vmware.com/s/article/2960948
Here are what you will need to do after you have your device connected to a PC running ADB.
Get Workspace ONE HUB agent apk installed. apk file can be downloaded from my VMware portal. It can also be downloaded from https://my.air-watch.com or https://getwsone.com
Setup WSO HUB agent as the device owner of the device and kick start the enrolment process.
Once the above steps are accomplished, the WSO HUB agent will be pinned to the screen and ready for enrollment. In the screen, you can input Workspace ONE UEM URL, Group ID, user credential to have a device enrolled.
Prior connecting your device to a PC and running the commands, please get your device factory reset.
Here are the commands to have agent installed and set agent as the device owner:
1. Command to tell a device is connected successfully via USB:
PC-a01:~ xxxxx$ adb devices
List of devices attached
QWXNU19302102050 device
2. Command to get HUB app installed to connected device:
PC-a01:~ xxxxx$ adb install AirwatchAgent-playstore-release-20.03.32-SNAPSHOT.apk
**Important: Don’t rush to launch the just installed HUB app. Go straight to the next command to set HUB agent as the device owner.
3. Command to setup HUB as DO (Device Owner)
PC-a01:~ xxxxx$ adb shell dpm set-device-owner com.airwatch.androidagent/com.airwatch.agent.DeviceAdministratorReceiver
You will get the following message if you got the HUB setup as DO (Device Owner) successfully:
Success: Device owner set to package ComponentInfo{com.airwatch.androidagent/com.airwatch.agent.DeviceAdministratorReceiver}
Active admin set to component {com.airwatch.androidagent/com.airwatch.agent.DeviceAdministratorReceiver}
In case you get an error like this:
Please perform a factory reset again. If the same warning remains, please check if there is account already set up on your device by going to settings->accounts. Remove the accounts and run the adb set-device-owner command again.
**Important: Now you should see HUB app starts and it is pinned to the screen.
Notes1: “adb devices“ is a command to list out connected Android device ID.
Notes2: “adb install” is a command to get apk file installed to a connected device.
Notes3:“adb shell dpm set-device-owner” sets WSO HUB agent as the device owner.
After you have the commands completed successfully, the WSO HUB agent will start and pinned on screen until you have the enrollment process finished.
Please note that if you need to get an Android with Google Mobile Service enrolled into closed network mode, you will need to deploy a PAC file for a device to use to by pass Google connectivity check.
The PAC file can be hosted on a Web server a device can reach to.
After connecting your Android to a WiFi, open up your Android Wifi advanced option and input the PAC info. Example:
Yorumlar