How to migrate ADSelfService Plus in a failover or load balancing environment

Last updated on:

Objective

Moving an ADSelfService Plus failover or load balancing deployment to new application servers lets you replace or upgrade the servers while keeping the existing external database, along with all the configuration and user data stored in it.

Failover and load balancing both require an external database, so the built-in PostgreSQL backup and restore procedure used for single-server migrations does not apply here. Your configuration, self-service policies, MFA enrollment data, technicians, and reports are all stored in the external database, and connecting new servers to that database is what carries the deployment across. Only the items that are not stored in the database, such as the SSL certificate, branding, applied patches, and custom language files, have to be copied across manually.

Note:

To set up failover or load balancing for the first time, or to convert a single-server installation into a failover deployment, refer to the Failover and Load Balancing sections of the admin guide.

Prerequisites

Ensure that the following requirements are met before you begin.

  • Deployment: An existing failover or load balancing deployment, with the Failover and Secure Gateway Services add-on licensed.
  • External database: A PostgreSQL or Microsoft SQL database already in use by the deployment.
  • Build: Every server must run the same ADSelfService Plus build number and the same build architecture (32-bit or 64-bit). To check the current build number, log in to the admin portal and click the License link in the top-right corner.
  • Installation: ADSelfService Plus must be installed and run as a Windows service on each new server, as it is on the existing ones.
  • Service account: The account that runs the service, and the local account used to launch the product, must have Full Control over the ADSelfService Plus installation directory. In a failover deployment, the account must also have Share permissions so that the installation directory can be shared between instances.
  • Ports: The product port must be open and identical on every server. The defaults are 8888 for HTTP and 9251 for HTTPS. Port 7800 must be open between the nodes for the failover or load balancing service. If 7800 is already in use, 7801 is assigned, then 7802, and so on.
  • Consistency: Every server must use the same protocol, the same context path if one is configured, and the same system time and time zone.
  • Access: Administrator access to ADSelfService Plus, and the Super Admin user name and password of each secondary server.
  • Database credentials: The host name, port, database name, user name, and password of the external database.
Note:

Update the existing deployment to the latest build before you start. Shut down every node, back up the external database, apply the service pack to the primary server first, then to each secondary, and start the primary before the secondaries. This ensures the new servers can be installed at a build that matches.

Before you begin

Two decisions shape the entire migration. Settle both before you touch the deployment.

Decide whether the virtual hostname or virtual IP will change

The virtual hostname and virtual IP identify the deployment as a whole, not any individual server. If they stay the same, the login agents, the NPS extension used for VPN MFA, the ADSelfService Plus MFA Connector used for OWA MFA, and every enrolled FIDO2 passkey continue to work without changes, because none of them ever referenced the individual server names.

If they change, the access URL changes with them. The Relying Party ID (RP ID) used by the FIDO2 Passkeys authenticator is derived from the access URL, so changing it invalidates every enrolled passkey.

Important:

If FIDO2 Passkeys is configured, retain the existing virtual hostname or virtual IP. Changing the access URL results in the loss of all passkey enrollment data and disenrolls every user, who must then enroll again.

Plan for the interruption to MFA-protected logins

If Endpoint MFA secures machine logins, an unreachable ADSelfService Plus server prevents users from logging in to their machines. OWA MFA similarly prevents access to mailboxes. Before you take the deployment down, confirm one of the following for every affected policy:

  • Offline MFA is configured and users’ machines are enrolled for it, or
  • Skip MFA when the ADSelfService Plus server is down or unreachable is enabled under Configuration > Self-Service > Multi-factor Authentication > Advanced > Endpoint MFA.
Note:

For OWA and VPN MFA, enabling the skip option in the product is not sufficient on its own. Set the BypassMFAOnConnectionError property to TRUE in the registry on the machine hosting the connector or the NPS extension. The keys are HKEY_LOCAL_MACHINE\SOFTWARE\ZOHO Corp\ADSelfService Plus IIS MFA Module and HKEY_LOCAL_MACHINE\SOFTWARE\ZOHO Corp\ADSelfService Plus NPS Extension respectively. Take a backup of the registry key before editing it.

