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 6.0.8 EMS Administration Guide
    6.0.8
    7.4.1
    7.4.0
    7.2.6
    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

    Standalone FortiClient EMS

    Standalone FortiClient EMS

    The diagram shows the topology when using FortiClient EMS in standalone mode.

    In this scenario, FortiClient EMS provides FortiClient endpoint provisioning. FortiClient endpoints connect Telemetry to FortiClient EMS to receive configuration information from FortiClient EMS. This scenario does not support compliance.

    When viewing the endpoint in the FortiClient EMS GUI, the endpoint's connection is shown as Managed by EMS.

    The below shows the FortiClient GUI when FortiClient is connected to FortiClient EMS but not FortiGate. FortiClient Console indicates that FortiClient is not participating in compliance enforcement because it is not connected to a FortiGate. You can also view the IP address, hostname, and serial number of the EMS to which Telemetry is connected. This means FortiClient EMS can push profiles to FortiClient. FortiClient EMS is providing endpoint provisioning to FortiClient.

    Previous
    Next

    Standalone FortiClient EMS

    Standalone FortiClient EMS

    The diagram shows the topology when using FortiClient EMS in standalone mode.

    In this scenario, FortiClient EMS provides FortiClient endpoint provisioning. FortiClient endpoints connect Telemetry to FortiClient EMS to receive configuration information from FortiClient EMS. This scenario does not support compliance.

    When viewing the endpoint in the FortiClient EMS GUI, the endpoint's connection is shown as Managed by EMS.

    The below shows the FortiClient GUI when FortiClient is connected to FortiClient EMS but not FortiGate. FortiClient Console indicates that FortiClient is not participating in compliance enforcement because it is not connected to a FortiGate. You can also view the IP address, hostname, and serial number of the EMS to which Telemetry is connected. This means FortiClient EMS can push profiles to FortiClient. FortiClient EMS is providing endpoint provisioning to FortiClient.

    Previous
    Next