(12.4-de) Update

This article shows how to configure app update settings in IGEL OS.

Apps can only be installed by the user if Permit local app installation is enabled under Security > Update. For more information, see Installing IGEL OS Apps Locally on the Device.

Menu path: System > Update

Open

Automatic reboot of system once app is installed

☑ After app installation, the device reboots automatically. The user cannot postpone the reboot. 

☐ After app installation, there is no automatic reboot. The user decides when to reboot. (Default)

Timeout for automatical reboot in seconds

Time period between the app installation and the reboot. (Default: 60)

Use a bandwidth limit while updating

☑ Limits bandwidth usage during the downloading of updates to the value set under Limit bandwidth used for updating.

☐ Bandwidth usage is not limited during the downloading of updates. (Default)

Limit bandwidth used for updating

The value to which the bandwidth is limited during the downloading of updates. You can give the value with KB, MB, or GB as the quantifier. If no quantifier is given, the value is in megabytes. (Default: 2MB)

Seconds to wait for network connection during a multi stage update

A multi stage update is cancelled if no network connection can be established during this period. (Default: 60)

Activate app after the installation

☑ Apps are directly activated after installation, no separate action is needed from the UMS Web App. (Default)

☐ Apps are activated through a separate action from the UMS Web App. 

Check for and download updates for non pinned apps on boot

This option helps keep the apps on the device up-to-date by checking for updates on each boot. This is potentially security-relevant

Non-pinned apps are all apps that are not assigned to a device via the UMS, regardless of whether the assignment was made via a profile or directly. This applies to apps that are dependencies of other apps, for instance. Example: The app Citrix Multimedia Codec is a dependency for the Citrix Workspace App. 

☑ On each boot, the device checks for updates of non-pinned apps. If updates are found, they are installed on the device. (Default)

☐ Updates of non-pinned apps are not checked automatically.

Check for and download updates for non pinned apps on given calendar time, use the crontab syntax to specify the calendar time

This option helps keep the apps on the device up-to-date by checking for updates periodically. To define the period, use the crontab syntax.

Non-pinned apps are all apps that are not assigned to a device via the UMS, regardless of whether the assignment was made via a profile or directly. This applies to apps that are dependencies of other apps, for instance. Example: The app Citrix Multimedia Codec is a dependency for the Citrix Workspace App.

If the defined checking time has been missed because the device has no network or cannot reach the UMS or the IGEL App Portal, the update check is queued until the connection is available again. If the defined checking time has been missed because the device has been powered off, the update check will not be queued.

Possible values: Crontab syntax; if the field is empty, no update check will be performed. For details on the crontab syntax, see https://man7.org/linux/man-pages/man5/crontab.5.html or check out the interactive tool at https://crontab.guru/.

Repositories

Prioritized list of repositories used for app updates

To manage the list:

• Click 

  Open

  

   to create a new entry.

• Click 

   to remove the selected entry.

• Click 

   to edit the selected entry.

• Click 

   to copy the selected entry.

Clicking  brings up the Add dialogue, where you can define the following settings:

• Certificate

• Priority

• Repository URL

Use only repositories deployed by the UMS

☑ The device can only download apps from repositories for which the UMS acts as an update proxy.

☐ The device can download apps from all the configured repositories. (Default)