Choosing a migration approach

Two approaches are available. Both end with the same result, and they differ only in how much downtime the switch costs.

Criterion Rebuild the deployment Migrate through a planned failover
Downtime The full migration window, from the moment the old servers are stopped until the new deployment is validated. The failover interval plus the promotion step.
Complexity Lower. The old and new deployments never coexist. Higher. The new servers join the running deployment before the switch.
When to use Deployments that can take a maintenance window. Deployments where Endpoint MFA means that downtime locks users out of their machines.

Steps to migrate ADSelfService Plus to new servers

Step 1: Record the current configuration

On the existing primary server, record the following values. You will reproduce them exactly on the new servers.

  1. The build number and architecture, from the License link in the top-right corner of the admin portal.
  2. The product port and protocol, and the context path if one is used, from Admin > Product Settings > Connection.
  3. The access URL, from Admin > Product Settings > Connection > Configure Access URL.
  4. The virtual IP and virtual host name, and the load balancing port if load balancing is configured, from Admin > Enterprise Essentials > Failover and Secure Gateway.
  5. The external database type, host name, port, database name, and credentials. The connection details are also stored in database_params.conf in the conf folder of the installation directory.
  6. The node that runs scheduled jobs, from Manage Scheduled Jobs on the Failover and Secure Gateway page. This applies to load balancing deployments only.
  7. The RADIUS shared secrets, and the values under HKEY_LOCAL_MACHINE\SOFTWARE\ZOHO Corp\ADSelfService Plus NPS Extension, if VPN MFA is configured.
  8. Whether a reverse proxy is configured, and the IP address of the reverse proxy server.

Step 2: Back up the deployment

  1. Take a full native backup of the external database, using the tooling for PostgreSQL or Microsoft SQL.
  2. Compress the ADSelfService Plus installation directory on the primary server and on every secondary server. The default location is C:\Program Files\ManageEngine\ADSelfService Plus.
Note:

The Backup Now option and the backup scheduler under Admin > Product Settings > Backup Settings operate on the built-in PostgreSQL database only, and cannot be used to back up an external database. In a failover or load balancing deployment they are unavailable for this reason.

Step 3: Remove the cluster configuration and stop the servers

  1. With every server still running, log in to the primary server and go to Admin > Enterprise Essentials > Failover and Secure Gateway.
  2. Click Remove Configuration and confirm the action. The primary server restarts, and the secondary servers are no longer part of the deployment.
  3. On each secondary server, open the Services console by pressing Win + R, typing services.msc, and pressing Enter. Right-click ManageEngine ADSelfService Plus and select Stop.
  4. Stop the ManageEngine ADSelfService Plus service on the primary server in the same way.
Important:

Remove the configuration before you stop any server. Configuration changes can be made only from the primary server, and a secondary server that is offline when the configuration is removed must be decommissioned manually afterwards to avoid leaving it in an insecure state.

Step 4: Install ADSelfService Plus on each new server

Repeat the following steps on the new primary server and on each new secondary server.

  1. Install the same build number and the same architecture as the deployment you are replacing, using the same port and protocol. Download the matching build from the ADSelfService Plus website, or contact support@adselfserviceplus.com if the build is no longer listed.
  2. Install the product as a service by going to Start > ADSelfService Plus > Install ADSelfService Plus as a Service.
  3. In the Services console, right-click ManageEngine ADSelfService Plus, select Properties, open the Log On tab, select This account, and enter the service account credentials.
  4. Grant the service account Full Control over the installation directory.
  5. If the external database is Microsoft SQL, install the MS SQL Native Client or the appropriate ODBC driver, then copy bcp.exe and bcp.rll into the bin folder of the installation directory. To confirm that the dependencies resolved correctly, open Command Prompt in that folder and run bcp.exe /v. The version is displayed if the dependencies are in place.

