Setting up Elemez agent on Android devices

The following article guides you through the set-up process of  Elemez Android Agent app on the Scalefusion managed Android devices.

1. Downloaded the elemez.apk agent app from the link provided by the Elemez team.

2. Token Retrieval: In your Elemez dashboard click on your username in the top righthand corner and select Enrollment.

   1. A Token String is displayed, and this can be locally saved by clicking on the download icon. By default, the filename is elemez.token. Save the Elemez.token file downloaded and note its location.
      

      

      
      

      

      
      

3. Adding The Elemez Android Agent to Scalefusion: Add Elemez Application in Scalefusion: Navigate to Application Management > Enterprise Store and click on Upload a New App button > click on Upload Android App.
   

   

   1. Select the Elemez APK and click on upload.

   2. Once the APK is uploaded go to the Elemez app details.
      

      

   3. Under App Information, select Manage Permissions.
      

      

   4. Grant All App Permissions and click on Save.
      

      

4. Adding the Elemez OEM Extensions: Follow the same steps as above to upload the OEM Extension you wish to add to your environment.

5. Publish the Elemez.apk to all devices to be monitored.

6. Publish the Extension only to devices matching the Manufacture. For example, Zebra Extension should only be installed on Zebra Devices.

7. Post Install Remote Command: Once the APK is installed (and relevant extension if available) you must issue a Remote Command in order to start the Elemez client and begin reporting data.
   

   Note:

   Please refer to our guide on how to create Remote Commands.

   1. For Devices WITH an Extension installed, build a Launch Activity remote command as such:

      1. Mode: Explicit

      2. Action: com.b2msolutions.elemez.MDM_TOKEN_ACTION

      3. Package: com.b2msolutions.elemez

      4. Class Name: com.b2msolutions.elemez.activities.AutoEnrolmentActivity

      5. Extras:

         1. Type: String

         2. Key: token

         3. Value: <enter the token string from Step 2 above>
            

            

   2. For Devices WITHOUT and/or extension installed, build a Launch Activity remote

      command as such:

      1. Mode: Explicit

      2. Acti
         on: com.b2msolutions.elemez.MDM_TOKEN_ACTION

      3. Package: com.b2msolutions.elemez

      4. Class Name: com.b2msolutions.elemez.activities.AutoEnrolmentActivity

      5. Extras 1:

         1. Type: String

         2. Key: token

         3. Value: <enter the token string from Step 2 above>

      6. Extras 2:

         1. Type: String

         2. Key: serial

         3. Value: $device.serial_no

      7. Extras 3:

         1. Type: String

         2. Key: imei

         3. Value: $device.imei_no
            

            

8. Deploy the Launch Activity command to the appropriate target group/device.

9. On a target device, you can tell if the install was successful by opening the Elemez

   app and clicking Status. The device should say Enrolled.
   

   

10. The device will start appearing in the Devices list in the Elemez Console as well.

Known issue

• Allowing Battery Optimization: Even when selecting GRANT for android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS in the App Permission Settings, it occasionally does not appear to actually grant the permission. This

  could cause inconsistent or incorrect data to be reported from the device

Note:

You can streamline the process of issuing Remote commands by scheduling them to "Run at first install" or setting them to execute on specific days.

1. Navigate to Device Profiles & Policies > Device Profile.

2. Edit the Device Profile.

3. Go to Run Commands section and toggle on the Enabled button for the Launch activity command.

4. You can toggle on the “Run at first install” button or toggle on the “Schedule” button and select the days, time and time zone.