Mobile Device Connector prerequisites - Linux

The following prerequisites must be met in order to install Mobile Device Connector on Linux:

A Database Server already installed and configured with a root account (a user account doesn't have to be created prior to installation, the installer can create the account).

An ODBC Driver for the connection to the database server (MySQL / MS SQL) installed on the computer. See the chapter ODBC installation and configuration.

validation-status-icon-infoNOTE: You should use unixODBC_23 package (not the default unixODBC) in order for the ERA Server to connect to the MySQL database without any issues. This is especially true for SUSE Linux.

oMDMCore installation file set as an executable.

chmod +x MDMCore-Linux-x86_64.sh

oAfter installation, verify that MDMCore service is running.

service eramdmcore status

oThe minimum supported version of openSSL is openssl-1.0.1e-30; openssl 1.1.* and later is not supported (the command openssl version shows current version).

validation-status-icon-infoNOTE: If your MDM database on MySQL is too large (thousands of devices) the default innodb_buffer_pool_size value is too small. For more information database optimizing see: http://dev.mysql.com/doc/refman/5.6/en/optimizing-innodb-diskio.html

validation-status-icon-warning IMPORTANT: You will need an SSL certificate in .pfx format for secure communication over HTTPS. We recommend that you use a certificate provided by a Certificate Authority (ERA CA or 3rd party CA). Self-signed certificates are not recommended because not all mobile devices let users to accept self-signed certificates. This isn't an issue with CA signed certificates, because they are trusted and do not require acceptance by the user.

validation-status-icon-infoNOTE: You need to have certificate signed by CA (ERA CA or 3rd party CA), and corresponding private key, and utilize standard procedures, to merge those (traditionally using OpenSSL) into one .pfx file:

openssl pkcs12 -export -in certificate.cer -inkey privateKey.key -out httpsCredentials.pfx
This is a standard procedure for most servers which are using SSL certificates.

validation-status-icon-warning IMPORTANT: For Offline installation, you will also need a Peer certificate (the Agent certificate exported from ESET Remote Administrator). Alternatively, you can use your custom certificate with ERA.