SOTI

Deploying BlueFletch Enterprise via SOTI

System Requirements

• Windows machine for SOTI Package Studio (Windows VM for Mac users)

• SOTI MobiControl account/environment

• SOTI Package Studio

• BlueFletch Files/Applications

• Android devices enrolled to SOTI

Getting Started

1. Log into SOTI MobiControl.

2. Select hamburger in top left, click on Packages.

3. Download Package Studio.

4. Save to your desired destination on your machine.

5. Launch Package Studio-9.

Building Packages using SOTI Package Studio

I. New Package Project

1. Click on File.

2. Then select Create New Package Project (Shortcut = CTRL + N).

II. Project Name

1. This will be the identifier for your package.

2. Each component (e.g. APKs, Files, scripts, etc) should have it’s own package.

3. Best Practice: Naming convention should leverage “BlueFletch”.

Examples:

• BlueFletch - Enterprise Launcher v3_0_12 052020

• BlueFletch - Authentication

• BlueFletch - Support Agent

III. Platform

1. Select Android.

IV. Set OS Version Range

1. Minimum for BlueFletch Enterprise is 5.0.

V. Comments

1. This field is optional.

VI. Vendor

1. Enter BlueFletch.

2. Click Next.

VII. New Package Wizard - Add Scripts

Notes:

1. Only the BlueFletch - Enterprise Launcher app package should require a script.

2. The checkboxes are only recursors to the scripts being added to the package. You will add the scripts themselves in step 10.

3. These options (pre-install, post-install, etc) can be used to have the device execute necessary processes to successfully manage package deployments. (For more information, please see SOTI Scripting Documentation)

VIII. New Package Wizard - Add Files or Folders

1. Reference the Grouping SOTI Packages section below to determine which files or applications are needed and ensure the correct destination on device is set.

2. Adding a File

• Click on "Add ..". to open the Selection box and choose "Add Files ...".

• Choose the File you wish to add from the appropriate location.

• Once selected, input the destination for the file on the device.

• Set the Copy Rule to Replace the file on the device if it is older or if file does not exist on the device.

1. Adding an APK

• Click on "Add ..." to open the Selection box and choose "Add Android APK ...".

• Choose the APK you wish to add from the appropriate location.

• Deselect Automatically Run Activity after Install.

• Once all necessary files or APKs have been added to the package, click Next and you'll be taken to the Size Settings screen.

IX. New Package Wizard - Size Settings

1. Do not alter default settings.

2. Press Finish.

1. "Build Package Now" pop up should appear.

1. If a script is NOT required, then select "Build Package Now".

• Make note of the destination path in Output Window for the “Package Saved at:” location.

1. If a script IS required, select "close" and move to step 10.

X. Finalizing Custom Scripting

1. Navigate to the desired script type from the tree navigation on the left-hand pane and double click the type (e.g. "Post-Install").

1. Add a new line under the header (the header includes the bottom-most line of semicolons) and paste the script text from the Grouping Packages section).

1. Save changes to the script using ctrl +s or from the File dropdown.

XI. Build Package

1. On Menu, select Project (drop down).

2. Select “Build Package” or press F7.

1. Make note of the destination path in Output Window for the “Package Saved at:” location

XII. Repeat steps 1-11 for each of the Packages in the Grouping Packages section below.

Uploading Package Builds to SOTI MobiControl

1. After all packages have been created, navigate browser to SOTI MobiControl.

2. Select hamburger in top left, click on Packages.

1. Click ‘New Package’ in the top, right area of the screen.

• Select ‘Android Plus’ as Platform.

• Click ‘Browse File’ on popup.

• Open the .pcg file from the /built folder noted in step 11 of the previous section.

• Click Upload.

• Repeat all steps for all Packages built in MobiControl Studio based on the Groupings below.

Grouping Packages - In Order of Installation

BEST PRACTICE TIPS : Limit packages to no more than one application at a time so that the packages can be easily updated without having to re-create multi-app packages.

I. BlueFletch - Launcher Config Package

1. Click Add Files.

2. Select customized Launcher.json file from local machine and set destination on device to %sdcard%\Download\ems\

• Make sure the Launcher config is titled launcher.json when being added to the Package.

1. Installing a logo: Select desired Icon and wallpaper png images from local machine and set destination on device to %sdcard%\Download\ems\

II. BlueFletch - Sitelist Package

1. Click Add Files.

• Select the Sitelist.csv from appropriate storage location and set destination on device to %sdcard%\Download\ems\

III. BlueFletch - Device ID Package

