ControlOne Agent Release Notes

ControlOne Agent v2.9.0 — Release Notes

Release date: May 06, 2026 (Beta)
Release date: May 13, 2026 (GA)
Applies to: ControlOne Agent

Bug Fixes

  • Device Posture — Datto RMM Detection: Fixed an issue where DPC failed to detect the publisher and thumbprint for Datto RMM binaries, causing posture policies using Datto presets to fail. Posture checks now correctly validate these services.
  • Teleport Search: Fixed a bug where the Teleport search field cleared itself while typing, preventing zone search from working. Search now filters results in real time as expected.

Improvements

  • Custom Session Timeouts: Partners can now configure idle session timeout and hard session lifetime per tenant in Company Admin Settings. Defaults: 7-day idle, 30-day hard. Customize to meet PCI, HIPAA, or CMMC requirements.
  • Agent Telemetry: Expanded telemetry to include tunnel connectivity probe tracking, periodic network adapter statistics, and current process list in diagnostic uploads. No partner action required.

Update

Agents update automatically based on your tenant's update policy. No manual action required.

ControlOne Agent – Version 2.8.6

Release date: Mar 11, 2026 (Beta)
Release date: Mar 16, 2026 (GA)
Applies to: ControlOne Agent
 

Bug Fixes

Improved policy-based routing behavior on Windows: The agent previously generated very small PBR subnets which caused Windows to automatically create special routes for certain addresses. In some cases, Windows treated the highest IP in those subnets differently, which could make specific destinations unreachable even though general connectivity was working. This update adjusts how PBR routes are generated so Windows does not apply those special routing rules. Partners and customers will see more reliable connectivity to affected services without needing local PBR bypass workarounds.

ControlOne Agent – Version 2.8.5

Release date: February 18, 2026
Applies to: ControlOne Agent
 

Enhancements and Bug Fixes

Smarter local DNS bypass behavior: The agent previously installed local DNS bypass routes in a way that could exclude certain customer-configured nameservers from the tunnel, making hosts that depended on them unreachable. This fix limits when those bypass routes are used: they are only installed when policy-based routing (PBR) requires them, and they are not installed if the nameservers are already on the network. Partners and customers who use local adapters with nameservers that are reachable via the agent will see correct connectivity without workarounds.

ControlOne Agent – Version 2.8.4

Release date: February 11, 2026
Applies to: Windows and macOS agents

Enhancements and Bug Fixes

Reliable startup updates: The agent now handles update checks more reliably when a device comes online after boot. This change was needed because early startup networking can be intermittent and previously caused delayed or missed checks. Partners should see more consistent update awareness after reboots, reducing manual verification.
 
Clearer tunnel failures: Terminal error states now report more explicit failure conditions during tunnel setup. This was needed to remove ambiguity that slowed down troubleshooting and extended recovery time. Partners should be able to identify root causes faster and resolve issues with less back-and-forth.

Safer cloned deployments: Devices created from golden images now avoid duplicate agent IDs by ensuring unique identifiers on first run. This change was required because cloned IDs could cause conflicts and inconsistent device reporting. Partners can deploy images at scale with fewer collisions and more predictable management.

ControlOne Agent – Version 2.8.3

Release date: January 21, 2026
Applies to: Windows and macOS agents

Enhancements and Bug Fixes

  • macOS Tahoe support in Device Posture Checks (DPC): macOS Tahoe is now selectable and correctly detected in DPC policies, with improved version comparison logic to support Apple’s updated versioning format.

  • Improved agent window placement on macOS: The agent window now opens on the same monitor as the user’s cursor, improving usability for multi-monitor setups.

Was this article helpful?
0 out of 0 found this helpful