Pricing  Get Quote
 
 

How to configure high availability in Azure using a load balancer

ManageEngine ADSelfService Plus provides a high availability feature to ensure uninterrupted access to the product even for system and product failures. With high availability, when the ADSelfService Plus service on one machine fails, another instance running on a different machine automatically takes over. Since Microsoft Azure does not inherently support ADSelfService Plus' high availability configuration , we use a load balancer to achieve the desired output.

Azure does not support the use of a single IP address for two machines that are part of the same virtual network. In ADSelfService Plus, a single virtual IP address needs to be assigned to the primary and secondary machines while configuring high availability.

The following guide helps you to configure high availability in Azure using a load balancer.

Prerequisite

Create two new virtual machines and install ADSelfService Plus in Azure by following this guide or use the pre-installed virtual machine image available in the Azure marketplace. Make sure both the virtual machines installed in Azure are in the same virtual network and in the same region. Designate the primary and secondary machines as per your requirement.

Configuring high availability settings in the ADSelfService Plus portal

  1. Log into ADSelfService Plus.
  2. Go to Admin → Enterprise Essentials → High Availability
  3. Select Enable High Availability
  4. In the Primary Server section, the URL of the ADSelfService Plus server you are currently accessing (i.e., the primary server) will be auto-filled.
  5. In the Standby Server section, enter the URL of the ADSelfService Plus standby server.
  6. In the Credentials section enter the Admin Username and the Password of a super admin user in the ADSelfService Plus standby server.
    Note: Super admins are users who have been given full control over the entire product.
  7. In the Virtual IP section, enter:
    • A temporary IP address that is not used in your Azure environment.
    • The Virtual Host Name.
      Note: A virtual host name is the alias given to the virtual IP.
    • Click Save.

      configure high availability in ADSelfService Plus portal

    • After successful configuration of high availability, in the fos.conf file (Installation directory→conf) set the publicIP.enabled property to false and restart both virtual machines.

Creating a load balancer in Azure

  1. In the search field present at the top of the Azure portal, enter load balancer and select the option Load balancers.
  2. Click Create.

Basic configuration

  1. In the Basics tab, select the same resource group as that of the virtual machines.
  2. Enter a name in the Name field. (for example: adssp-lb).
  3. In the Region field, select the region of the virtual machines.
  4. For SKU, Type and, Tier, you can choose between the options provided that suit your requirement.
  5. After the settings on the Basics tab are configured, click Next:Frontend IP configuration that displays at the bottom of the screen.

    Create load balancer in Azure

Frontend IP configuration

  1. Click Add a frontend IP configuration.
  2. In the Add frontend IP address tab, enter a name (for example: adssp-lb-frontend) in the Name field.
    Note: The frontend IP configured is the IP address that will be used to access the virtual servers hosting the ADSelfService Plus instance via the load balancer.
  3. If you have chosen Public as the Type in step 6 of Basic configuration, you can create a new public IP address by entering a name or select an IP address from the drop-down menu.
  4. If Internal was chosen as the Type in step 6 of Basic configuration, select a virtual network (same as that of the virtual machine) and subnet. For Assignment, you can choose either Dynamic or Static as per your preference.
  5. Click Next: Backend pools.

    how to setup front ip address for load balancer configuration

Backend pool configuration

  1. Click + to add a backend pool.
  2. In the Name field, enter any name.
  3. Choose the same virtual network as that of the virtual machines.
  4. If Standard was the chosen option for SKU in step 6 of Basic configuration,
    • Select either the NIC or IP Address radio button for Backend Pool Configuration.
    • As per the option you have chosen, you can either select the virtual machines from the list or enter the IP address of the two virtual machines and click Add.

    how to backend pool for load balancer configuration

  5. If the option selected for SKU was Basic in step 6 of Basic configuration,
    • For Associated to, choose the option Virtual machines from the drop-down menu.
    • Click the + button and select the virtual machines from the list.
    • Click Add.

    how to add additional virtual machine

Inbound rules configuration

  1. Click on Add a load balancing rule.
  2. In the Name field, enter a name (for example: adssp-lb-rule).
  3. In the Frontend IP address drop-down menu, select the IP address configured earlier.
  4. Select the backend pool name entered previously from the drop-down menu. (Refer step 14 in the Backend pool configuration section)
  5. For Protocol, choose TCP.
  6. In the Port field, enter a port number through which you wish to access the load balancer
  7. Enter the product port number in the Backend port field.

    load balancing rule configuration

  8. For Health probe, select the option Create new and enter a name.
  9. Choose TCP as the protocol from the drop-down menu and enter the product port number in the Port field.
  10. Leave the default values for the other two settings and click OK.

    how to add load balancing rule for HA setting

  11. In the Session persistence field, enter the Client IP (optional).
  12. Retain the default options for the rest of the settings and click Add.
  13. Keep the default value settings in the Outbound rules and Tags tabs.
  14. Click the option Review + create and then click Create.

Once all the settings are configured, you will be able to access ADSelfService Plus through the configured frontend IP address and port.

Note: The load balancer is used for redistributing the request to the virtual machines in the backend pool. The virtual machines in the pool cannot access the load balancer in the same pool.

 

Request Support

Need further assistance? Fill this form, and we'll contact you rightaway.

Highlights

Password self-service

Free Active Directory users from attending lengthy help desk calls by allowing them to self-service their password resets/ account unlock tasks. Hassle-free password change for Active Directory users with ADSelfService Plus ‘Change Password’ console. 

One identity with Single sign-on

Get seamless one-click access to 100+ cloud applications. With enterprise single sign-on, users can access all their cloud applications with their Active Directory credentials. Thanks to ADSelfService Plus! 

Password/Account Expiry Notification

Intimate Active Directory users of their impending password/account expiry by mailing them these password/account expiry notifications.

Password Synchronizer

Synchronize Windows Active Directory user password/account changes across multiple systems, automatically, including Office 365, G Suite, IBM iSeries and more. 

Password Policy Enforcer

Ensure strong user passwords that resist various hacking threats with ADSelfService Plus by enforcing Active Directory users to adhere to compliant passwords via displaying password complexity requirements.

Directory Self-UpdateCorporate Search

Portal that lets Active Directory users update their latest information and a quick search facility to scout for information about peers by using search keys, like contact number, of the personality being searched.

ADSelfService Plus trusted by

A single pane of glass for complete self service password management