Step 5: Copy the customization files to each new server

The external database does not hold the following items. Copy them from each old server to the corresponding new server.

Customization File(s) / Folder(s) to copy Default location
SSL certificate server.p12 (or your keystore file), server.xml, web.xml ..\ADSelfService Plus\conf
Branding and login page html, images, resources, and styles folders ..\ADSelfService Plus\webapps\adssp
Custom language resources folder ..\ADSelfService Plus
Applied patches patch folder ..\ADSelfService Plus
Mobile app configuration MPM folder ..\ADSelfService Plus
BCP utilities bcp.exe and bcp.rll ..\ADSelfService Plus\bin
Important:

Copy these files to every node, not only to the primary server. Branding, SSL, and login agent customization are read from each server’s own installation directory, so a secondary server brought up without them will serve a differently branded portal the moment it becomes active. If the files are not restored, customizations such as language changes, SSL configuration, login page design, and login agent behavior will not work correctly.

Step 6: Connect the new primary server to the external database

  1. On the new primary server, confirm that the ManageEngine ADSelfService Plus service is stopped.
  2. Right-click Command Prompt and select Run as administrator.
  3. Navigate to the bin folder of the installation directory using the cd command. The default path is C:\Program Files\ManageEngine\ADSelfService Plus\bin.
  4. Run the database configuration script. The Database Setup Wizard opens.
changeDB.bat

In the Database Setup Wizard that appears:

  1. In the Server Type field, select MSSQL Server or Pgsql Server to match your external database.
  2. Enter the Host Name, Port, Database Name, User Name, and Password that you noted from the existing primary server. For Microsoft SQL, also select the Instance and the Authentication method.
  3. Leave the Migrate Data From Existing Server checkbox cleared.
  4. Click Test to verify the connection, then click Save.
Important:

Leave the Migrate Data From Existing Server checkbox cleared. The data is already present in the database you are connecting to, and selecting the checkbox starts a data migration that is not required. The checkbox is available in build 6527 and later.

Note:

Run changeDB.bat on the new primary server only. Secondary servers use the database configured on the primary server, and receive that configuration when you set up failover or load balancing.

Step 7: Create the failover or load balancing configuration

  1. Start the ManageEngine ADSelfService Plus service on the new primary server, and then on each new secondary server.
  2. Log in to the new primary server as an administrator.
  3. Go to Admin > Enterprise Essentials > Failover and Secure Gateway, and click Click to Configure.
  4. In the Deployment Mode field, select Failover or Load Balancing to match the deployment you are replacing.
  5. In the Primary Server section, confirm that the Primary Server URL is correct. ADSelfService Plus fills in the URL of the server you are currently accessing.
  6. In the Secondary Server(s) section, enter the Secondary Server URL, Admin Username, and Admin Password of the first new secondary server. Click + Add Secondary Server and repeat for each additional node.
  7. In the Access Mode section, enter the virtual IP, virtual host name, and load balancing port that you recorded from the existing primary server:
    • Same subnet: Leave the Primary and Secondary Servers are on Different Subnets checkbox cleared, and enter the Virtual IP and Virtual Hostname. The virtual IP binds automatically to whichever server is active.
    • Different subnets: Select the Primary and Secondary Servers are on Different Subnets checkbox and enter the Virtual Hostname. A virtual IP cannot be used across subnets.
    • Load balancing: Also enter the Load Balancing Port. It must be different from the product port.
  8. Click Configure. The primary server restarts first, and the secondary servers restart once it is up.
Note:

When the servers are on different subnets and the active server changes, your DNS or network administrator must update the virtual host name’s DNS record to point to the new active server. This is not automatic.

Note:

If RADIUS Authentication is used as an MFA method, configure every new node on the RADIUS server with the same shared secret, and use that secret when enabling RADIUS authentication.

Step 8: Reassign scheduled jobs

