new
improved
fixed
Windows Roaming Client
RC Release Channels
Beta
11/13 November 13 - Windows Roaming Client v3.0.0 Beta
The latest
Windows Roaming Client (v3.0.0)
is now available in the Beta Channel
and can be downloaded from Deployments → Roaming Clients → Install Roaming Client
in your dashboard. ✨ What’s New
🧱
Modernized Architecture
Implemented a modern architecture that improved reliability, performance, and long-term maintainability.
- Upgraded to .NET Core, aligning with modern Windows frameworks and improving compatibility with future releases.
- Refactored core services for more consistent performance and cleaner communication between components.
- Streamlined update handling and service behavior for smoother operation in complex environments.
- Establishes a stronger, more maintainable base for future feature development and cross-platform consistency.
🧩
Configuration & Management Improvements
Introduced a unified configuration structure that simplified management, customization, and troubleshooting across deployments.
- Centralized configuration, logging, and overrides to make setup and maintenance more consistent.
- Adopted a modern configuration model. Registry support temporarily continues, but all custom settings should now be applied through theappsettings.overrides.jsonfile. This update also enables distinction between server-managed and local device configurations.
- Standardized validation and logging to ensure settings apply correctly during upgrades and improve diagnostic clarity.
- Established a foundation for future dashboard-based configuration visibility and remote management.
🪲 Bug Fixes
- Improved VPN Compatibility Recognition– Fixed an issue where the client ignored the dashboard’s VPN Compatibility setting until the service restarted, causing inconsistent behavior in 2.x deployments.
- Enhanced Recovery Handling– Addressed a condition where the client failed to recover automatically after a “pipe not connected” error, requiring a manual restart.
- Corrected Logging Behavior– Resolved inconsistent log rotation and retention that could lead to excessive file sizes or missing entries.
- Stabilized IPv6 Operation– Fixed a failure mode in IPv6-only environments where the client incorrectly closed filtering if no IPv6 DNS was advertised.
- Improved Configuration Reliability– Fixed scenarios where client overrides (such as VPN or registry-based settings) were not applied during startup or reinstallation.