Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • EMS Administration Guide

    Home FortiClient 7.2.0 EMS Administration Guide
    7.2.0
    7.4.1
    7.4.0
    7.2.5
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.0.13
    7.0.12
    7.0.11
    7.0.10
    7.0.9
    7.0.8
    7.0.7
    7.0.6
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.9
    6.4.8
    6.4.7
    6.4.4
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.2.9
    6.2.8
    6.2.7
    6.2.6
    6.2.4
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.0.8
    6.0.6
    6.0.5
    6.0.4
    6.0.3
    6.0.2
    6.0.1
    6.0.0

    Initially deploying FortiClient software to endpoints

    Initially deploying FortiClient software to endpoints

    Following is an overview of how to initially deploy FortiClient to endpoints and connect them to EMS. You can use one of the following methods:

    Deployment method

    Description

    Microsoft System Center Configuration Manager (SCCM) or group policy object (GPO)
    1. Create a custom deployment package (MSI file) on EMS. See Adding a FortiClient deployment package.
    2. Deploy the FortiClient deployment package to desired endpoints using one of the following:
      1. SCCM: Deploy applications with Configuration Manager.
      2. GPO: Use Group Policy to remotely install software.

    Mobile device management (MDM)

    Use an MDM application to initially deploy FortiClient to the desired endpoints. FortiClient supports the following MDM applications. See the guide for each MDM application:

    Sending installer link to end users
    1. Create a custom deployment package on EMS. See Adding a FortiClient deployment package.
    2. Create an invitation on EMS, configuring the invitation to be sent to all desired end users. See Invitations.
    3. The end user receives an email or SMS notification that includes the configured invitation code and installer. They install FortiClient on their devices using the included installer and enter the invitation code to connect their FortiClient to EMS.
    Note

    After FortiClient and EMS establish a Telemetry connection, you can push FortiClient updates to endpoints using EMS. The aforementioned methods are only required for initial FortiClient deployment to endpoints. See Deployment & Installers.
    Note

    In 7.2.0, you cannot deploy initial FortiClient installations to Active Directory domain-joined devices. You must use one of the aforementioned methods to deploy initial FortiClient installations.
    Previous
    Next

    Initially deploying FortiClient software to endpoints

    Initially deploying FortiClient software to endpoints

    Following is an overview of how to initially deploy FortiClient to endpoints and connect them to EMS. You can use one of the following methods:

    Deployment method

    Description

    Microsoft System Center Configuration Manager (SCCM) or group policy object (GPO)
    1. Create a custom deployment package (MSI file) on EMS. See Adding a FortiClient deployment package.
    2. Deploy the FortiClient deployment package to desired endpoints using one of the following:
      1. SCCM: Deploy applications with Configuration Manager.
      2. GPO: Use Group Policy to remotely install software.

    Mobile device management (MDM)

    Use an MDM application to initially deploy FortiClient to the desired endpoints. FortiClient supports the following MDM applications. See the guide for each MDM application:

    Sending installer link to end users
    1. Create a custom deployment package on EMS. See Adding a FortiClient deployment package.
    2. Create an invitation on EMS, configuring the invitation to be sent to all desired end users. See Invitations.
    3. The end user receives an email or SMS notification that includes the configured invitation code and installer. They install FortiClient on their devices using the included installer and enter the invitation code to connect their FortiClient to EMS.
    Note

    After FortiClient and EMS establish a Telemetry connection, you can push FortiClient updates to endpoints using EMS. The aforementioned methods are only required for initial FortiClient deployment to endpoints. See Deployment & Installers.
    Note

    In 7.2.0, you cannot deploy initial FortiClient installations to Active Directory domain-joined devices. You must use one of the aforementioned methods to deploy initial FortiClient installations.
    Previous
    Next