Forticlient 7.0.14 Windows Release Notes
Forticlient 7.0.14 Windows Release Notes
FORTINET BLOG
https://blog.fortinet.com
FORTIGUARD LABS
https://www.fortiguard.com
FEEDBACK
Email: [email protected]
Change log 4
Introduction 5
Licensing 5
Special notices 6
Nested VPN tunnels 6
Installation information 7
Firmware images and tools 7
Upgrading from previous FortiClient versions 8
Downgrading to previous versions 9
Firmware image checksums 9
Product integration and support 10
Language support 11
Conflicts with third party AV products 12
Intune product codes 12
Resolved issues 13
Install and upgrade 13
Remote Access 13
Remote Access - SSL VPN 13
Known issues 15
New known issues 15
Existing known issues 15
Configuration 15
Remote Access 15
Remote Access - IPsec VPN 16
Remote Access - SSL VPN 16
ZTNA connection rules 16
This document provides a summary of enhancements, support information, and installation instructions for FortiClient
(Windows) 7.0.14 build 0585.
l Special notices on page 6
l Installation information on page 7
l Product integration and support on page 10
l Resolved issues on page 13
l Existing known issues on page 15
Review all sections prior to installing FortiClient.
FortiClient (Windows) 7.0.14 components that interact with Microsoft Security Center are signed with an Azure Code
Signing certificate, which fulfills Microsoft requirements.
Licensing
FortiClient (Windows) does not support parallel independent VPN connections to different sites. However, FortiClient
(Windows) may still establish VPN connection over existing third-party (for example, AT&T Client) VPN connection
(nested tunnels).
The following files are available in the firmware image file folder:
File Description
FortiClientVPNSetup_7.0.14.0585.exe
Free VPN-only installer (32-bit)
FortiClientVPNSetup_7.0.14.0585.zip
FortiClientVPNSetup_7.0.14.0585_x64.exe
Free VPN-only installer (64-bit)
FortiClientVPNSetup_7.0.14.0585_x64.zip
File Description
EMS 7.0.14 includes the FortiClient (Windows) 7.0.14 standard installer and zip package containing FortiClient.msi and
language transforms.
The following tools and files are available in the FortiClientTools_7.0.14.0585.zip file:
File Description
OnlineInstaller Installer files that install the latest FortiClient (Windows) version available.
File Description
Review the following sections prior to installing FortiClient version 7.0.14: Introduction on page
5 and Product integration and support on page 10.
l Deploy FortiClient 7.0.14 as an upgrade from EMS. With the endpoint security improvement feature, there are
backward compatibility issues to consider while planning upgrades. See Recommended upgrade path.
l Manually uninstall existing FortiClient version from the device, then install FortiClient (Windows) 7.0.14.
FortiClient (Windows) 7.0.14 features are only enabled when connected to EMS 7.0 or 7.2.
See the FortiClient and FortiClient EMS Upgrade Paths for information on upgrade paths.
You must be running EMS 7.0.2 or later before upgrading FortiClient.
FortiClient (Windows) 7.0.14 does not support downgrading to previous FortiClient (Windows) versions.
The MD5 checksums for all Fortinet software and firmware releases are available at the Customer Service & Support
portal. After logging in, click Download > Firmware Image Checksum, enter the image file name, including the extension,
and select Get Checksum Code.
The following table lists version 7.0.14 product integration and support information:
The following FortiOS versions support IPsec and SSL VPN with FortiClient
(Windows) 7.0.14:
l 7.4.0 and later
Language support
The FortiClient language setting defaults to the regional language setting configured on the client workstation, unless
configured in the XML configuration file.
If the client workstation is configured to a regional language setting that FortiClient does not support,
it defaults to English.
The AV feature in FortiClient is known to conflict with other similar products in the market.
l Do not use FortiClient's AV feature with other AV products.
l If not using FortiClient's AV feature, exclude the FortiClient installation folder from scanning for the third party
AV product.
During a new FortiClient installation, the installer searches for other registered third party software and, if it finds any,
warns users to uninstall them before proceeding with the installation. There is also an option to disable FortiClient real
time protection.
Deploying FortiClient with Intune requires a product code. The product codes for FortiClient 7.0.14 are as follows:
Enterprise 707CAECE-5226-4BC8-AE2A-D9139C0C348C
The following issues have been fixed in version 7.0.14. For inquiries about a particular bug, contact Customer Service &
Support.
Bug ID Description
1057335 FortiAuthenticator Windows agent does not work after FortiClient upgrade.
Remote Access
Bug ID Description
711402 FortiClient (Windows) fails to establish per-user autoconnect VPN tunnel and per-machine
autoconnect tunnel remains connected after Windows logon.
930172 With priority=0 + machine autoconnect enabled, per-user autoconnect tunnel fails to connect after
Windows logon.
1052284 Per-machine prelogon tunnel does not work by per-user autoconnect configuration.
1066263 Free VPN-only client console does not minimize after it establishes tunnel with <minimize_
window_on_connect> enabled.
1092542 After upgrading FortiClient, FortiClient (Windows) quickly and automatically removes VPN
credentials, making VPN connection difficult.
Bug ID Description
920383 FortiClient enables Turn off smart multi-homed name resolution on Windows machine after
successful connection.
922941 Connecting to SSL VPN with FQDN resolved to both IPv4 and IPv6 as remote gateway gets stuck
at 98%.
Bug ID Description
1052659 FortiClient (Windows) gets stuck at 98% and cannot reconnect when endpoint is left in standby or
sleep for a couple of hours until reboot.
The following issues have been identified in a previous version of FortiClient (Windows) and remain in FortiClient
(Windows)7.0.14.
Configuration
Bug ID Description
1016803 After installation, the Remote Access tab is hidden even if a Remote Access profile is embedded in
the installer.
Remote Access
Bug ID Description
996877 Manage Engine ADSelfService-installed endpoint causes issue on other user screen when VPN
before logon is enabled.
Bug ID Description
758424 Certificate works for IPsec VPN tunnel if put it in current user store but fails to work if in local
machine.
Bug ID Description
909244 Split DNS name resolution stops working after VPN is up for a few minutes in some environments
until running ipconfig /flushdns.
914018 SSL VPN SAML login fails to work if using YubiKey for MFA.
947381 With <prefer_sslvpn_dns> disabled, when SSL VPN is up, FortiClient (Windows) adds
DNS suffix to all network interfaces.
950787 Domain filter cannot block access for specific server FQDN.
993876 FortiClient (Windows) provides inaccurate error in German when SSL VPN password is incorrect.
Bug ID Description
839589 ZTNA TCP forwarding does not work for GoAnywhere application.
1001116 FortiClient requests SAML credentials after network change in ZTNA connections.
Copyright© 2024 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., and other Fortinet names herein
may also be registered and/or common law trademarks of Fortinet. All other product or company names may be trademarks of their respective owners. Performance and other metrics contained herein were
attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance
results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract,
signed by Fortinet’s Chief Legal Officer, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such event, only
the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be limited to performance in the same ideal
conditions as in Fortinet’s internal lab tests. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change,
modify, transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.