Hi - has anyone successfully deployed the FortiClient with auto-connect enabled, in a Windows Hello environment? We are having issues with the VPN client not auto-connecting at login, and I believe it could be due to how fast Windows logs in using Windows Hello with a camera and no password. Thanks.
Hello,
In a Windows Hello environment, the speed of login can indeed affect the auto-connect feature of FortiClient. Here are some steps to address this issue:
1. plz Verify Auto-Connect Settings- Ensure that the auto-connect feature is properly configured in FortiClient. This includes setting the correct VPN tunnel and ensuring that credentials are stored.
2. then Check Windows Hello Configuration setting.
3. Delay Startup Consider adding a slight delay to the FortiClient startup process.
4. finally Review the Logs Check the FortiClient logs for any errors or messages that might indicate why the auto-connect is failing.
5. Update Software like both Windows and FortiClient are updated to the latest versions.
Thanks. I've done all the steps listed to no avail, with the exception of #3. What's the proper way to delay the startup of the FortiClient?
User | Count |
---|---|
2621 | |
1390 | |
804 | |
666 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.