Help › Manage › G7

Distribute software (packages, rollouts)

Describe software as a package, release it for an access and distribute it to one device or all devices — in waves, with a dry run and a result per device.

Preview this guide has not yet been clicked through on a real device. Button names and steps come from the program but may differ in details.

For
Account administrator
Applies to
Cloud · Own relay
Licence
service "Software distribution" (Cloud)
Right in the console
Technician (distribute); Tenant administrator (create and release packages)
Controlled device
Windows · macOS · Linux
Control from
Browser

What it is for

With software distribution you install or remove programs on your devices without opening a session. A package describes how a program is detected, installed and removed. You release it for your access and then distribute it to one device or all devices of the access. In the console an access is called tenant.

What you need

  • Role: technician or higher to distribute; tenant administrator or higher to create and release packages.
  • Cloud: the service "Software distribution" (paid Cloud; not in Free). Own relay: always.
  • Access: the rule Allow software management must not be Off (G3).
  • Device: online, device setting Software management (install/remove packages) not Off (on out of the box).
  • Packages have sections for Windows, macOS and Linux (Debian and RPM systems). The package sources Chocolatey and winget only exist on Windows.

How to do it

Step 1: Create a package

  1. Sidebar Scripts & packages → tab Software. You see Software packages.
  2. New package. In the dialog Edit package: - Metadata: name, Version, Display name, Publisher, Category, Tenant (— global (all tenants) — or your access). - Tab YAML: how the software is detected, installed and uninstalled. A wizard builds a skeleton. - Files: attach installers and further files. - Test run: try the package on exactly one connected device. Dry run (changes nothing) and Check only (changes nothing) change nothing.
  3. Save. Raise the Version after every change — otherwise devices do not detect an update.

Step 2: Release

  • Drag the package in the list onto your access in the tree on the left. A right click on the package removes the assignment.
  • In the package it can additionally be released to specific devices or groups.
  • Only active, released packages can be distributed.

Step 3: Distribute

  1. Devices → right-click a device → Run & deploy → Deploy software….
  2. Choose the package, Next.
  3. In the section Deploy package: - Mode: Install if needed (recommended), Force install (repair), Check only (changes nothing) or Dry run (changes nothing). - Intent: Install or Remove. - Target: All devices of the tenant or Selected devices only.
  4. Deploy.

Distribution runs in waves of at most eight devices at a time. Devices that are offline are noted and skipped; the rollout continues.

Single programs from Chocolatey or winget (Windows)

In the details of a Windows device under Software you see the installed software. There you can directly Install a program via Package source (Chocolatey or winget) and Package ID (e.g. git, 7zip). Under Updates available pending updates are listed with Update all.

How you know it worked

  • The rollout's run view shows phase and result per device.
  • In the device's details under Software the program appears after the next scan (Refresh re-reads the inventory on the device).
  • Tab Updates under Scripts & packages: devices with pending package updates from Chocolatey and winget.

Good to know

  • Test the package before the rollout: Test run with Dry run (changes nothing) on one device shows what would happen.
  • Global packages (badge "System") are maintained by the system administrator; you use them but do not change them.
  • Unmeasured on devices: there is no documented measurement of software distribution on real devices — especially not for macOS and Linux.
  • Distribute software in several steps or on a schedule: as a step in a workflow (G8).

If it does not work

You seeMeaning and remedy
"No software is assigned to “…” — assign some in the library first."No package is released for the access. Step 2.
A device is marked as skipped in the rolloutIt was offline. Distribute again later.
"software management disabled by tenant policy"The rule Allow software management is Off (G3).
„Softwareverteilung ist in BrowserDesk Free nicht enthalten, mit einer Cloud-Lizenz schon.“ (software distribution is not included in Free)The service is missing — G4, Prices.
The device reports no update despite a new versionThe Version in the package was not raised.