# Configuring Failover Server Last updated: August 18, 2026 This page explains how to configure a secondary failover server in Mobile Device Manager Plus, which acts as a standby and takes over device management routines automatically if the primary server goes down. Downtime affects productivity and is a threat to every enterprise. Mobile Device Manager Plus allows admins to configure a secondary server that acts as a standby, whenever the primary server fails. The data in the primary server is replicated regularly on to the secondary server to ensure the device management routine is not hampered when the primary server goes down. This document explains the steps involved in configuring the failover server. ## Prerequisites Ensure the following requirements are met before configuring the failover server. - License for the failover server- The lincense for the failover server must be purchased and uploaded on the product. - Remote MSSQL Database- The failover server works only with an MSSQL database. Ensure the database is installed on a remote computer present in the same network as the MDM server. - Static IP Address- A static IP address must be configured for the primary and secondary servers. Follow the steps given below to assign a static IP to these servers: 1. Navigate to **Control Panel -> Network and Internet -> Network and Sharing Center -> Ethernet -> Properties**. 2. In Properties, select **Internet Protocol version 4**. 3. Modify the mode from **Obtain IP address automatically** to **Use the following IP**. 4. Enter the required static IP for the servers. ![Failover Server3](https://www.manageengine.com/mobile-device-management/help/failover_server3.png) | Icon | Details | |---|---| | ![Infoicon](https://www.manageengine.com/mobile-device-management/help/images/infoicon.png) | Ensure that the Mobile Device Manage Plus' primary and the secondary servers belong to the same domain and are located in the same subnet. If you have configured NAT settings to redirect all communications to a local IP, ensure that the redirected communications reach the virtual IP address. | ## Configuring Failover Server Follow the steps to configure failover server: 1. Navigate to **Admin -> Setting up MDMP ->Failover Server** 2. Check if all the pre-requisites for configuring the failover server are met. Click on **Continue** to proceed with failover server configuration. 3. Specify the **primary and secondary servers' IP address** along with a **virtual IP address**. The communication from the managed devices is routed through the virtual IP. If NAT is configured to redirect all communications to a local IP, ensure the redirected communications reach the virtual IP address. All requests that reach this virtual IP will be redirected to the primary server. If the primary server is not reachable, the communications will be moved to the secondary server. The secondary server will periodically sync all the data from the primary server, so that it is up-to-date. Settings can be configured to receive mail notifications, whenever one of the server is down or not reachable. ## Activate Failover Server Follow the steps given below to activate the failover server: 1. [Providing required permissions](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/configuring_failover_server.html#permission) 2. [Clone server components to secondary server](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/configuring_failover_server.html#clone) 3. [Activate secondary server](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/configuring_failover_server.html#activate_server) ## Providing Required Permissions | Icon | Details | |---|---| | ![Infoicon](https://www.manageengine.com/mobile-device-management/help/images/infoicon.png) | Ensure the secondary server has permissions to sync data from the primary server and vice versa. | You will have to enable the following settings: - **Access to computers** where Mobile Device Manager Plus primary and secondary servers are installed. - **Permission for the admin** to manage both the primary and secondary servers of Mobile Device Manager Plus. During activation the below mentioned steps should first be performed on the primary server and then the secondary server. ![Failover Server1](https://www.manageengine.com/mobile-device-management/help/failover_server1.png) ![Failover Server2](https://www.manageengine.com/mobile-device-management/help/failover_server2.png) Steps for sharing: 1. Right click on the folder and click on the **Sharing** tab. 2. Click **Advanced Sharing**. 3. Enable **Share this Folder**. 4. Specify the name as **MDMServer**. 5. Click **Permissions**. 6. Click **Add**. 7. Choose **Object Types**. 8. Enable **Computers**. 9. Click **OK**. 10. Under **Enter Object Name**, specify the secondary server name and the username with Admin privileges. 11. Click **Share Permission** and select **user** and **computer**. Ensure **Full Control** is enabled. 12. Click **OK** to complete the process. ## Clone Server Components to Secondary Server Perform the following steps on the computer where the primary Mobile Device Manager Plus server is installed: 1. Stop the Mobile Device Manager Plus server. 2. Navigate to **/ManageEngine/MDMServer/bin** 3. Execute **Clone_Primary_Server.bat** to clone and create a zip folder which contains the server components. 4. A new zip file "product.zip" will be created in the **"/ManageEngine/MDMServer>"** folder. ## Activate Secondary Server Perform the steps mentioned below on the computer where the secondary server is installed: 1. Download **Configure_Failover_Server.bat** from the product by navigating to **Admin -> Setting up MDMP ->Failover Server** and execute it. 2. Repeat the [steps for sharing](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/configuring_failover_server.html#Steps_for_Sharing) as mentioned above on the secondary server and ensure that the name of the computer where the primary server is installed is provided in step 10. The server components are replicated to the secondary server from the primary server. | Section | Links | |---|---| | **See Also:** | [Configuring Proxy Server](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/mdm_proxy_settings.html), [Configuring Mail Server](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/mdm_mail_server_settings.html), [Configuring Server Settings](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/mdm_server_settings.html), [Configuring Remote DB Access](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/mdm_remote_db_access.html), [Importing SSL Certificates](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/import_ssl_certificates.html), [User Administration](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/user_administration.html), [Personalize MDM](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/personalize_client_settings.html), [Data Backup and Restore](https://www.manageengine.com/mobile-device-management/help/configuring_mobile_device_manager/data_backup_and_restore.html) | ## Frequently Asked Questions - **What are the prerequisites for setting up a failover server in ManageEngine MDM?** The failover server requires the same OS and MDM version as the primary server, access to the same database, and a shared network path for data synchronization between primary and standby servers. - **Does the failover server take over automatically when the primary server fails?** Yes. Once configured, the failover server automatically detects primary server unavailability and takes over device management operations, ensuring continuity without manual intervention. - **Can both the primary and failover servers manage devices simultaneously?** No. The failover server operates in standby mode and only becomes active when the primary server is unreachable. Both servers cannot manage devices at the same time to avoid data conflicts.