[KB7812] Install ESET PROTECT On-Prem on Linux and connect it to SQL Server on Windows

Issue

Solution

2. Before installing ESET PROTECT Server on Linux, make sure the system meets all other prerequisites (except the ODBC driver).
    
3. Download the ESET PROTECT Server installation file from the ESET website.
    
4. Open the Terminal as root, navigate to the folder where you saved the ESET PROTECT Server installer and make the file executable:
   
   

   chmod +x server-linux-x86_64.sh

5. Run the ESET PROTECT Server installer with proper parameters (see example code below).
   

   Installation parameters

   See all available installation parameters in ESET PROTECT Online Help. The code below is an example - substitute highlighted text with your values:

   • Always use --db-type="MS SQL Server"
   • Type the database user username and password as specified in step 2 in section Configure MS SQL Server.
   • In --db-driver= type the ODBC driver name as specified in /etc/odbcinst.ini
      
   sudo ./server-linux-x86_64.sh \
--skip-license \
--db-type="MS SQL Server" \
--db-driver="ODBC Driver 17 for SQL Server" \
--db-hostname=10.20.30.40 \
--db-port=1433 \
--db-admin-username=user \
--db-admin-password=pAssword1 \
--server-root-password=pAssword1 \
--db-user-username=user \
--db-user-password=pAssword1 \
--cert-hostname="10.20.30.50;ubuntu1"
   
   If the installation stops with an error Unknown database driver or data source name you may need to install a different version of MS ODBC driver.
    
6. After the successful installation, the ESET PROTECT Server installed on Linux is connected to SQL Server database installed on Windows.
    
7. You can continue with other ESET PROTECT installation components: Web Console and ESET Management Agent.

III. Enable encrypted connection to MS SQL database (optional)

To improve security, enable an encrypted connection between the ESET PROTECT Server and the SQL database.

Perform the steps below on the ESET PROTECT Server Linux machine:

1. Open the terminal as root.
    
2. Stop the eraserver service:
   
   

   service eraserver stop

3. Open the StartupConfiguration.ini file:
   
   

   nano /etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini

4. Add the following code to the end of the file:
   
   

   Encrypt=yes;TrustServerCertificate=yes;

   Below is an example of the StartupConfiguration.ini file (replace the parts highlighted in yellow with your values):
   
   DatabaseType=MSSQLOdbc
DatabaseConnectionString=Driver=ODBC Driver 17 for SQL Server;Server=10.20.30.40,1433;Uid=era_user;Pwd={SecretPassword};CharSet=utf8;Database=era_db;Encrypt=yes;TrustServerCertificate=yes;
    
5. Save the updated file.
    
6. Start the eraserver service:
   
   

   service eraserver start

7. If you are able to log in to the ESET PROTECT Web Console, the encrypted connection to the database works properly. If you are not able to log in to the ESET PROTECT Web Console, revert your changes to the StartupConfiguration.ini file.