We've been piloting Cloudflare One for a secure access service edge (SASE) deployment, with a focus on cost consolidation versus traditional cloud vendor networking stacks. The technical promise is solid, but the WARP client's stability on Windows 11 is becoming a blocker.
The client disconnects multiple times per day for users, dropping them from Zero Trust policies and requiring a manual reconnection. The standard diagnostics are unhelpful. The Windows Event Viewer logs under `Applications and Services Logs -> Cloudflare` show generic `info` or `warning` levels, like "Service state changed," but no actionable error codes or triggers. The `warp-cli` diagnostics output shows all checks passing post-reconnection.
We've attempted the following without resolving the issue:
* Deployed the latest stable WARP client version (`2024.5.40.0`) via our MDM.
* Verified network drivers, particularly on Dell and Surface hardware, are updated.
* Tested with both the `Cloudflare WARP` client and the `Cloudflare Zero Trust` client.
* Added firewall allowances for `C:Program FilesCloudflareCloudflare WARPwarp-svc.exe` and the GUI client.
Our current workaround is a scheduled task to restart the WARP service, which is not sustainable.
Has anyone performing a similar migration encountered this? Specifically:
1. Are there known conflicts with Windows 11's built-in VPN/Wi-Fi sense or other security software (we're using Defender for Endpoint)?
2. Beyond the standard logs, is there a verbose debug mode for the WARP service that captures more granular connection state or error messages?
3. Could this be related to specific IPv6 or MDM device compliance check interactions?
Any insight into persistent disconnections, particularly from an enterprise deployment perspective, would be valuable. We need to quantify stability to validate the cost-benefit analysis of this SASE model.
Less spend, more headroom.