ESET Online Help

Search English
Select the category
Select the topic

Mobile Device Connector installation - Windows


ESET PROTECT Mobile Device Management/Connector (MDM/MDC) component (on-premises only) reached End of Life in January 2024. Read more. We recommend that you migrate to Cloud MDM.


Mobile Device Connector must be accessible from the internet so that mobile devices can be managed at all times regardless of their location.


We recommend that you deploy your MDM component on a host device separate from the one ESET PROTECT Server is hosted on.

Follow the steps below to install the Mobile Device Connector component for ESET PROTECT Server on Windows:


Ensure to meet all the installation prerequisites.

1.Visit the ESET PROTECT download section to download a standalone installer for this ESET PROTECT component (mdmcore_x64.msi).

2.Run the Mobile Device Connector installer and accept the EULA if you agree with it.

3.Click Browse, navigate to the location of your SSL certificate for communication via HTTPS, type in the password for this certificate.

4.Specify MDM hostname: this is the public domain or public IP address of your MDM server as it is reachable by mobile devices from the internet.


MDM hostname must be typed in the same form as specified in your HTTPS Server certificate, otherwise the iOS mobile device will refuse to install MDM Profile. For example, if there is an IP address specified in the HTTPS certificate, type in this IP address into the MDM hostname field. If FQDN is specified (e.g. in the HTTPS certificate, type this FQDN in MDM hostname field. Also, if there is a wildcard * used (e.g. * in HTTPS certificate, you can use in the MDM hostname field.

5.The installer now needs to connect to an existing database that which will be used by Mobile Device Connector. Specify the following connection details:

Database: MySQL Server/MS SQL Server/MS SQL Server via Windows Authentication

ODBC Driver: MySQL ODBC 5.1 Driver/MySQL ODBC 5.2 Unicode Driver/MySQL ODBC 5.3 Unicode Driver/MySQL ODBC 8.0 Unicode Driver/MySQL ODBC 8.1 Unicode Driver/SQL Server/SQL Server Native Client 10.0/ODBC Driver 11 for SQL Server/ODBC Driver 13 for SQL Server/ODBC Driver 17 for SQL Server/ODBC Driver 18 for SQL Server

Database name: We recommend using the pre-defined name or changing it if required.

Hostname: hostname or the IP address of your database server

Port: used for connection to the database server

Database admin account Username/Password

Use Named Instance - If you use a Microsoft SQL database, you can select the Use Named Instance check box to use a custom database instance. You can set it in the Hostname field in the form HOSTNAME\DB_INSTANCE (for example,\ESMC7SQL). For a clustered database, use only the cluster name. If this option is selected, you cannot change the database connection port - the system will use default ports determined by Microsoft. To connect the ESET PROTECT Server to the Microsoft SQL database installed in a Failover Cluster, type the cluster name in the Hostname field.


You can use the same database server you are using for ESET PROTECT database, but it is recommended to use a different DB server if you are planning to enroll more than 80 mobile devices.

6.Specify user for newly created Mobile Device Connector database. You can Create new user or Use existing database user. Type in the password for the database user.

7.Type Server host (name or IP address of your ESET PROTECT Server) and Server port (default port is 2222, if you are using different port, then replace the default port with your custom port number).

8.Connect the MDM Connector to the ESET PROTECT Server. Fill in the Server host and Server port required for connection to the ESET PROTECT Server and select either Server Assisted installation or Offline Installation to proceed:

Server assisted installation - Provide ESET PROTECT Web Console administrator credentials and the installer will download the required certificates automatically. Also check the permissions required for server-assisted installation.

1.Type your Server host - name or IP address of your ESET PROTECT Server and Web Console port (leave default port 2223 if you are not using custom port). Also, provide Web Console administrator account credentials - Username/Password.

2.When asked to Accept the Certificate, click Yes. Continue to step 10.

Offline installation - Provide a Proxy certificate and Certification Authority which can be exported from ESET PROTECT On-Prem. Alternatively, you can use your custom certificate and appropriate Certification Authority.

1.Click Browse next to the Peer certificate and navigate to the location of your Peer certificate location (this is the Proxy certificate you have exported from ESET PROTECT On-Prem). Leave the Certificate password text field blank as this certificate does not require a password.

2.Repeat the procedure for Certificate Authority and continue to step 10.


If you are using custom certificates with ESET PROTECT On-Prem (instead of the default ones that were automatically generated during ESET PROTECT On-Prem installation), these should be used when you are prompted to supply a Proxy certificate.

9.Specify destination folder for Mobile Device Connector (we recommend using default), click Next, then Install.

10. After the installation is complete, check if the Mobile Device Connector is running correctly by opening https://your-mdm-hostname:enrollment-port (for example in your web browser or from mobile device. If the installation was successful, you will see following message: MDM Server up and running!

11. You can now activate MDM from ESET PROTECT On-Prem.