Before you proceed, make sure that the previous assumptions are met.

  1. Primary node: Install MOVEit Automation.
    • Select the account type you would like to use: GMSA/Windows/Virtual Account with SQL Authentication or Windows Authentication (GMSA/Windows Accounts only).
    • SQL Authentication is only permitted when using Virtual Account type. If using SQL Authentication, enter the user you would like the installer to create, for example, moveitautomation.
    • Enter the details of the remote SQL Server and the database name you would like to use, for example, micstats.
    • If using SQL Authentication, enter the user you would like the installer to create, for example moveitautomation.
  2. Secondary node: Install MOVEit Automation.
    • Select the account type you would like to use: GMSA/Windows/Virtual Account with SQL Authentication or Windows Authentication (GMSA/Windows Accounts only). If using GMSA, ensure the same GMSA is used on both nodes.
    • If using Windows Authentication with a Windows Account, ensure the same Active Directory account is used, or the Windows Account exists on the SQL Server and both MOVEit Automation nodes with the same password.
    • Enter the details of the remote SQL Server and the database name you would like to use, for example, micstats.
    • If using SQL Authentication, enter a temporary user that the installer will create, for example, moveitautomation_del .
  3. Both nodes: Stop the MOVEit Automation Service.
  4. Both nodes: Open the registry editor and navigate to HKEY_LOCAL_MACHINE\Software\Standard Networks\MOVEit Central\Resil. Enter SuppressDbRep=1. Create a new DWORD named SuppressDbRep with a value of 1.
  5. Both nodes: Synchronize the KeyMat registry keys:
    • Export the KeyMat registry key from the primary node and import it into the secondary node.
    • Export the KeyMat registry key from the secondary node and import it into the primary node.
  6. Both nodes: Create a new local user named automationfailover and add it to the MOVEit Admins group. Or use an Active Directory user. Below is a sample PowerShell script to create a local user:
    $pass = ConvertTo-SecureString “<enter password here>” -AsPlainText -Force
New-LocalUser “automationfailover” -Password $pass -PasswordNeverExpires
Add-LocalGroupMember -Group “MOVEit Admin” -Member “automationfailover”
  7. Primary node: Open the Config Utility > Failover Tab and configure the following information:
    • This Node - Startup Role: Primary
    • This Node - Node Number: 1
    • This Node - Nodes to ping: (Optional: usually the IP address of trusted router, leave blank if unsure)
    • Other Node - Hostname or IP: [IP Address of Node #2]
    • Other Node - MOVEit Admin user: automationfailover
    • Other Node - Password: [automationfailover's Password]
    • Click Apply.
  8. Secondary node: Open the Config Utility > Failover Tab and configure the following information:
    • This Node - Startup Role: Secondary
    • This Node - Node Number: 2
    • This Node - Nodes to ping: (Optional: usually the IP address of trusted router, leave blank if unsure)
    • Other Node - Hostname or IP: [IP Address of Node #1]
    • Other Node - MOVEit Admin user: automationfailover
    • Other Node - Password: [automationfailover's Password]
    • Click Apply.
  9. Secondary node: Update the database details:
    • Open the Config Utility > Database Tab.
    • Update the database name and credentials (if applicable) to match the primary node.
    • Click Apply.
  10. Primary node: Start the MOVEit Automation service. From a command line, you may use the command net start moveitautomation.
  11. Secondary node: Start the MOVEit Automation service. From a command line, you may use the command net start moveitautomation.
  12. Primary node: Open MOVEit Automation Web Admin and log on. Check the status on the System > Failover dialog. This should show that the Primary node is the primary MOVEit Automation node, and the Secondary node is the secondary MOVEit Automation node.
  13. Primary node: Use the MOVEit Automation Web Admin Commands > Reset Tamper Detection menu item to reset tamper detection for the failover system.
  14. SQL Server:
    • Once you have confirmed everything is operational, delete the Database created in step 2 above.
    • If using SQL authentication, delete the SQL user created in step 2 above.
    • Reset the moveit_installer user password.
  15. Both nodes: If the SQL Server is running in Mixed Mode.
    • Open the Config Utility and enter the new password