a year ago
ControlOne Agent 2.0.1
What's New
With the ControlOne Agen 2.0.1, we have made several enhancements. These enhancements include:
- All new branding, login flow, multi-factor auth experience, and many UX improvements.
- New high visibility system tray icons representing the connection state and status. mceclip1.png
- Improved responsiveness, energy efficiency, CPU + memory utilization on Windows and macOS.
- The Agent now reacts to controller messages in a fraction of the time, such as when a device is quarantined because of a device posture failure, or when a user's Zone assignment is changed by an admin.
- Status now displays "Account Pending" when the User's assigned Zone has no Cloud Gateway configured.
- The connection status byte counters now display the rate (not volume) of data securely sent and received by the Agent through the ControlOne platform.
- Faster connection setup + reconnection times, and more robust failure avoidance including a new DNS based probe.
- A new command line interface `controlone-cli` is now included in the installation directory -- for Nerds only :) Try the `--help` option to get started.
- Wifi / Lateral movement protection status is now displayed in the main panel.
- Added automatic log rotation.
Bug Fixes
- The Agent would use more CPU than necessary while failing Device Posture Check or when the system was unable to reach the ControlOne platform.
- The tray GUI could be running without a system tray icon or a main window, on Windows.
- The tray GUI would sometimes appear in the task bar on Windows.
- When Windows "hotspot mode" was enabled, the Agent's connectivity and guests of the hotspot would be unable to pass traffic.
- The tray GUI was not auto launching when installed an AD joined system, or would not launch when logging into Windows with cached Azure credentials.
- A new ControlOne virtual adapter was being created more often than necessary on Windows.
- A login startup item would appear in macOS System Preferences application as an unsigned binary called "open" in macOS Ventura (13.x).
- Fixed a bug preventing the local gateway IP from being displayed on macOS.
- The Agent would spawn more threads than necessary on macOS.
- The background service would not properly handle SIGTERM on macOS.
- Local gateway IP would blank out on the diagnostic panel for macOS.
Known Issues
- The connection counters and graph may get stuck until a reboot or background service restart on Windows systems that return from "hibernation" / S4 sleep state and reconnect automatically. Agent connectivity is unaffected by this graphical bug.
- Some WSL2 applications are unable to pass traffic when using the Agent.
- The username may disappear from the bottom of main panel when upgrading versions on macOS. Agent connectivity is unaffected by this graphical bug.