Downloads, versions and device upgrades

Get the current version

In Downloads, choose “Install with an account” and your system. Download a published unified client without signing in to the website. The page shows version, architecture, size, OS requirements, release notes, and checksum; store releases use official store links. Sign in inside the installed app and enable remote access in settings on supported platforms when needed.

Obtain no-account Agent installation content for a device group in the workspace. The target device does not sign in. Public account installers do not replace group-bound installation content. Downloads distinguishes an empty release list from a failed request; you can use a browser to access existing devices meanwhile.

When the app requires an update

A platform administrator can set a minimum supported version. Older apps receive an update-required response when signing in or refreshing a session. Existing native sessions also lose access to device operations.

Install an available version from the Downloads page on your configured server, then sign in again. Different servers can have different release policies. This policy does not silently downgrade a newer installation or bypass system installation and permission prompts.

Publish software as an administrator

Administrators with platform settings write permission can open Software releases and updates. Workspace administration alone does not grant platform release access.

1. Create a release with its platform, architecture, edition, channel and version.
2. Add an immutable HTTPS artifact URL or official store URL and release notes. Installers require a file size and SHA-256 checksum.
3. Complete platform signing, notarization or store distribution checks and an installation test before confirming the release review. Keep unsigned internal artifacts as drafts.
4. Publish, then select the current version to enable Download center distribution. Enable update checks and set a minimum supported version if needed.

Account-client records retain compatible internal editions: controller for Linux and iOS; full for Windows, macOS, and Android, on the stable channel. Downloads uses this mapping to present one account product without a Controller/Full choice. Publish only integrated unified-client installers that have passed release review. Agent editions and automatic-update binaries are not public account-client downloads.

Published and withdrawn metadata cannot be edited. Create a new version when artifact bytes change. Choose another published release to switch the download entry. Withdrawal disables that release's managed download and update recommendation. Pausing update checks keeps the current download available.

Upgrade device Agents in batches

Batch upgrades support official MeshAgent services with standard Core on Windows, macOS and Linux. They update the device Agent. They do not silently install controller applications, Android APKs or iOS applications.

Create a release with the MeshAgent automatic upgrade binary type and Agent edition. Enter its exact architecture, MeshAgent architecture ID, target build number and SHA-384 checksum. An operator must first stage matching official bytes on each relevant data node. Entering a download URL alone does not stage the file on a node.

After publishing, select Batch upgrade, search for and explicitly select devices, acknowledge that the Agent restart may interrupt sessions, then create the job. A batch supports up to 100 devices and waits up to 24 hours for offline devices. The task restarts the Agent rather than the computer, so remote connections can briefly disconnect.

Monitor progress and stop a job

Dispatched means the node received the upgrade; it does not confirm installation. Success requires observing the target build after the device reconnects. An equal or newer Agent build is skipped.

Open job details for device-level progress. Architecture mismatches, missing staged files, checksum failures and timeouts have distinct reasons. An uncertain delivery is queried on the original node without blindly repeating the installation.

Stopping a job cancels devices that have not been dispatched. An upgrade already handed to an Agent can still finish. Withdrawal, loss of the initiating administrator's permission, or a device ownership change also blocks later dispatch. Resolve the reported cause before creating a new job for devices that need another attempt.