Control the devices' updates (target version, automatic updates, force an update)

What it is for

BrowserDesk updates itself on the devices. As administrator you decide which version a device goes to and whether at all: you assign a target version to a device or the whole access, lock updates during a test phase or let the devices freely follow the newest version. In the console an access is called tenant.

What you need

• A sign-in to the console with the role Tenant administrator or higher.
• For the release per platform and the forced version of the whole relay: the role system administrator (own relay). On browserdesk.de the operator decides this.
• Devices with a current BrowserDesk version — older devices only receive assignments after an update.

How to do it

A target version for one device (or several)

1. Open Devices and find the device (G1). For several: tick the boxes on the left.
2. Right-click → Manage → Assign version….
3. In the dialog Assign version choose a version under Target version and click Assign.
4. To take it back, use the same place and choose — None (remove assignment) —.

The device downloads the version at its next connection, checks it and restarts — even if it does not do automatic updates itself.

A target version for all devices of the access

1. Tenants → double-click the access (Edit tenant) → tab Devices & updates.
2. Section Version & updates → choose Version for all devices (without their own assignment).
3. Save.

A device with its own assignment keeps it. — none (global version) — means: the relay's default applies.

Lock updates

• Whole access: in the same section tick Lock updates for all devices of this tenant, Save.
• Single devices: right-click → Manage → Lock updates or Unlock updates. Or in the device's details under Overview the row Updates → Lock for this device.

Switch automatic updates on or off

Device setting Automatic updates in the group Software and updates — for a device, the access or the whole relay (G2).

For the whole relay (system administrator)

Settings → Version management:

• Released version per platform: which version devices without an assignment pull, separately for Windows, Linux, Android/Fire TV, relay, macOS and iOS. Below it you see how many devices run which version.
• Forced version: brings all devices of a platform to exactly this version.
• In the same section below: Rollout throttling: Max. concurrent updates limits how many devices download at once (0 = unlimited).

How you know it worked

• In the device's details under Overview: Current version and Target version with the addition "(Update ausstehend)" or "(erreicht)"; if the target comes from the access it says "(tenant, …)".
• On the left Update history: which update ran when from which to which version.
• In the device list the column Version — it can be filtered and grouped.

Good to know

• Order: device → access → relay. The assignment on the device wins.
• Target and automatic updates no longer fight: if a device has a target version or a lock, the automatic update installs no other version — neither newer nor older. Without a target it follows the released version.
• Lock means standstill: a locked device stays on its version even when a new one appears. Someone at the device who clicks update there may still do so.
• Linux: a target that is older than the newest version on the update server cannot be reached by a Linux device. The lock works.
• Without the console: a device can also be brought to the released version by a command on the device itself — see Force an update.
• A device that has not signed in again for more than 14 days may install the newest version once and is brought back to its target at its next sign-in.

If it does not work