Skip to content

Changes in Release 1.132 (2026/10/11)

New: Access to Clients with Machine Groups

Until now, policies could only lead to Assets, Virtual Assets and Subnets. With this release, the laptops and desktops of your users can be policy destinations too:

  • Remote support: let your helpdesk reach every employee laptop via Remote Desktop, SSH or a remote-support tool.
  • Own devices: let every user reach their own other devices, e.g. their office desktop from their laptop.
  • Machine-to-machine: let a management or deployment server reach your clients, whether or not anyone is signed in on them.

The new Machine Groups under Definitions make this manageable:

  • A group contains Assets and Clients, either picked explicitly (Static) or selected automatically by machine kind (Assets + Clients, Assets only, Clients only), operating system, machine tag or user group (Dynamic). Dynamic groups update themselves when machines change.
  • A group declares the services it offers, and can be added to policies directly from its Access tab. This also simplifies policies for Assets: group e.g. all file servers, offer SMB once on the group, and a new file server is covered by tagging it, without editing any policy.
  • As a policy destination, a group makes all its machines reachable. The built-in groups All Clients (every client in the tenant) and Own Clients (the clients of the accessing user) work without any setup.
  • As a policy source, a static or dynamic group grants access to the machines themselves, independently of who is signed in, unlike a user group, whose access only applies while its user is signed in. The two built-in groups are destinations only.

A client must run agent version 1.132 or later to be reachable. See Machine Groups for details and a step-by-step example, and Policies for how they fit into a policy.

Admin Console

  • New: Client creation tokens can register new clients as disabled, like asset creation tokens.
  • Changed: When creating a Managed Subnet and no asset qualifies as its gateway, the side panel now explains that a Linux asset with a second, non-uplink network interface is required, instead of showing No Assets deployed.
  • Fixed: Clicking Apply several times while importing user groups from the identity provider created duplicate groups. Existing duplicates are merged.
  • Fixed: With Microsoft Entra ID, users could intermittently drop out of a group when Microsoft Graph throttled the group sync, or lose all their groups at login when they belong to more than 200 groups.

Agents

  • Fixed: On Windows, stopping the agent service could hang for several minutes while the tunnel failed to come up, and agent updates could repeatedly abort because the old service did not stop.
  • Fixed: Relayed connections could switch back and forth between two relays with similar latency, which showed e.g. as artifacts in video calls. The agent now only changes relays for a clear and lasting improvement, and still fails over immediately when a relay stops responding.
  • Fixed: In the desktop client, the close button disappeared for very long user names or guest domains; the label is now shortened, with the full text in a tooltip.