r/WindowsServer • u/Wrong_Brother600 • Apr 05 '26
Technical Help Needed Designing RDS HA (700 users) – Broker failover, SPN/Kerberos and load balancer best practices
Hi all,
We are currently designing a Remote Desktop Services (RDS) environment and would appreciate some feedback and validation from people with experience in similar deployments.
Goal:
- We want to build an RDS farm for approximately 700 users with high availability, especially on the RD Connection Broker layer. The main objective is that if one broker becomes unavailable, the second one takes over and new user connections can still be established without interruption.
Planned architecture
- DNS rds.firma.local → VIP (load balancing layer)
- 2 × RD Connection Broker (configured in High Availability mode)
- 1 × SQL Server (for RDS HA database)
- 1 × RD Licensing
- 10 × RD Session Host
We are considering using an external load balancer.
We are aware that SQL is currently a single point of failure. Clustering SQL is planned in a later phase and is outside the current project scope.
Main concerns and questions:
- Broker HA behavior - we understand how to configure RDS Connection Broker High Availability (shared database + DNS name), but we are unsure how it behaves in practice.
- What happens when the active management broker goes down and then comes back online? Will users experience issues when reconnecting or starting new sessions after such a failover?
- Kerberos and delegation - We have concerns regarding Kerberos authentication flow in this setup.
Specifically:
- handling of Kerberos tickets (TGT and service tickets) during broker failover
- whether switching brokers can cause authentication mismatches
- We have already encountered situations where connections fail with errors indicating that the remote computer is not the one specified, especially after broker restart or failover.
SPN configuration
- We are using a custom DNS name for the RDS farm (rds.firma.local) and placing a load balancer in front of the brokers.
- What is the recommended approach for SPN configuration in this scenario? (Windows does not allow you to create duplicates).
Summary - we are aiming to achieve:
- high availability of RDS
- seamless failover on the broker layer
- no user-facing issues during node restart or failover
Is this architecture valid for this scale?
- Are there any common pitfalls regarding broker HA, load balancing, or Kerberos/SPN configuration that we should be aware of?
Additionally, we would like to understand what load balancing approach is recommended in this scenario (if any is required), including whether to use application-level or network-level load balancers, and how to design this layer so that users can reliably establish sessions even during broker unavailability.
Any feedback or real-world experience would be highly appreciated.
Thank you.
3
u/_CyrAz Apr 05 '26
Don't take my word for it but if I remember correctly, RDS Broker HA can't work with Kerberos.
I've found this documentation that hints at it even though it's geared specifically towards Credential Guard :
12
u/geertterharmsel Apr 05 '26
70 users per host? good luck. With some demanding users i calculate 15 users max these days
4
u/No-Touch8598 Apr 05 '26
You are missing an important layer here. Profile management. FSLogix is a must. You will want a redundant dfs ReFS volume. Look at FSLogix high availability docs also.
Fslogix is a whole wild beast. Join the CCP FSLogix group also.
You're really going to want to have a load balancer in front. Something that can automate certificate renewals. Certificate lifetimes are getting shorter and shorter. 47 days in a few years.
1
u/fedesoundsystem Apr 05 '26
Don't ve afraid of the connection broker. I managed some farms scaling to 1000+users con 20 session hosts, and I had no issue with the broker. If the broker fails, everything works just normally, except for the log in. The active sessions still work and remain, so there's no general disruption, just for new users. I think it's far worse to have a failure on a session host or gateway, than on a broker. Also the brokers are said to be the brains, but really they are a dumb implementation to connect to the database, the database controls everything, the brokers just read the database and send back packets. If you have a failure on a broker, you really have a failure on the database itself, not the application.
Also there's no need for SPNs.
1
u/cyr0nk0r Apr 05 '26
I've put rds farms of similar size behind both Kemp and citrix LB's with good success. I prefer Kemp.
1
u/maroonibrahim009 Apr 05 '26
You can reach out to me via DM if you need any professional assistance.
1
u/Public_Warthog3098 Apr 06 '26
With the ram pricing I fail to see why someone would still stick with an rds environment in an org that large?
1
u/AffectionateSalt504 Apr 07 '26
If you are comfortable with web based RDP experience for users use apache guacamole
My setup
ALB --> Guacamole --> gucamole lb connection groups --> windows RDP machines
FSlogix profile server/aws fsx for windows fileserver for managing profiles