Install forticlient

FortiClient always installs the Fortinet Security Fabric Agent (SFA) feature and enables the Vulnerability Scan feature by default. You can select to install one or more of the following options: Secure Remote Access: VPN components (IPsec and SSL) will be installed. Advanced Persistent Threat (APT) Components: FortiSandbox detection and quarantine features will be installed. Additional Security Features: Select one or more of the following to install them: AntiVirus, Web Filtering, Single Sign On, Application Firewall It is recommended to not install VPN components on Windows Server systems if not required. Upgrading from previous FortiClient versions FortiClient version 6.0.7 supports upgrade from FortiClient versions 5.4 and later. If you are deploying an upgrade from FortiClient 5.6.2 or earlier versions via FortiClient EMS and the upgrade fails, uninstall FortiClient on the endpoints, then deploy the latest version of FortiClient. Downgrading to previous versions Downgrading FortiClient version 6.0.7 to previous FortiClient versions is not supported. Firmware image checksums The MD5 checksums for all Fortinet software and firmware releases are available at the Customer Service & Support portal. After logging in, click on Download > Firmware Image Checksums, enter the image file name, including the extension, and select Get Checksum Code.

Installing FortiClient using the CLI You can install FortiClient using the CLI. When an EMS administrator creates a FortiClient installer as Adding a FortiClient deployment package describes, EMS creates .exe and .msi installers. You can use either to install FortiClient: Installer file Description .exe Includes custom modifications as configured when creating the deployment package. You can double-click the file to run the installer, or install FortiClient in the CLI. .msi You must use the .msi installer in combination with the .mst file., as the .msi file does not include any custom modifications configured when creating the deployment package. If using the .msi file, you must install FortiClient using the CLI so that you can provide the accompanying .mst file. Otherwise, the custom modifications are unavailable to FortiClient after installation. The following table summarizes the installation options available when using the CLI. All of the following options are available if you use the .exe file. If you use the .msi file with the .mst file, not all of the following options are available, as you are constrained by the CLI options that Windows Installer permits. See Command-Line Options. Option Description /quiet Installation is in quiet mode and requires no user interaction. /passive Installation is in unattended mode, showing only the progress bar. /norestart Does not restart the machine after installation is complete. /promptrestart Prompts you to restart the machine if necessary. /forcerestart Always restarts the machine after installation. /uninstallfamily Uninstalls FortiClient. With this option, the FortiClient installer detects whatever version of

Minimum system requirements 2.0 GHz 64-bit processor, six virtual CPUs 8 GB RAM (10 GB RAM or more is recommended) 40 GB free hard disk Gigabit (10/100/1000baseT) Ethernet adapter Internet access is recommended, but optional, during installation. SQL Server may require some dependencies to be downloaded over the internet. EMS also tries to download information about FortiClient signature updates from FortiGuard. You should only install FortiClient EMS and the default services for the operating system on the server. You should not install additional services on the same server as FortiClient EMS. FortiAnalyzer 7.4.0 and later 7.2.0 and later 7.0.0 and later Although EMS supports the listed FortiAnalyzer versions, confirming the compatibility between your FortiAnalyzer and FortiClient versions is recommended. Otherwise, not all features may be available. See the FortiClient Release Notes. FortiAuthenticator 6.6.0 and later 6.5.0 and later 6.4.0 and later 6.3.0 and later 6.2.0 and later 6.1.0 and later 6.0.0 and later FortiClient (Linux) 7.2.0 and later 7.0.2 and later FortiClient (macOS) 7.2.0 and later 7.0.2 and later FortiClient (Windows) 7.2.0 and later 7.0.2 and later FortiManager 7.4.0 and later 7.2.0 and later 7.0.0 and later FortiOS 7.4.0 and later 7.2.0 and later 7.0.0 and later (for zero trust network access, 7.0.6 or later is recommended) 6.4.0 and later FortiSandbox 4.4.0 and later 4.2.0 and later 4.0.0 and later 3.2.0 and later