Knox E-FOTA On-Premises 23.04 release notes

Improvements to the Knox E-FOTA firmware downloader

To reduce the number of firmware versions you need to download for your on-premises server, the Knox E-FOTA firmware downloader now allows you to select target firmware versions to download for your on-premises server.

The latest list of available firmware versions can be obtained as a input.json file from the Knox Admin Portal homepage. You can browse for this file in the firmware downloader, as well as a scenario.json file containing the current firmware versions of your enrolled devices.

After uploading these two files, you can then select specific firmware versions for download. Note that if your PC is behind a proxy server, you also need to enter your proxy server host IP and port before you can download the firmware.

Support for a certificate password field in configuration file

The Knox E-FOTA On-Premises agent now allows you to input required passwords through an additional field in the efota_config file. If you’re familiar with the Android API, you can also add an Android intent listener to define the password.

See Step 5 — Download and install the agent app for more details.

Improvements to service performance

Starting with the 23.04 release, Knox E-FOTA On-Premises now automatically evenly polls device groups for updates. If you allocated a maximum bandwidth per device in the campaign policy, the agent ensures it meets the download speed limit by stopping and starting the firmware download as needed.

Enhancements to bulk device deletion

Previously, Knox E-FOTA On-Premises didn’t require additional confirmation from you when bulk deleting devices.

With the 23.04 release, when you delete devices in bulk, a dialog asks you to confirm before the operation begins.

Enhancements to device tags

Prior to the 23.04 release, Knox E-FOTA On-Premises only supported device tags up to 10 characters long. When the maximum device tag length was reached, no error message would display in the console.

To allow for easier differentiation between devices, device tags up to 45 characters long are now supported. Tag limitations are also dynamically shown as you enter the device tag — for example, an error message notifies you when you enter a tag 46 characters long.