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.2.1 EMS Administration Guide
    6.2.1
    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

    Installing FortiClient EMS using the CLI

    Installing FortiClient EMS using the CLI

    Installing FortiClient EMS using the CLI allows you to enable certain options during installation, such as customizing the EMS installation directory, using custom port numbers, and so on.

    The following table provides a description of all options available when installing FortiClient EMS using the CLI. These options are case-sensitive:

    Option

    Description

    AllowedWebHostnames

    The default value is localhost, 127.0.0.1. To clear this value, first enter AllowedWebHostnames=*, then enter the desired AllowedWebHostnames value. Otherwise, the value entered will be appended to [localhost, 127.0.0.1], so that AllowedWebHostNames=localhost, 127.0.01, <new_value>.

    ApacheServerAdminEmail

    Enter the Apache Server administrator's email address. By default, this is admin@yourcompany.com.

    BackupDir

    Enter the desired backup directory path for SQL Server.

    ClientDownloadPort

    Enter the HTTP port number. The default is 80.

    RemoteManagementPort

    Enter the HTTPS port number. The default is 443.

    InstallFolder

    Specify the directory to install EMS to.

    InstallSQL

    Controls whether the installer will install SQL Server Express on the same server as FortiClient EMS. Enter 1 to install SQL Server Express; otherwise, enter 0. By default, SQL Server Express is installed with FortiClient EMS.

    ScriptDB

    Controls where the installer will attempt to create the database from db scripts. Enter 1 to create the database from db scripts. 0 should only be entered if databases have already been set up on the server and you are only installing EMS components locally.

    ServerHostname

    Enter the preferred hostname (the remote hostname). The default is the local host.

    SQLAuthType

    Enter sql.

    SQLCmdlineOptions="/INSTANCEDIR"

    Enter the desired directory to install SQL Server Express to.

    SQLCmdlineOptions="/INSTANCENAME"

    Enter the SQL Server instance name.

    SQLEncryptConnection

    (Optional) Enter yes to encrypt the connection to SQL Server. Otherwise, enter no. The default is yes.

    SQLPort

    Enter the port number the remote SQL Server instance is listening on. You should configure SQL Server to use a static port number.

    SQLServer

    Enter the DSN name of the computer where SQL Server is already installed.

    SQLServerInstance

    Enter the SQL Server instance name.

    SQLService

    If using a default database instance, enter the instance name. If using a named database instance, enter mssql$<instance_name>. For example, if your instance is named "database000", enter mssql$database000.

    SQLTrustServerCertificate

    (Optional) Enter yes to trust the SQL Server certificate on the machine where FortiClient EMS is installed. If entering no, you must install the issuing CA certificate of SQL Server's certificate onto the machine you are connecting FortiClient EMS from.

    SQLUser

    Enter the SQL username used to connect to the database instance. This must be pre-configured in SQL Server as described in .

    SQLUserPassword

    Enter the SQL password used to connect to the database instance.

    WindowsUser

    Enter the Windows username used to connect to the database instance. This must be pre-configured in SQL Server as described in .

    WindowsUserPassword

    Enter the Windows password used to connect to the database instance.

    The following topics describe how to use the options above for specific use cases.

    Previous
    Next

    Installing FortiClient EMS using the CLI

    Installing FortiClient EMS using the CLI

    Installing FortiClient EMS using the CLI allows you to enable certain options during installation, such as customizing the EMS installation directory, using custom port numbers, and so on.

    The following table provides a description of all options available when installing FortiClient EMS using the CLI. These options are case-sensitive:

    Option

    Description

    AllowedWebHostnames

    The default value is localhost, 127.0.0.1. To clear this value, first enter AllowedWebHostnames=*, then enter the desired AllowedWebHostnames value. Otherwise, the value entered will be appended to [localhost, 127.0.0.1], so that AllowedWebHostNames=localhost, 127.0.01, <new_value>.

    ApacheServerAdminEmail

    Enter the Apache Server administrator's email address. By default, this is admin@yourcompany.com.

    BackupDir

    Enter the desired backup directory path for SQL Server.

    ClientDownloadPort

    Enter the HTTP port number. The default is 80.

    RemoteManagementPort

    Enter the HTTPS port number. The default is 443.

    InstallFolder

    Specify the directory to install EMS to.

    InstallSQL

    Controls whether the installer will install SQL Server Express on the same server as FortiClient EMS. Enter 1 to install SQL Server Express; otherwise, enter 0. By default, SQL Server Express is installed with FortiClient EMS.

    ScriptDB

    Controls where the installer will attempt to create the database from db scripts. Enter 1 to create the database from db scripts. 0 should only be entered if databases have already been set up on the server and you are only installing EMS components locally.

    ServerHostname

    Enter the preferred hostname (the remote hostname). The default is the local host.

    SQLAuthType

    Enter sql.

    SQLCmdlineOptions="/INSTANCEDIR"

    Enter the desired directory to install SQL Server Express to.

    SQLCmdlineOptions="/INSTANCENAME"

    Enter the SQL Server instance name.

    SQLEncryptConnection

    (Optional) Enter yes to encrypt the connection to SQL Server. Otherwise, enter no. The default is yes.

    SQLPort

    Enter the port number the remote SQL Server instance is listening on. You should configure SQL Server to use a static port number.

    SQLServer

    Enter the DSN name of the computer where SQL Server is already installed.

    SQLServerInstance

    Enter the SQL Server instance name.

    SQLService

    If using a default database instance, enter the instance name. If using a named database instance, enter mssql$<instance_name>. For example, if your instance is named "database000", enter mssql$database000.

    SQLTrustServerCertificate

    (Optional) Enter yes to trust the SQL Server certificate on the machine where FortiClient EMS is installed. If entering no, you must install the issuing CA certificate of SQL Server's certificate onto the machine you are connecting FortiClient EMS from.

    SQLUser

    Enter the SQL username used to connect to the database instance. This must be pre-configured in SQL Server as described in .

    SQLUserPassword

    Enter the SQL password used to connect to the database instance.

    WindowsUser

    Enter the Windows username used to connect to the database instance. This must be pre-configured in SQL Server as described in .

    WindowsUserPassword

    Enter the Windows password used to connect to the database instance.

    The following topics describe how to use the options above for specific use cases.

    Previous
    Next