This step applies to load balancing deployments only. The Manage Scheduled Jobs setting names a specific node, and that assignment is not carried over from the old deployment.

  1. On the primary node, go to Admin > Enterprise Essentials > Failover and Secure Gateway.
  2. Click Manage Scheduled Jobs in the top-right corner.
  3. In the Run Scheduled Jobs On drop-down, select the node that should run scheduled jobs such as report generation and directory synchronization.
  4. Select the Enable Scheduler Failover checkbox so that scheduled jobs move to the first available node if the selected node goes down.
  5. Click Save, and restart the server for the change to take effect.
Note:

In a failover deployment this step is not required. Scheduled jobs run on the primary server by default, and move automatically to whichever server takes over as the active server.

Step 9: Reconnect the dependent components

Update every component that points at the ADSelfService Plus deployment.

Component Action required
Access URL Go to Admin > Product Settings > Connection and click Configure Access URL. Set the Server Name to the virtual host name, or to the load balancer URL in a load balancing deployment, then set the Protocol and Port and click Save.
SSL certificate Apply the certificate on each node from Admin > Product Settings > Connection > Apply SSL Certificate. The certificate must be configured individually on every node and must be uniform across all of them. Restart each server afterwards.
Login agents No action is needed if the virtual host name is unchanged. If it changed, update Configure Access URL on the GINA/Mac Customization page under Configuration > Administrative Tools > GINA/Mac/Linux (Ctrl+Alt+Del), then run the customization scheduler so that the agents already installed pick up the new address.
VPN MFA Register every new node as a RADIUS client on the RADIUS server using the same shared secret. Set the ServerName value under HKEY_LOCAL_MACHINE\SOFTWARE\ZOHO Corp\ADSelfService Plus NPS Extension to the virtual host name, and confirm ServerPortNo and ServerContextPath.
OWA MFA Confirm that the ADSelfService Plus MFA Connector resolves the updated access URL, and that the ADSelfService Plus SSL certificate is installed on the Exchange server.
Reverse proxy Add the reverse proxy server’s IP address to the internalProxies value of the RemoteIpValve entry in server.xml, in the conf folder of each node.
Integrations Verify the ADManager Plus, ServiceDesk Plus, ServiceDesk Plus Cloud, Splunk, Syslog, Have I Been Pwned, and Log360 integrations under Admin > Product Settings > Integration Settings.
Important:

Without the internalProxies entry, ADSelfService Plus treats every request as originating from the reverse proxy server rather than from the actual client. Audit reports, IP-based conditional access rules, and the anti-hacking system will not work correctly until the entry is added.

Note:

Enabling failover or load balancing on a deployment that already forwards logs to Log360 can disrupt log file recognition from the secondary nodes. If log forwarding stops working after the migration, re-integrate Log360 with ADSelfService Plus.

Migrating through a planned failover

Use this approach when downtime must be kept to a minimum. The new servers join the running deployment as secondary servers, and the switch is made by stopping the old primary server so that failover takes place.

Note:

