Document
Library

Administration Guide

Introduction
- FortiClient, FortiClient EMS, and FortiGate
- Fortinet product support for FortiClient
- Feature comparison of FortiClient standalone and licensed versions
- Endpoint communication security improvement
  - Recommended upgrade path
Getting started
- Getting started with FortiClient
- EMS and endpoint profiles
- Telemetry connection options
- EMS and automatic upgrade of FortiClient
Provisioning preparation
- Installation requirements
- Licensing
- Required services and ports
- Firmware images and tools
- Obtaining FortiClient installation files
Provisioning
- Installing FortiClient on computers
- Installing FortiClient on infected systems
- Installing FortiClient as part of cloned disk images
- Installing FortiClient using the CLI
- Deploying FortiClient using Microsoft AD servers
  - Deploying FortiClient with Microsoft AD
  - Uninstalling FortiClient with Microsoft AD
- Uninstalling FortiClient
- Upgrading FortiClient
- Verifying ports and services and connection between EMS and FortiClient
User details
- Viewing user details
- Retrieving user details from cloud applications
- Adding your phone number and email address manually
- Specifying the user avatar manually
- User Profile notification
Zero Trust Telemetry
- FortiClient Telemetry
- Compliance with EMS and FortiOS
- On-/off-fabric status with EMS
  - Logging to FortiAnalyzer
- Quarantined endpoints
Remote Access
- Configuring VPN connections
  - Configuring an SSL VPN connection
  - Configuring an IPsec VPN connection
- Connecting VPNs
- SAML support for SSL VPN
- Advanced features (Windows)
- Advanced features (macOS)
  - Creating redundant IPsec VPNs
  - Creating priority-based SSL VPN connections
- VPN tunnel and script
  - Windows
  - macOS
- Standalone VPN client
ZTNA Connection Rules
Malware Protection
- Antivirus
- Cloud Based Malware Protection
- AntiExploit
  - Viewing detected exploit attempts
  - Evaluating the anti-exploit detection feature
- Removable media access
- Quarantined files
  - Viewing quarantined files
  - Submitting quarantined files for scanning
Sandbox Detection
- Scanning with FortiSandbox on-demand
- Viewing FortiSandbox scan results
- Using the popup window
Web Filter
- Web browser plugin for HTTPS web filtering
- Viewing violations
- Troubleshooting Web Filter
Application Firewall
Vulnerability Scan
- Scanning on-demand
- Automatically fixing detected vulnerabilities
- Reviewing detected vulnerabilities before fixing
- Manually fixing detected vulnerabilities
- Viewing details about vulnerabilities
- Viewing vulnerability scan history
Notifications
Settings
- System
- Logging
  - Sending logs and Windows host events to FortiAnalyzer or FortiManager
  - Exporting the log file
- VPN options
- Advanced options
- FortiTray
Diagnostic Tool
Appendix A - FortiClient API
- Overview
- API reference
Appendix B - FortiClient log messages
Appendix C - Vulnerability patches
Appendix D - FortiClient processes
- FortiClient (Windows) processes
- FortiClient (macOS) processes
Appendix E - FortiClient (Linux) CLI commands
Appendix F - VPN autoconnect
- Configuring autoconnect with username and password authentication
- Configuring autoconnect with certificate authentication

Home FortiClient 7.0.2 Administration Guide

Upgrading FortiClient

7.0.2

Copy Link

Copy Doc ID 4ccf1d68-31c2-11ec-9c99-00505692583a:991309

Download PDF

Upgrading FortiClient

For information about supported upgrade paths for FortiClient, see the FortiClient and FortiClient EMS Upgrade Paths.

An administrator controls FortiClient upgrades for you. See EMS and automatic upgrade of FortiClient.

When an administrator deploys a FortiClient upgrade from EMS to endpoints running a Windows operating system, an Upgrade Schedule dialog displays in advance on the endpoint to let users schedule the upgrade and mandatory endpoint reboot. If FortiClient is not installed on the endpoint, the installation does not require a reboot, and the Upgrade Schedule dialog does not display. The user can postpone the reboot for a maximum of 24 hours. Before the mandatory reboot occurs, a FortiClient dialog displays a 15 minute warning.

Previous

Next

Upgrading FortiClient

For information about supported upgrade paths for FortiClient, see the FortiClient and FortiClient EMS Upgrade Paths.

An administrator controls FortiClient upgrades for you. See EMS and automatic upgrade of FortiClient.

When an administrator deploys a FortiClient upgrade from EMS to endpoints running a Windows operating system, an Upgrade Schedule dialog displays in advance on the endpoint to let users schedule the upgrade and mandatory endpoint reboot. If FortiClient is not installed on the endpoint, the installation does not require a reboot, and the Upgrade Schedule dialog does not display. The user can postpone the reboot for a maximum of 24 hours. Before the mandatory reboot occurs, a FortiClient dialog displays a 15 minute warning.

Previous

Next