- Download Android device policy App (https://play.google.com/store/apps/details?id=com.google.android.apps.work.clouddpc&hl=en_US)
- From the App scan the Enrollment QR code
- Add the devices to admin as normal
- (Observe) you will have a "Play Store" app and a "Work Play Store"
The devices will have the same icon in admin.
If the Inventory field "Is User-Owned" is True, the device is a BYOD.
I would add this as a column in the client view to more easily identify.
Enrollment Workflow (EMM)
If you have a Google Policy Fileset with Network information in it. You can select it when you generate a QR code. This inserts the information onto the device for easy enrollment.
|Figure 1.1 - WiFi selected in enrollment QR|
The QR code that is generated contains the WiFi password in plain text.
DO NOT leave the QR code just sitting around.
Ability to edit notes (AKA Chromebook Data) that syncs between FileWave (Figure 1.2) and the Device info from your G Suite Admin console (Figure 1.3).
|Figure 1.2 - Chromebook Data||Figure 1.3 - G Suite Admin|
Note that although the Google APIs do not support a remote powerwash, you can now deprovision a device from your Google Admin through FileWave. This places the device is an unmanaged state, until it is next erased and re-enrolled. Accessible from the Client Info view as shown below:
Disable/re-enable (EMM & Chrome)
|Device||Disable (AKA Missing)||Enable|
Varies by Device Manufacturer
For example on a test Lenovo: All apps but play store are disabled. On others the whole devices might be disabled to an unusable state
|Returns to normal|
|Android EMM BYOD|
Varies from Manufacturer
For example on a test Lenovo :Apps installed by FileWave (AKA Work Apps) are disabled.
Receives a notification that "This devices isn't active Contact your IT admin"
|Returns to normal|
|Chromebook||Screen is locked with a message , device is disabled for all users||Returns to normal|
Move device in admin moves in G Suite Domain structure (Chrome)
If you have connected your FileWave with your G Suite ( See: Quick Start Guide for Chromebooks ). You will have your G Suite OU structure mirrored in FileWave Admin (See Figure 1.4)
The new Google permissions to move devices and edit OUs will be disabled for all pre-existing or new admins by default. Only superadmin (AKA fwadmin) has those rights. You must check the box in manage administers for Google rights for any users who need them.
|Figure 1.4 - G Suite OU in FW Admin|
Drag and drop devices amid OUs as you normally would organize things in the admin view. (Note that moving of OUs themselves is not supported in the current Google API.
The Google API only allows for 50 devices moves per call. In Admin if you move more, we break that into appropriate calls of 50 till the move is done.
- Right-Click on the OU you want your new one to be created inside
- Select "Add GSuite OU..." (Figure 1.5)
- Give it a name, description
- Press Create
- Update Model
|Figure 1.5 - Create OU||Figure 1.6 - Remove OU|
- Right-Click on the OU you want removed
- Select "Delete" (Figure 1.6)
- Press OK to confirm
If Delete is grayed out, it might be updating or you don't have permissions. Wait one moment and then R-Click again.
If Delete is not there, there may be objects in that group still.
The FW Extension now gathers these fields in a more reliable way:
- Local Device Name
- Device Serial Number
- Current Logged in user
- Current IP
- Current Asset ID
The Chrome App ID is the same, there is no need to change or upgrade the FileWave Inventory Extension that is being sent. As soon as FileWave pushes updates to the app, the devices update.
Android EMM Location Tracking
Android EMM devices need to install a FileWave "companion" application onto the device that will send us location data. Reference Force Location for EMM Android Devices for details.