Migration of MDM
|
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. |
To migrate MDM (on-premises) from one server to another server, follow the instructions below.
Migration of MDM from one server to another server (on-premises)
This procedure aims to migrate your existing instance of ESET PROTECT MDM and keep your existing ESET PROTECT MDM database, including enrolled mobile devices. The migrated ESET PROTECT MDM will have the same IP address/hostname as the old ESET PROTECT MDM, and the database of the old ESET PROTECT MDM will be imported to the new MDM host before installation.
|
•Migrating databases is only supported between identical database types (from MySQL to MySQL or from Microsoft SQL to Microsoft SQL). •When migrating a database, you must migrate between instances of the same ESET PROTECT version. See our Knowledgebase article for instructions to determine the versions of your ESET PROTECT components. After completing database migration, you can perform an upgrade, if necessary, to get the latest version of ESET PROTECT. |
I. On your current (old) ESET PROTECT MDM server:
1.Create a backup of MDM configuration.
a)In Computers, click the MDM Server and select Details.
b)Click Configuration > Request configuration. You may need to wait some time (depending on your Agent connection interval) until the requested configuration is created.
c)Click the ESET PROTECT Mobile Device Connector and select Open Configuration.
d)Export the following items from the configuration to external storage:
oThe exact Hostname of your MDM Server.
oPeer Certificates - The exported .pfx file will have the private key included.
|
If you are running ESET PROTECT MDM server on Linux, you need to export the HTTPS certificate from the MDM configuration policy: I.Click View next to HTTPS Certificate. II.Click |
e)Export the following certificates and tokens as well if present:
oThe enrollment profile signing certificate.
oAn APNS Certificate (export both APNS Certificate and APNS Private Key).
oApple Business Manager (ABM) authorization token.
2.Stop the ESET PROTECT MDM service.
3.Export/Back up the ESET PROTECT MDM Database.
4.Turn off the current ESET PROTECT MDM machine.
|
Do not uninstall/decommission your old ESET PROTECT MDM yet. |
II. On your new ESET PROTECT MDM Server:
|
Ensure the network configuration on your new ESET PROTECT MDM server (the hostname you exported from the configuration of your "old" MDM server) matches that of your old ESET PROTECT MDM. |
1.Install/Launch a supported ESET PROTECT MDM database.
2.Import/Restore the ESET PROTECT MDM database from your old ESET PROTECT MDM.
3.Install ESET PROTECT Server/MDM using the All-in-one package installer (Windows) or choose another installation method (Windows manual installation, Linux or Virtual Appliance). Specify your database connection settings during installation of ESET PROTECT MDM.
|
When installing ESET PROTECT MDM on Linux, use the HTTPS certificate from your backup. |
4.Connect to the ESET PROTECT Web Console.
5.Restart the ESET PROTECT MDM service.
Managed mobile devices should now connect to your new ESET PROTECT MDM server using their original certificate.
III. Old ESET PROTECT Server/MDM uninstallation:
When you have everything running correctly on your new ESET PROTECT Server, carefully decommission your old ESET PROTECT Server/MDM using our step-by-step instructions.