Deploying OEM Configuration Applications

OEM Configuration Applications aka OEM Config apps are applications offered by OEMs or Device manufactures to control OEM device specific properties and policies that go beyond the standard Android Enterprise API offering. These applications are developed by the OEMs and follow the OEM Config standard set by Android Enterprise for these applications, making it easier for them to be configured directly from the EMM/MDM console and deployed to your EMM managed devices.

Scalefusion makes it even easier to configure and deploy OEMConfig applications by integrating them right inside the Device Profile, thereby allowing the IT Admins to easily discover and configure them along with other policies. Scalefusion also provides the status information or feedback notifications at a profile level which helps IT Admins monitor the status related to installation of these applications and the status of configuration.

Follow the steps below to configure a OEMConfig application from the device profile and check the status.

Configuring OEM Specific Settings

  1. From the Device profile listing page, click on Edit to start editing the profile
  1. OEM Configurations section displays the curated list of OEM specific applications. Click on Configure button next to the application that you want to configure,
  1. The resulting wizard would display all the policies offered by this OEM as shown below,
    1. Configuration Name: Start by entering the configuration name.
    2. Policy Editor: Start reviewing each policy and edit them and add or set values as per your requirements.
      Some OEM Configurations set all device policies to FALSE/DISABLED by default there by completely disabling them when these apps are deployed. Please ensure that you have reviewed all settings and ensure that their defaults are set properly.
    3. Save: Click on Save to save the configuration.
    4. Cancel: Click Cancel to cancel the configuration.
  2. Once you have configured the settings, click Update Profile.
    1. This action would first automatically publish/push the applications to all your EMM managed devices which initiates the installation of the app. Once the application is installation the configured settings are delivered to these applications.
    2. To delete a configured OEM Config app and unpublish it or edit it subsequently, you can navigate to the same section in profile i.e OEM Configurations
      1. Edit: Editing the settings and updating the profile will automatically push the new settings to the device.
      2. Delete: Delete would delete the configuration and unpublish it from all the devices.
If you are looking to configure DataWedge on Zebra devices, then you can configure Zebra OEM Configuration app from this section and refer to this document (from Step 4) on how to configure data wedge.
If you are looking to set up Remote Control and configure boot/shutdown animation on Motorola Devices, then you can configure Moto OEM Config App from this section. Refer to this document (Step #2 > 4) for the configurations required to be done.

View Configurations Status

  1. Once an OEM specific configuration application is configured in a profile that is applied to the devices, you would notice a new "eye" icon in the quick actions menu.
  1. Clicking on the icon, would display the status wizard that helps you with the information on the status of the configuration on all devices in this profile and allows you to filter and download the information.
    1. Filters: You have the following filters available,
      1. Configuration package: Filter the list by the OEM Config apps that are configured in this profile.
      2. All App Status: Filter the list based on the installation state of the app on the devices. The possible states are,
        1. Published
        2. Installed
        3. Install Pending
        4. Install Failed
        5. Uninstalled
      3. All Config Status: Filter the list by the based on the configuration/settings delivery state. The possible states are,
        1. Pending: Shown when the Scalefusion backend is yet to push the configuration to device.
        2. Unknown: Shown when the Android Enterprise APIs have returned no information
        3. Success: Shown when all the configuration parameters have been successfully applied.
        4. Failed: Shown when at-least one of the configuration parameters could not be applied. Clicking on the status provides you with the details of the failure.
      4. Show Offline Devices only: If selected, this will only display devices which are offline.
    2. Device Information Panel: The table below displays the following information,
      1. Device Name: Name of device on which app is published
      2. Current Installed Version: The current version of the installed app
      3. Group/Profile: The device group and profile of the device
      4. H/W IDS: IMEI no. and other device details
      5. Install Status: Installation status of the application on the device
        1. Status Info: The meta-data on the installation status to help you understand the installation status better.
      6. Published Config: Displays name of the configuration and its current status,
        Feedback notifications for App configurations are in a Beta stage and hence the reporting may not be accurate.
Additional Actions

You can perform the following additional actions from the status wizard,

  1. Download CSV: Download the installation and configuration status report in a csv format.
  2. Search: Search for devices by device name or IMEI number
  3. Re-Publish: Use this option to republish the application on the devices where the application is still in pending state or has failed.
    1. Re-Publish via Legacy API: Use this option to republish the application using legacy APIs. Helpful on devices where the app is not getting installed even after multiple attempts.
  4. Sync Status: Manually sync the installation status of the application. Scalefusion automatically syncs the status after 15 minutes of app publish and hence this button gets enabled after 15 minutes of publishing the app.
  5. Sync Config Status: Force sync the status of the configuration


How did we do?


Powered by HelpDocs (opens in a new tab)