Decommission the old ESMC/ESET PROTECT/MDM Server after migration to another server
|
Ensure your new ESET PROTECT Server/MDM is running and client computers and mobile devices are connecting to your new ESET PROTECT correctly. |
There are two options when decommissioning your old ESMC/ESET PROTECT Server/MDM after migration to another server:
I.Keep the server machine OS and reuse it
1.Stop the old ESMC/ESET PROTECT Server service.
2.Delete (DROP DATABASE) the old ESMC/ESET PROTECT Server database instance (Microsoft SQL or MySQL).
|
If you migrated the database to the new ESET PROTECT Server, ensure to delete the database on the old ESMC/ESET PROTECT Server before uninstallation to prevent licenses from being dissociated (removed) from the new ESET PROTECT Server database. |
3.Uninstall the old ESET PROTECT/MDM Server and all its components (including ESET Management Agent, Rogue Detection Sensor, MDM etc.):
oUninstall ESET PROTECT—Windows
|
Do not uninstall your database if there is other software dependent on your database. |
4.Plan an operating system restart of your server after uninstallation.
II.Keep the server machine
The easiest way to remove ESMC/ESET PROTECT/MDM is to format the disk where it is installed.
|
This will erase everything on the disk, including the operating system. |