DOCUMENT LIBRARY

EMS Administration Guide

Introduction
- FortiClient EMS components
- Documentation
Getting started
- Getting started with managing Windows, macOS, and Linux endpoints
- Getting started with managing Chromebooks
Installation preparation
- System requirements
- License types
  - FortiClient EMS
  - Component applications
- Required services and ports
- Management capacity
- FortiClient Telemetry security features
- Server readiness checklist for installation
- Upgrading from an earlier FortiClient EMS version
- Install preparation for managing Chromebooks
Installation and licensing
- Downloading the installation file
- Installing FortiClient EMS
- Installing FortiClient EMS using the CLI
- Starting FortiClient EMS and logging in
- Accessing FortiClient EMS remotely
- Licensing FortiClient EMS
  - License status
  - Help with licensing
- Specifying different ports
- Upgrading Microsoft SQL Server Express to Microsoft SQL Server Standard or Enterprise
- Uninstalling FortiClient EMS
Chromebook-only setup
- Google Admin Console setup
- Service account credentials
  - Configuring default service account credentials
  - Configuring unique service account credentials
GUI
- Banner
- Left pane
- Content pane
Dashboard
- Viewing the FortiClient Status
- Viewing the Vulnerability Scan dashboard
- Viewing Chromebook Status
Endpoint management
- Windows, macOS, and Linux endpoints
- Google Domains
- Group assignment rules
Quarantine Management
- Files
  - Viewing quarantined files
  - Allowlisting quarantined files
- Whitelist
Software Inventory
- Applications
- Hosts
Endpoint Policy
- Adding an endpoint policy
- Editing an endpoint policy
- Deleting an endpoint policy
- Enabling/disabling an endpoint policy
Chromebook Policy
Endpoint Profiles
- Configuring profiles
- Viewing profiles
- Managing profiles
- Profile references
Managing installers
- Deployment Packages
- FortiClient installers
  - Adding a custom FortiClient installer
  - Viewing installers
Profile Components
Telemetry Gateway Lists
- Creating a Telemetry gateway list
- Exporting a Telemetry gateway list to XML
- Viewing Telemetry gateway lists
- Viewing assigned Telemetry gateway lists
Compliance Verification
- Compliance Verification Rules
- Host Tag Monitor
- Configuring FortiOS dynamic policies using EMS dynamic endpoint groups
- Fabric Device Monitor
Deployment
- Preparing the AD server for deployment
- Preparing Windows endpoints for FortiClient deployment
- Deploying FortiClient on endpoints
- Deploying initial installations of FortiClient (macOS)
- Deploying FortiClient upgrades from FortiClient EMS
Administration
- Administrators
- Admin roles
- User Servers
- Configuring User Settings
- Database management
  - Backing up the database
  - Restoring the database
- Licenses
  - Logging into FortiCare
  - Uploading a license file for activation, upgrade, or renewal
- Logs
System Settings
- Configuring Server settings
- Adding an SSL certificate to FortiClient EMS for Chromebook endpoints
- Configuring Logs settings
- Configuring FortiGuard settings
- Configuring Endpoints settings
- Configuring the login banner
- Alerts
- Custom Messages
  - Customizing the endpoint quarantine message
  - Customizing Web Filter messages
Creating a support package

Home FortiClient 6.2.1 EMS Administration Guide

6.2.1

System requirements

The minimum system requirements for FortiClient EMS are as follows.

Microsoft Windows Server 2012 R2 or newer
No additional installed services
2.0 GHz 64-bit processor, dual core (or two virtual CPUs)
4 GB RAM (8 GB RAM or more is recommended)
40 GB free hard disk
Gigabit (10/100/1000baseT) Ethernet adapter
Internet access

Internet access is required during installation. This becomes optional once installation is complete. FortiClient EMS accesses the Internet to obtain information about FortiGuard engine and signature updates.

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.