A secondary server cannot be promoted while the primary server is still running. Stopping the old primary server deliberately is what makes the Promote as Primary option available.

  1. On the existing primary server, note down the following details so that you can set up the new servers identically.
    1. Build number and architecture, shown when you click the License link at the top right of the admin portal.
    2. Product port, protocol, and context path (if one is set), under Admin > Product Settings > Connection.
    3. Access URL, under Admin > Product Settings > Connection > Configure Access URL.
    4. Virtual IP, virtual host name, and load balancing port (in a load balancing deployment), under Admin > Enterprise Essentials > Failover and Secure Gateway.
    5. External database type, host name, port, database name, and credentials. These connection details are also saved in database_params.conf, in the conf folder of the installation directory.
    6. In a load balancing deployment, the node assigned to run scheduled jobs, under Manage Scheduled Jobs on the Failover and Secure Gateway page.
    7. If VPN MFA is configured, the RADIUS shared secrets and the values under HKEY_LOCAL_MACHINE\SOFTWARE\ZOHO Corp\ADSelfService Plus NPS Extension.
    8. If a reverse proxy is in use, the IP address of the reverse proxy server.
  2. Back up the running deployment.
    1. Back up the external database in full with the native PostgreSQL or Microsoft SQL tools. Backup Now and the backup scheduler under Admin > Product Settings > Backup Settings cannot be used here. They work only with the built-in PostgreSQL database, which is why they are unavailable in failover and load balancing deployments.
    2. On the primary server and every secondary server, compress the ADSelfService Plus installation directory (C:\Program Files\ManageEngine\ADSelfService Plus by default).
  3. Install ADSelfService Plus on the new primary server and on every new secondary server. Do not run changeDB.bat, and do not create a new failover or load balancing configuration.
    1. Use the same build number and architecture as the existing deployment, with the same port and protocol. Get the matching build from the ADSelfService Plus website, or contact support@adselfserviceplus.com if it is no longer listed.
    2. To run the product as a service, go to Start > ADSelfService Plus > Install ADSelfService Plus as a Service.
    3. Open the Services console and right-click ManageEngine ADSelfService Plus. Select Properties, go to the Log On tab, select This account, and enter the credentials of the service account.
    4. Give the service account Full Control over the installation directory.
    5. For a Microsoft SQL database, install the MS SQL Native Client or the appropriate ODBC driver, and place bcp.exe and bcp.rll in the bin folder of the installation directory. To check that the dependencies resolved, open Command Prompt in that folder and run bcp.exe /v. If they are in place, the command displays the version.
  4. On every new server, including the secondary servers, copy the following customization files from the corresponding old server. These items are not stored in the external database, and each node reads its branding, SSL, and login agent customization from its own installation directory. Without these files, a node serves a differently branded portal as soon as it becomes active, and language changes, SSL configuration, login page design, and login agent behavior do not work correctly.
    1. SSL certificate: server.p12 (or your keystore file), server.xml, and web.xml, located by default in ..\ADSelfService Plus\conf
    2. Branding and login page: the html, images, resources, and styles folders, located by default in ..\ADSelfService Plus\webapps\adssp
    3. Custom language: the resources folder, located by default in ..\ADSelfService Plus
    4. Applied patches: the patch folder, located by default in ..\ADSelfService Plus
    5. Mobile app configuration: the MPM folder, located by default in ..\ADSelfService Plus
    6. BCP utilities: bcp.exe and bcp.rll, located by default in ..\ADSelfService Plus\bin
  5. Start the ManageEngine ADSelfService Plus service on each new server, and confirm that each one is reachable from the existing primary server. A node whose service is stopped cannot be added to the deployment.
  6. On the existing primary server, go to Admin > Enterprise Essentials > Failover and Secure Gateway, click + Add Secondary Server, and enter the Secondary Server URL, Admin Username, and Admin Password of each new server. Click Configure. The new nodes restart and join the deployment, receiving the database configuration from the primary server.
  7. Confirm that every new node has joined and is reachable on the Failover and Secure Gateway page.
  8. Stop the ManageEngine ADSelfService Plus service on the old primary server. Failover takes place and one of the remaining servers begins serving requests. On a same-subnet deployment the virtual IP binds to it automatically. On a different-subnet deployment, ask your DNS administrator to repoint the virtual host name.
  9. Log in to one of the new servers. When the promotion prompt appears, click Promote Now. You are redirected to the Failover and Secure Gateway page, where the available standby servers are listed.
  10. Click Promote as Primary for the new server that should become the primary server.
  11. On the new primary server, hover over the entry for each old server and click the remove icon to drop it from the deployment. Confirm each removal.
  12. In a load balancing deployment, reassign scheduled jobs, because the node assignment is not carried over from the old deployment. A failover deployment can skip this step, since scheduled jobs run on the primary server by default and move automatically to whichever server becomes active.
    1. On the primary node, open Admin > Enterprise Essentials > Failover and Secure Gateway and click Manage Scheduled Jobs at the top right.
    2. From the Run Scheduled Jobs On drop-down, choose the node that should handle scheduled jobs such as report generation and directory synchronization.
    3. Select Enable Scheduler Failover so that scheduled jobs shift to the first available node if the selected node goes down.
    4. Click Save, then restart the server to apply the change.
  13. Update each component that connects to the ADSelfService Plus deployment.
    1. Access URL: In Admin > Product Settings > Connection, click Configure Access URL. Enter the virtual host name as the Server Name (or the load balancer URL, in a load balancing deployment), set the Protocol and Port, and click Save.
    2. SSL certificate: On every node, apply the certificate from Admin > Product Settings > Connection > Apply SSL Certificate. Each node needs its own configuration, and every node must use the same certificate. Restart each server when you are done.
    3. Login agents: If the virtual host name is the same as before, nothing needs to change. If it is different, go to Configuration > Administrative Tools > GINA/Mac/Linux (Ctrl+Alt+Del), update Configure Access URL on the GINA/Mac Customization page, and run the customization scheduler so that the agents already installed receive the new address.
    4. VPN MFA: On the RADIUS server, add each new node as a RADIUS client with the same shared secret. Under HKEY_LOCAL_MACHINE\SOFTWARE\ZOHO Corp\ADSelfService Plus NPS Extension, change the ServerName value to the virtual host name, and check ServerPortNo and ServerContextPath.
    5. OWA MFA: Check that the ADSelfService Plus MFA Connector resolves the new access URL, and that the Exchange server has the ADSelfService Plus SSL certificate installed.
    6. Reverse proxy: On each node, open server.xml in the conf folder and add the IP address of the reverse proxy server to the internalProxies value of the RemoteIpValve entry. Until this entry is in place, ADSelfService Plus sees every request as coming from the reverse proxy server instead of the actual client, so audit reports, IP-based conditional access rules, and the anti-hacking system do not work correctly.
    7. Integrations: Under Admin > Product Settings > Integration Settings, check the ADManager Plus, ServiceDesk Plus, ServiceDesk Plus Cloud, Splunk, Syslog, Have I Been Pwned, and Log360 integrations. Turning on failover or load balancing in a deployment that already forwards logs to Log360 can disrupt log file recognition from the secondary nodes, so if log forwarding stops after the migration, integrate Log360 with ADSelfService Plus again.
