Connect ESET PROTECT Server or MDM to a database

Follow the steps below on the machine where ESET PROTECT Server or ESET PROTECT MDM is installed to connect it to a database.

1.Stop the ESET PROTECT Server/MDM service.

2.Find startupconfiguration.ini

oWindows:
Server:

%PROGRAMDATA%\ESET\RemoteAdministrator\Server\EraServerApplicationData\Configuration\startupconfiguration.ini
 MDMCore:
%PROGRAMDATA%\ESET\RemoteAdministrator\MDMCore\EraServerApplicationData\Configuration\startupconfiguration.ini

oLinux:
Server:

/etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini
 MDMCore:
/etc/opt/eset/RemoteAdministrator/MDMCore/startupconfiguration.ini

3.Change the database connection string in ESET PROTECT Server/MDM startupconfiguration.ini

oSet the address and port of the new database server.

oSet new ESET PROTECT user name and password in the connection string.

The final result should look like:

MS SQL:

DatabaseType=MSSQLOdbc

DatabaseConnectionString=Driver=SQL Server;Server=TARGETHOST,1433;Uid=TARGETERALOGIN;Pwd={TARGETERAPASSWD};CharSet=utf8;Database=TARGETERADBNAME;

MySQL:

DatabaseType=MySqlOdbc
DatabaseConnectionString=Driver=MySQL ODBC 5.3 Unicode Driver;Server=TARGETHOST;Port=3306;User=TARGETERALOGIN;
Password={TARGETERAPASSWD};CharSet=utf8;Database=TARGETERADBNAME;

note

Note

In the configuration above, please always replace:

TARGETHOST with the address of the target database server

TARGETERADBNAME with the name of the target ESET PROTECT database (after migration)

TARGETERALOGIN with the login name for the new ESET PROTECT database user on the target database server

TARGETERAPASSWD with the password of the new ESET PROTECT database user on the target database server

4.Start the ESET PROTECT Server or ESET PROTECT MDM and verify that the service is running correctly.