Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

EMS Administration Guide

Installing FortiClient EMS to specify SQL Server Enterprise or Standard instance

If you are using SQL Server Enterprise or Standard with FortiClient EMS, you must install FortiClient EMS using the CLI to specify the correct SQL Server instance. Ensure you have already installed and configured SQL Server Enterprise or Standard.

Local existing database

This section lists the CLI commands for when FortiClient EMS and SQL Server Enterprise or Standard are installed on the same machine.

Database type

Command

Local default instance using SQL authentication

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLUser=<username> SQLUserPassword=<password> InstallSQL=0 ScriptDB=1 SQLServerInstance= SQLService=<instance_name> SQLCmdlineOptions="/INSTANCENAME="

Local default instance using local Windows authentication

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLServerInstance= SQLService=<instance_name> SQLCmdlineOptions="/INSTANCENAME=" InstallSQL=0 ScriptDB=1

Local named instance using SQL authentication

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLUser=<username> SQLUserPassword=<password> InstallSQL=0 ScriptDB=1 SQLServerInstance=<instance_name> SQLService=mssql$<instance_name> SQLCmdlineOptions="/INSTANCENAME=<instance_name>"

Local named instance using local Windows authentication

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLServerInstance=<instance_name> SQLService=mssql$<instance_name> SQLCmdlineOptions="/INSTANCENAME=<instance_name>" InstallSQL=0 ScriptDB=1

For example, if installing FortiClient EMS and pointing to a local instance named "database000" using SQL authentication, with SQL username "janedoe", password "password123", the command would be as follows:

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLUser=janedoe SQLUserPassword=password123 InstallSQL=0 ScriptDB=1 SQLServerInstance=database000 SQLService=mssql$database000 SQLCmdlineOptions="/INSTANCENAME=database000"

Remote existing database

To create a backup directory:

Prior to installing FortiClient EMS, create a backup directory on the database server and set the permissions as described:

  1. On the database server, create a backup directory.
  2. Right-click the directory and select Properties.
  3. On the Security tab, ensure all users have full control of the directory.

Installation commands for remote existing databases

For remote instances using Windows authentication (domain user), do the following:

  1. Join the EMS and database servers to the same domain.
  2. Create a database user that maps to the domain user.
  3. In Local Group Policy Editor, add the domain user to the Log on as a service policy.

Database type

Command

Remote default or named instance using SQL authentication

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLServer=<SQL_Server_name> SQLUser=<username> SQLUserPassword=<password> InstallSQL=0 ScriptDB=1 BackupDir=<backupdirectorypath>

Remote default or named instance using Windows authentication (domain user)

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLServer=<SQL_Server_name> WindowsUser=<username@domain.loc> WindowsUserPassword=<password> InstallSQL=0 ScriptDB=1 BackupDir=<backupdirectorypath>

For example, if installing FortiClient EMS and pointing to a remote named instance on a computer with DNS name WIN-088 using Windows authentication, with Windows username "janedoe", password "password123", the command would be as follows. This example also includes the optional SQLEncryptConnection option:

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLServer=WIN-0888 WindowsUser=janedoe@ems.loc WindowsUserPassword=password123 InstallSQL=0 ScriptDB=1 BackupDir=c:\backup\ SQLEncryptConnection=no

Installing FortiClient EMS to specify SQL Server Enterprise or Standard instance

If you are using SQL Server Enterprise or Standard with FortiClient EMS, you must install FortiClient EMS using the CLI to specify the correct SQL Server instance. Ensure you have already installed and configured SQL Server Enterprise or Standard.

Local existing database

This section lists the CLI commands for when FortiClient EMS and SQL Server Enterprise or Standard are installed on the same machine.

Database type

Command

Local default instance using SQL authentication

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLUser=<username> SQLUserPassword=<password> InstallSQL=0 ScriptDB=1 SQLServerInstance= SQLService=<instance_name> SQLCmdlineOptions="/INSTANCENAME="

Local default instance using local Windows authentication

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLServerInstance= SQLService=<instance_name> SQLCmdlineOptions="/INSTANCENAME=" InstallSQL=0 ScriptDB=1

Local named instance using SQL authentication

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLUser=<username> SQLUserPassword=<password> InstallSQL=0 ScriptDB=1 SQLServerInstance=<instance_name> SQLService=mssql$<instance_name> SQLCmdlineOptions="/INSTANCENAME=<instance_name>"

Local named instance using local Windows authentication

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLServerInstance=<instance_name> SQLService=mssql$<instance_name> SQLCmdlineOptions="/INSTANCENAME=<instance_name>" InstallSQL=0 ScriptDB=1

For example, if installing FortiClient EMS and pointing to a local instance named "database000" using SQL authentication, with SQL username "janedoe", password "password123", the command would be as follows:

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLUser=janedoe SQLUserPassword=password123 InstallSQL=0 ScriptDB=1 SQLServerInstance=database000 SQLService=mssql$database000 SQLCmdlineOptions="/INSTANCENAME=database000"

Remote existing database

To create a backup directory:

Prior to installing FortiClient EMS, create a backup directory on the database server and set the permissions as described:

  1. On the database server, create a backup directory.
  2. Right-click the directory and select Properties.
  3. On the Security tab, ensure all users have full control of the directory.

Installation commands for remote existing databases

For remote instances using Windows authentication (domain user), do the following:

  1. Join the EMS and database servers to the same domain.
  2. Create a database user that maps to the domain user.
  3. In Local Group Policy Editor, add the domain user to the Log on as a service policy.

Database type

Command

Remote default or named instance using SQL authentication

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLServer=<SQL_Server_name> SQLUser=<username> SQLUserPassword=<password> InstallSQL=0 ScriptDB=1 BackupDir=<backupdirectorypath>

Remote default or named instance using Windows authentication (domain user)

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLServer=<SQL_Server_name> WindowsUser=<username@domain.loc> WindowsUserPassword=<password> InstallSQL=0 ScriptDB=1 BackupDir=<backupdirectorypath>

For example, if installing FortiClient EMS and pointing to a remote named instance on a computer with DNS name WIN-088 using Windows authentication, with Windows username "janedoe", password "password123", the command would be as follows. This example also includes the optional SQLEncryptConnection option:

FortiClientEndpointManagement_6.2.1.XXXX_x64.exe SQLServer=WIN-0888 WindowsUser=janedoe@ems.loc WindowsUserPassword=password123 InstallSQL=0 ScriptDB=1 BackupDir=c:\backup\ SQLEncryptConnection=no