1. Add Files > Add Android APK.

• Select the Device ID APK from appropriate storage location.

• Deselect Automatically Run Activity after Install.

1. Scripts The following scripts will initialize Device ID after they have been installed.

• Post Install

1. sendintent -a "intent:#Intent;action=com.bluefletch.ems.deviceid.ACTION_INIT;component=com.bluefletch.ems.deviceid/com.bluefletch.ems.deviceid.MainActivity;end;"

IV. BlueFletch - Messaging Package

1. Add Files > Add Android APK.

• Select the Messaging APK from appropriate storage location.

• Deselect Automatically Run Activity after Install.

V. BlueFletch - Device Finder Package

1. Add Files > Add Android APK

• Select the Device Finder APK from appropriate storage location.

• Deselect Automatically Run Activity after Install.

VI. BlueFletch - Support Analytics Package

1. Add Files > Add Android APK.

• Select the Support Agent APK from appropriate storage location.

• Deselect Automatically Run Activity after Install.

VII. BlueFletch - Auth App Package

1. Add Files > Add Android APK.

• Select the Auth APK from appropriate storage location.

• Deselect Automatically Run Activity after Install.

VIII. BlueFletch - Launcher App Package.

1. Add Files > Add Android APK.

• Select the Launcher APK from appropriate storage location.

• Deselect Automatically Run Activity after Install.

1. Scripts The following scripts will initialize Support Agent and Enterprise Launcher after they have been installed.

• Post Install

1. sendintent -a "intent:#Intent;action=android.intent.action.MAIN;component=com.bluefletch.ems.emm.support/com.bluefletch.ems.emm.support.features.ui.hidden.SilentInitActivity;end;"

2. sendintent -a "intent:#Intent;action=android.intent.action.MAIN;component=com.bluefletch.ems.emm.launcher/com.bluefletch.ems.emm.launcher.Launcher;end;"

Create Profile to Deploy Packages

Once all Packages have been created per the groupings above, a Profile needs to be created for deploying the all of the packages to enrolled devices.

I. Navigate back to SOTI MobiControl Cloud.

II. Select hamburger in top left, click on Profiles.

III. Click ‘New Profile’ in the top, right area of the screen.

IV. Select Android Plus as Platform.

V. General Tab

1. Profile Name

• Apply a profile name that correlates to the packages being added.

1. e.g. "BlueFletch Enterprise Suite"

2. Best Practice Tip - If you have plan to deploy sets of packages that differ by attributes such as location or role, you can use the profile name to reflect those differences for ease of management.

3. Description

• Best Practice - This is good opportunity to utilize information such as “Pilot”, “POC”, or specify test groups, etc. It gives the admin the ability to recognize the purpose of the specific profile.

• Ensure packages get added to the Profile in the same order as listed above.

VI. Configurations Tab

1. If not already set via a separate profile, ensure Restrictions > Feature Control configuration “Disable Verify Apps” is checked.

• E.g. Profile > Configurations > Restrictions > Feature Control > scroll down to Security > check Disable Verify Apps Enforcement.

VII. Packages Tab

1. Select Add.

1. Click the check box next to all Packages uploaded in section “Uploading Packages to SOTI MobiControl” above.

2. Select OK.

3. Using the up/down arrows, ensure the order of Packages matches the Grouping listed above.

VIII. Click ‘Save and Assign’

1. Select to the Device Group containing device(s) for testing BlueFletch Enterprise.

2. Click Assign.

IX. Wait for device(s) to receive assignments from SOTI.

Remotely Wiping a Device (Enterprise Reset)

BlueFletch Enterprise Launcher disables the ability to Enterprise Reset Zebra devices unless in Local Admin mode. To remotely wipe a device you must first enable the InvokeEnterpriseReset parameter on device. Then you can follow these steps to execute a remote wipe of the device(s).

1. Create a .xml file and title it AllowEnterpriseReset.xml

   1. Enter the follow into the file:

      <wap-provisioningdoc> <characteristic version="8.1" type="SettingsMgr"> <parm name="InvokeEnterpriseReset" value="1" /> </characteristic>

   2. Save the file.

2. Create a new SOTI Package.

3. Check Post-Install Script box to add to project.

4. Add Files:

   1. Select AllowEnterpriseReset.xml and set destination to /sdcard/Download

5. Add a script to the Post-Install Script file:

   1. mxconfig /sdcard/Download/AllowEnterpriseReset.xml

6. Build package and add to the appropriate Profile.

7. Deploy Profile.