Skip to main content

Managing desktop app updates

The desktop app updates itself by default. Turn automatic updates off when you ship each version through your MDM. On a managed Mac, the PKG’s updater installs updates without admin rights, so you can leave them on.

Before you begin

Pick one owner before you deploy:
  • Langdock manages versions: leave the policy unset. In Intune, use the kit’s Deploy.ps1 as the detection script. It accepts the kit’s version or newer.
  • Your MDM manages versions: turn automatic updates off and upload each new version yourself.
On Windows, the kit’s task updates the device as SYSTEM. People choose Restart to Update. A plain MSIX updates each person on their own. Automatic updates need Windows 10 version 2004 or later.

Control updates on Windows

The kit keeps the device up to date on its own. People choose Restart to Update. To stay on one version line, set targetVersionPrefix in HKLM\SOFTWARE\Policies\Langdock to a prefix that ends with a dot, for example 1.42..

Updates on managed Macs

The macOS PKG updater keeps the Mac up to date. It replaces /Applications/Langdock.app without an admin prompt. When Langdock is open, people see Restart to Update. A DMG install has no updater. Run the DMG install script again to update it. To stay on one version line, set targetVersionPrefix in a device profile for com.langdock.desktop, for example 1.4.

How the updater stays current

The kit’s task and the Mac updater take new update logic from each signed release. After three broken runs, they go back to the previous one. Right after install there is no previous version, so Langdock tells people to contact IT until the next release, or until you deploy the kit or PKG again. updater-health.json sits next to state.json on Windows and status.json on macOS. If needsKitReinstall or needsPkgReinstall is true, deploy the current kit or PKG.

Turn off automatic updates

With automatic updates off, Langdock doesn’t install security fixes on its own. You deploy every new version, including security updates.
In Matrix42 Empirum, extend the Setup.ps1 from the deploy guide so it sets the policy on install:
On macOS, set the keys in a device profile: Application & Custom Settings in Jamf Pro, a preference file in Intune, or a custom profile in Kandji. Restart Langdock after you change the policy. When an MSIX or PKG version is no longer supported, Langdock tells people to contact IT. It doesn’t offer Download update. Upgrade your deployment. When a newer version is ready, they see Restart to update. A personal install still offers Download update.

Verify the setting

Restart Langdock and open Check for Updates.
  • Updates off: “Updates are managed by your organization.”
  • Nothing newer: “You’re up to date. Updates install automatically.”
  • A version is ready: Restart to update
  • The run failed: “Updates couldn’t be installed. Contact your IT admin.”
On a Mac, the status file shows off when updates are off.

Deploy approved versions

Do this only when automatic updates are off. Roll out the new kit or PKG the same way as the first install. On Windows, ask people to quit Langdock first.

Turn updates back on

Set updateMode to automatic, or delete it, and restart Langdock. On a DMG or the personal Langdock Setup.exe, remove disableAutoUpdates. In Intune, keep the kit’s Deploy.ps1 as the detection script.