connections for remote users. This version introduces native support for Windows ARM64
Ensure the client machine can reach the firewall's WAN IP on the configured user portal port. Tap Driver Error during installation Conflict with third-party VPN virtual adapters.
: Distributed as an .msi file, making it compatible with automated deployment tools. sophosconnect 2.5.0 ga%28ipsec and sslvpn%29.msi
The client handles both IPsec and SSL VPN connections inside a single user interface. Users do not need separate software packages for different network architectures. 2. Enhanced Authentication Options
Because the installer is packaged as a Microsoft Installer ( .msi ), system administrators can deploy it silently across hundreds of endpoints using Microsoft Endpoint Configuration Manager (SCCM), Microsoft Intune, or Group Policy Objects (GPO). Standard Silent Installation connections for remote users
The Sophos Connect window now reliably displays in the lower right corner of the screen, providing a consistent user experience. Why Use the .MSI File?
– This version may have known vulnerabilities (e.g., outdated OpenVPN or IPsec components). Do not use it for new deployments. : Distributed as an
Uninstall old Sophos SSL VPN clients before running the .msi . Provisioning file ( .pro ) fails to sync Port 443 or user portal port is blocked.
The client automatically imports this file, setting up the connection details, user settings, and certificates, allowing the user to simply click "Connect." Manual Configuration Open the Sophos Connect client.
Browse to and select your assigned .scx , .ovpn , or .pro file. Click and enter your corporate domain credentials. Troubleshooting Common Errors Error: "Failed to establish connection"
: Admins can deploy a universal configuration file ( .pro ), which allows the client to automatically fetch the specific VPN configuration for each user.