Important:

Decommission the old servers manually after removing them from the deployment, so that they are not left running with access to the external database.

If the database server is also moving

Move the database before you connect the new application servers to it.

Note:

Reconfiguring the database connection requires the deployment to be stopped, so this variation applies to the rebuild approach only. If the database server is also moving, use the rebuild approach rather than the planned failover approach.

  1. Take a full backup of the external database on the old database server.
  2. Transfer the backup file to the new database server and restore the database there.
  3. Ensure that the new database server has the same firewall exceptions as the old one, so that the ADSelfService Plus servers can reach it. For Microsoft SQL, open port 1433 (TCP) for the default instance and port 1434 (UDP) for the SQL Server Browser service. For PostgreSQL, open the port the server listens on, which is 5432 by default.
  4. When you run changeDB.bat to connect the new primary server to the external database, enter the connection details of the new database server instead of the existing ones.
Note:

If you are prompted for a master key during the restoration, contact support@adselfserviceplus.com. The master key can be retrieved only from the ADSelfService Plus application server by the support team.

Validation and confirmation

Complete these checks before you decommission the old servers.

  1. Confirm which server is active on the Failover and Secure Gateway page.
  2. Log in to the admin portal and the end-user portal through the virtual host name or the load balancer URL.
  3. Verify that the license details, self-service policies, authenticator configurations, technicians, and reports are all present and correct.
  4. Confirm that the SSL certificate is valid and that the login page customizations appear on each node.
  5. Perform a test password reset and a test account unlock.
  6. Complete an MFA prompt through the login agent on a user machine.
  7. Complete a VPN login and an OWA login, if those are configured.
  8. Launch an SSO-enabled application from the end-user portal.
  9. Run a scheduled report and confirm that it is generated and delivered.
  10. Review wrapper.log in the logs folder of the installation directory on each node for database connection errors.
