Configuring Failover Server

Downtime is a threat to every enterprise, which would affect productivity. Remote Access Plus offers Failover Server to overcome these challenges. You can configure a secondary server, which will act as a standby server whenever the primary server fails. This ensures that the desktop management system is not aborted due to hardware issues. This document explains the steps to configure the failover server. This feature is supported for computers running Windows XP and later versions.

Prerequisites

Ensure the following criteria are met before configuring the failover server:

Failover is supported only for MSSQL database. Ensure that a license is purchased and uploaded. The database should reside on a remote machine to avoid disruption when one server fails. Use static IP addresses for both primary and secondary servers to maintain proper routing and communication.

Ensure that the Remote Access Plus's primary server, secondary server and the remote database (if any) belong to the same domain and are located in the same subnet. If the primary and secondary servers are on different subnets, contact Support. For NAT configurations, make sure communications are redirected to the virtual IP address.

Configuring Failover Server

You can configure the failover server via Remote Access Plus web console -> Admin -> Server Settings -> Failover Server. Provide the IP addresses of both Primary and Secondary Servers and specify a virtual IP address, which will be used for agent communication. All traffic will be routed to the virtual IP and subsequently to the appropriate server.

The secondary server synchronizes periodically with the primary server to stay updated. You can also configure email notifications in case one of the servers is unreachable.

  1. Clone Server components to secondary server
  2. Configuring Secondary Server
  3. Activate Secondary Server

Clone Server components to secondary server

Perform the following steps on the computer where the (Primary) Remote Access Plus server is installed:

  1. Stop Remote Access Plus server
  2. Navigate to <Installation_Directory>/ManageEngine/UEMS_Server/bin
  3. Execute Clone_Primary_Server.bat to clone and create a zip folder containing the server components
  4. A new zip file Product.zip will be created in the <Installation_Directory>/ManageEngine/UEMS_Server folder
  5. Start Remote Access Plus server

Configure Share Permissions

Ensure that the secondary server has permissions to synchronize the data from the primary server and vice versa.

Enable the following settings:

  • Access to computers where the primary and secondary servers are installed
  • System user permissions to manage both servers

Perform these steps first on the primary server and repeat on the secondary server during activation.

Windows sharing permissions dialog Advanced sharing configuration panel

Steps for Sharing

  1. Right-click on the folder and choose Sharing tab
  2. Click Advanced Sharing
  3. Enable Share this Folder
  4. Specify the name as UEMS_Server
  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 user name with Admin privileges
  11. Click Share Permission, select user and computer, and ensure that Full Control is enabled
  12. Click OKto complete the process.

    If Remote Access Plus server is installed in Windows 10 or Windows Server 2012 R2, ensure permissions are modified under: Right-click Remote Access Plus folder -> Properties -> Security -> Edit Permissions -> Edit -> Add (add the name of the secondary server).

Activate Secondary Server

Perform the following on the computer where the Secondary server is installed:

  1. Download the Configure_Failover_Server.bat from the product: Remote Access Plus web console -> Admin -> Server Settings -> Failover Server
  2. Open Command Prompt as an administrator, navigate to the location where the .bat file is downloaded, and execute Configure_Failover_Server.bat <PrimaryServer_IP>
  3. Repeat the steps for sharing on the secondary server and ensure that you provide the name of the primary server in step 10.

You can now see that the server components are replicated to the secondary server.

Back to Top