Workspace One (VMWare AirWatch)

This guide goes over the steps to deploy the BlueFletch application suite via VMWare Workspace One (WS1) using the "Provisioning" or "Products" section of Workspace One.

Deploying BlueFletch Enterprise via Workspace One

Introduction

There are a few different ways to install the BlueFletch application suite via VMWare Workspace One (WS1). This guide will focus on the "Provisioning" or "Products" section of WS1. This method of deployment will give you the ability to control the app versions on devices, and organize the order that software will install and run, so that you can automate as much of the process as possible (depending on device OEM).

System Requirements

• Admin Access to a Workspace One Environment

• BlueFletch Files/Applications

• Android OS Fully Managed devices enrolled in Workspace One

Getting Started

1. Log into the Workspace One (WS1) management console.

2. Go to Devices > Provisioning > Components > Applications.

3. Upload the BlueFletch applications here that you will be deploying.

Adding Start Launcher Intent

1. In the Workspace One (WS1) management console, go to Devices > Provisioning > Components > Files/Actions.

2. Create a new File/Action, select "Android", and name it something like "Invoke Intent - Start EMS Launcher" (the name is not important, just remember what you call it).

3. Go to the "Manifest" tab at the top, and select "Add Action" under the "Installation Manifest".

4. Select "Run Intent" from the dropdown.

5. In the text field labeled, "Command Line and Arguments", copy/paste the following intent, and leave "timeout" set to 0: mode=explicit,action=android.action.intent.MAIN,package=com.bluefletch.launcher,class=com.bluefletch.launcher.Launcher,broadcast=false

6. Select "Save", and then "Save" again to save the File/Action.

Adding a Launcher Configuration File

1. In the Workspace One (WS1) management console, go to Devices > Provisioning > Components > Files/Actions.

2. Create a new File/Action, select "Android", and name it something like "Copy File - Launcher.json" (the name is not important, just remember what you call it).

3. Go to the "Files" tab.

4. Select "Add Files" and then "Choose Files".

5. Navigate to the Launcher.json file you would like to send to devices (locally on your computer file system) And select it. Select "Open". NOTE: Make sure the file is named "launcher.json" before opening.

6. Select "Save".

7. In the Download Path text field enter the following: /sdcard/Download/ems/

8. Leave "Version" alone, and press "Save".

9. Press "Save" again to save the File/Action.

Create a Product to Deploy BlueFletch Apps

1. In the Workspace One (WS1) management console, go to Devices > Provisioning > Product List View.

2. Select "Add Product" and then select "Android".

3. Name the product something like "Install and Start BlueFletch Apps".

4. Add the smart group(s) or organization group(s) you want to deploy to to the "Smart Groups" field.

5. You can also set up an Assignment Rule at the bottom of this page to only target specific device models or other factors within the smart group or org group. Example of targetting only Zebra TC52 devices:
6. Select the "Manifest" tab.

7. Select "Add" and then select "Application - Install".

8. Locate the application & version that you would like to install as part of this product. Select it, and then press "Save".

9. Repeat steps 7 & 8 for each of the BlueFletch apps that you would like to install with this product.

10. Once you have added all the app installs you want to for this product, select "Add" again and this time, select "File/Action - Install".

11. Locate your file/action for starting the launcher, select it and then press "Save".

12. Repeat step 10 & 11, except this time, select the File/Action that contains the launcher.json configuration file.

13. Once you have all of your steps in the manifest, you can reorganize them by pressing the Up/Down arrows on the left-hand side. Make sure that the file/actions are installed after the applications are.

Note: If you prefer, you can create a separate product for the configuration file. This can make it easier to manage configuration file changes without requiring the device to go through the entire install product each time that a configuration change is made.

Granting App Permissions via Workspace One:

App permissions can be granted via Workspace One by setting up a profile.

For Android 10+, follow the instructions below to create a profile with "Grant All Permissions": https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/Android_Platform/GUID-AndroidProfilesCONCEPT.html#permissions-21 Note that on Android 8 & 9, there is a bug that does not allow permissions to be set this way in Workspace One. Refer to the VMWare KB article below for information on setting permissions automatically via workspace one for Android 8 & 9: https://kb.vmware.com/s/article/78590 Or this VMWare-provided blog post: https://communities.vmware.com/t5/Workspace-ONE-Discussions/Manage-your-Internal-Apps-Permissions-on-Android-Enterprise-Work/td-p/516798