Agilicus Connector Windows Cluster
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. To do this, you will install the Connector twice, with identical command-line parameters (same GUID etc) on both machines in the cluster. The Windows Failover will ensure exactly 1 is running.
The high level instructions are:
- configure a windows failover cluster
- install the Agilicus Connector on each server in the failover cluster using an identical command line. Use the ‘subsequent’ option in the Agilicus Admin dialog to indicate the 2nd one is part of a cluster.
- stop the service on both nodes and set it to Manual
- open the failover cluster manager
- In your cluster, select Roles-> add new roles
- click next, select the “Generic Service” role
- Select the “Agilicus Connector Connector”
- name the service something unique (e.g. “agilicus-share-server”)
- Don’t add any storage or registry settings
- click confirm, finish
- verify it comes up running
- configure connector as normal with access to resources you desire.
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
Related Configuration
Return to Product Configuration
- Agilicus AnyX Frequently Asked Questions
- VNC Desktop
- Agilicus Connector – Container/Docker
- Agilicus Connector – NanoPI R5S
- Agilicus AnyX Product Updates
- Agilicus Connector – Microsoft Windows
- Sign-In Errors
- Time Synchronisation
- Locked-Down Networks Certificate Revocation
- Signup: Firewall Configuration
- Geo-Location-Based Access Control
- Resources – Overview, Concepts
- Connect to VTScada – Adding a Web Application
- Web Application Security
- Administrative Users
- Define Application: Proxy
- Authorisation rules
- Real VNC & Raspberry Pi
- Connector Install: Raspberry Pi
- Kubernetes Connector Install
- Linux, FreeBSD, Embedded Connector Install
- Connector Install: Ubiquiti EdgeRouter X
- Audit Destinations
- Agilicus Connector Install: MikroTik RouterOS
- Connector Install: Netgate SG-1100 pfSense
- Identity Group Mapping
- Billing
- Auto-Create Users From Specific Domain With Google Workplace
- Organisation
- Authentication Audit
- Authentication Issuer – Custom Identity
- Sign Up
- Microsoft ClickOnce
- Groups
- Agilicus Connector Windows Cluster
- Launchers
- Forwarding
- Usage Metrics
- Service Accounts
- Identity & Authentication Methods
- Content Security Policy
- Users
- Sign-In Theming
- Sign in With Apple
- Azure Active Directory
- Sign in With Microsoft
- Agilicus Launcher (Desktop)
- Agilicus-Connector
- Zero-Trust SSH Access
- Theory of Operation: CNAME + DOMAIN
- Zero-Trust Desktop Access
- Command Line API Access
- Applications
- Permissions
- Profile
- Multi-Factor Authentication
- Authentication Rules
- Application Request Access
- OpenWRT Connector Install
- Synology Connector Install
- Authentication Clients
- Shares
- Services
- Resource Permissions
- Resource Groups
- Legacy Active Directory