Note:

During the cutover, consider increasing the database connection retry period so that a brief database delay does not stop the service. Add or amend the check.dbcrash.delay property in configuration.properties, in the conf folder of the installation directory, and restart the service. The default retry period is 10 seconds.

Rolling back the migration

Roll back before you decommission the old servers, while the original installation directories and the pre-migration database backup are still intact. The procedure differs depending on the approach you followed.

Rolling back the rebuild approach

  1. Stop the ManageEngine ADSelfService Plus service on every new server.
  2. If the external database was modified, restore it from the backup taken in Step 2.
  3. Start the ManageEngine ADSelfService Plus service on the old primary server, and then on each old secondary server.
  4. On the old primary server, open Admin > Enterprise Essentials > Failover and Secure Gateway and confirm the deployment. If the configuration was removed in Step 3, create it again using the values recorded in Step 1.
  5. Confirm that the access URL still points to the original virtual host name or virtual IP, and that end users can reach the portal through it.

Rolling back the planned failover approach

  1. Stop the ManageEngine ADSelfService Plus service on every new server.
  2. If the external database was modified, restore it from the backup taken in Step 2.
  3. Start the ManageEngine ADSelfService Plus service on the old primary server, and then on each old secondary server.
  4. On the old primary server, open Admin > Enterprise Essentials > Failover and Secure Gateway and review the deployment. If the new servers are still listed as secondary servers, remove each of them.
  5. If a new server had already been promoted and the old servers had been removed from the deployment, click Click to Configure and create the configuration again using the values recorded in Step 1.
  6. Confirm that the access URL still points to the original virtual host name or virtual IP, and that end users can reach the portal through it.
Note:

Roll back before you remove the old servers from the deployment if you can. Once a new server has been promoted and the old servers have been removed, the original configuration has to be created again from the values recorded in Step 1 rather than simply restored.

Troubleshooting

Build number is different from the primary node

  • Cause: The ADSelfService Plus build number on a secondary node does not match the primary node.
  • Solution: Update every secondary node to the build number of the primary node using the service pack.

Scheduled jobs are not running. Please restart this server.

  • Cause: The Manage Scheduled Jobs setting was changed and the server has not been restarted.
  • Solution: Restart the ADSelfService Plus server.

Protocol mismatch found. Make sure all the nodes involved in load balancing use the same protocol.

  • Cause: A secondary node is using a different protocol from the primary node.
  • Solution: Enable the same protocol on every node. If HTTPS is enabled on the primary node, enable it on all secondary nodes as well.

Communication issue. Make sure port 7800 is not blocked by the firewall in both the primary and secondary nodes.

  • Cause: There is a network connection issue between the nodes, or the failover port is blocked by a firewall or antivirus software.
  • Solution: Ping each secondary node from the primary node to check connectivity, and confirm that port 7800 is open on every node. If it is unavailable, 7801 and then 7802 are used.

A node is unreachable

  • Cause: The node is stopped, its IP address has changed, or there is a communication error between the primary node and the affected node.
  • Solution: Restart the node and confirm that it can communicate with the primary node without restriction.

Tips

  • Point end users and the login agents at the virtual host name rather than at an individual server name, so that access continues after a failover without any change on the client side.
  • If you restrict admin portal access by IP address, add the virtual IP to the allowed list under Admin > Customize > Login Settings > General, so that the console remains reachable after the virtual IP binds to another server.
  • Update every node in the same maintenance window. Staggered updates leave the nodes on mismatched builds, which disrupts the deployment until the versions match again.
  • Keep the pre-migration database backup and the compressed installation directories until the new deployment has been validated in full.