# Agilicus Connector Windows Cluster

1. [Home](https://www.agilicus.com/)
2. Agilicus Connector Windows Cluster

![cluster](https://www.agilicus.com/www/16e39be0-cluster.svg)Alternate High Availability

---

## Windows Cluster

The Agilicus Connector supports native high-availability. In some environments (notably Windows High Availbility File Servers), it may be desirable to instead use Microsoft's Windows Clustering technology.

[CONTACT](/contact-us/)

## Agilicus Connector Windows Cluster

To enable High Availability in the Agilicus Connector in a Windows environment (e.g. for resilient access to a Share, to remote desktops), configure it within a Windows Failover cluster.

The high level instructions are:

1. configure a windows [failover cluster](https://docs.microsoft.com/en-us/windows-server/failover-clustering/create-failover-cluster) with a shared disk of at least 200MiB.
2. Install the Agilicus Connector into the shared disk on one of the servers. See below for specific instruction.
3. Stop the service on the node and set it to **Disabled**
4. Open the failover cluster manager
5. In your cluster, select Roles-> add new roles
6. Click next, select the “Generic Application” role
7. For the command line, enter F:\\agilicus-agent.exe (the working directory from the install instructions, the shared disk)
8. name the service something unique (e.g. “agilicus-connector”)
9. Add the storage (e.g. F: in our example)
10. Don't register settings
11. Click confirm, finish
12. Verify the Agilicus connector is running

[![](https://www.agilicus.com/www/21421bcc-image-1024x708.png)](https://www.agilicus.com/www/21421bcc-image.png)[![](https://www.agilicus.com/www/b3def478-image-1024x712.png)](https://www.agilicus.com/www/b3def478-image.png)[![](https://www.agilicus.com/www/3c7874f4-image-1024x466.png)](https://www.agilicus.com/www/3c7874f4-image.png)[![](https://www.agilicus.com/www/1aefac83-image-1024x720.png)](https://www.agilicus.com/www/1aefac83-image.png)[![](https://www.agilicus.com/www/f93129f0-image-1024x707.png)](https://www.agilicus.com/www/f93129f0-image.png)[![](https://www.agilicus.com/www/c5012e81-image-1024x605.png)](https://www.agilicus.com/www/c5012e81-image.png)

### Connector Install

On one of the servers in the cluster, we will perform the install as normal, with one modification.

Open a browser (on any machine, does not need to be the windows cluster), sign in to the Agilicus Admin web interface, create a new connector, select the appropriate OS tab, and copy.

On the machine in the server cluster, open an administrative shell, paste the command line. DO NOT PRESS ENTER. Add a command line parameter of '--working-directory <PATH>' where <PATH> is the shared folder (e.g. F:\\Agilicus).

For cmd, the sample command would then look something like below:

```
curl -sSL -o %TEMP%\aa.exe agilicus.com/www/releases/secure-agent/stable/agilicus-agent.exe && %TEMP%\aa.exe client --install --working-directory F:\Agilicus --challenge-id xxxxxxxxxxxx --challenge-code xxxxxx --debug  && del %TEMP%\aa.exe
```

[![](https://www.agilicus.com/www/7b4c8574-image.png)](https://www.agilicus.com/www/7b4c8574-image.png)[![](https://www.agilicus.com/www/531231d0-image.png)](https://www.agilicus.com/www/531231d0-image.png)

### Like Share Warning

If you add a Share, ensure that both paths map to the same resource. E.g. ensure that X:\\foo is the same on both machines if you will export X:\\foo

[![](https://www.agilicus.com/www/1452b7ee-screenshot-from-2021-10-04-22-25-48-1024x483.png)](https://www.agilicus.com/www/1452b7ee-screenshot-from-2021-10-04-22-25-48.png)[![](https://www.agilicus.com/www/5841f1cc-screenshot-from-2021-10-04-22-26-23-1024x480.png)](https://www.agilicus.com/www/5841f1cc-screenshot-from-2021-10-04-22-26-23.png)[![](https://www.agilicus.com/www/80224d15-screenshot-from-2021-10-04-22-29-25-1024x482.png)](https://www.agilicus.com/www/80224d15-screenshot-from-2021-10-04-22-29-25.png)