AuthAnvil Clustering - How can I create a .CLU file?

With the release of 2FA v5.5, SSO v4.5 and Password Server v2.6, we made clustering and fault tolerance a whole lot easier. AuthAnvil now includes a PowerShell script that will interrogate an existing AuthAnvil server deployment to determine what product is installed and ask you for a destination name to generate a CLU file (*.clu).


You can create the .CLU file following these steps.

  1. Open an elevated PowerShell window (Run as Administrator).
  2. Navigate to "C:\Program Files\Scorpion Software\AuthAnvil\AuthAnvilTools".
  3. Run the Export-AuthAnvilRedundancyInfo tool.
    PS C:\Program Files\Scorpion Software\AuthAnvil\AuthAnvilTools> .\Export-AuthAnvilRedundancyInfo.ps1
  4. You will then be prompted to select the products you want to add to the Cluster.
    Select [A] for all [2] for 2FA/SSO or [P] for the Password Server.
  5. Name the CLU file.
    Example: Cluster.
  6. Select Enter.
  7. You should now see the cluster file completed and located in the same folder as the tool was run.
  8. Check C:\Program Files\Scorpion Software\AuthAnvil\AuthAnvilTools for <filename>.CLU.


Copy the CLU file to the server(s) you wish to add to the cluster.

Note: The additional AuthAnvil server(s) must have the system requirements setup including a valid third party issued SSL certificate. 


This CLU file will work in the installer for all three core AuthAnvil products, allowing you to add a new node to an AuthAnvil cluster in just a few clicks. You will notice the option to use a CLU file for a cluster in the base menu when the installer starts.


Note: Installation of 2FA v5.5 will configure SSO v4.5 by default if you selected SSO during the CLU file creation.


Note: The primary server will need to be configured to allow Remote connections from the secondary server. 

- This article may be helpful
- You may also need enable the SQL browser service. This article may be helpful



If you have any questions or need some help, we would be happy to assist. Open a case at or send an email to


Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section