Mobile Device Connector prerequisites

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

Public IP address or public domain accessible from the Internet.

validation-status-icon-infoNOTE: If you need to change the hostname of your MDM Server, you will need to run a repair installation of your MDC component. If you change the hostname of your MDM Server, you will need to import a new HTTPS Server certificate that includes this new hostname for MDM to continue working correctly.

Ports open and available - see the complete list of ports here. We recommend using default port numbers 9981 and 9980, but these can also be changed in configuration file of your MDM Server if needed. Make sure that mobile devices are able to connect via specified ports. Change your firewall and/or network settings (if applicable) to make this possible. For more information about MDM architecture click here.

Firewall settings - if installing Mobile Device Connector on non-server OS such as Windows 7 (for evaluation purpose only), make sure to allow communication ports by creating firewall rules for:

C:\Program Files\ESET\RemoteAdministrator\MDMCore\ERAMDMCore.exe, TCP port 9980

C:\Program Files\ESET\RemoteAdministrator\MDMCore\ERAMDMCore.exe, TCP port 9981

C:\Program Files\ESET\RemoteAdministrator\Server\ERAServer.exe, TCP port 2222

 

validation-status-icon-infoNOTE: Actual paths to .exe files may vary depending on where each of the ERA components is installed on your client OS system.

A database server already installed and configured. Make sure you met Microsoft SQL or MySQL requirements.

RAM usage of MDM connector is optimized so there can be maximum of 48 "ESET Remote Administrator MDMCore Module" processes running concurrently and if the user connects more devices, the processes will then periodically change for each device that currently needs to use the resources.

Microsoft .NET Framework 3.5 must be installed, if you are running Windows Server 2008 and later you can install it using the Roles and Features Wizard (as shown below), if you are using Windows Server 2003, you can download .NET 3.5 here: http://www.microsoft.com/en-us/download/details.aspx?id=21

install_net_framework

Certificate requirements

validation-status-icon-warning IMPORTANT: You will need an SSL certificate in .pfx format for secure communication over HTTPS. We recommend that you use the certificate provided by your Certificate Authority (ERA CA or 3rd party CA). Self-signed certificates are not recommended because not all mobile devices let users 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 a certificate signed by CA (ERA CA or 3rd party CA), a corresponding private key, and utilize standard procedures to merge (traditionally using OpenSSL) them 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: In the case of Offline installation, you will also need an Agent certificate exported from ESET Remote Administrator. Alternatively, you can use your custom certificate with ERA.