Back to top

Best practices for using Knox E-FOTA

Last updated September 27th, 2024

Categories:

Environment

  • Knox E-FOTA
  • SOTI MobiControl

Overview

This guide provides some common best practices that enhance your experience with managing device firmware.

Lock your firmware to a stable version

To ensure the continuity of business-critical apps and avoid risk of app failure due to new, unexpected OS updates, you can lock the firmware used for your enterprise devices using the Lock Current Firmware feature in Knox E-FOTA.

This feature prevents new untested firmware from being pushed to your fleet of devices, and restricts access to the Software Update screen on the devices.

Allocate test devices and plan for testing

We recommend that you allocate at least one test device per model for testing all new firmware. Use the test devices to test the updated firmware version and ensure all business apps and required features work as expected.

After you confirm that the tests are successful, you can update your devices.

If there are any issues with an app as a result of a firmware update, please notify your software vendor for a solution.

Apply security updates frequently

Ensure that your devices have the latest security patches and fixes and are up-to-date with the latest tested firmware.

You can use the Specific Firmware or Latest Upto feature in Knox E-FOTA to update within your current OS version.

Depending on when your firmware was locked, there may be multiple OS version updates available for your devices. We recommend using the Latest Upto feature to test one OS version higher than your current version.

For example, if your test device is running Android 13, you can update and test Android 14, instead of directly updating to Android 15.

Is this page helpful?