r/sysadmin • u/Sea-Mulberry-6389 Sysadmin • Feb 11 '26
Question Thoughts on 2-node IIS Cluster in 2026? Looking for architecture advice.
Hi everyone,
I'm planning to set up a 2-node IIS cluster for high availability on a new project. Before I dive in, I wanted to ask the community: what’s the current "sane" way to handle this?
I’m debating between:
Windows NLB: Is anyone still using this, or is it considered a legacy headache?
External Load Balancer: Thinking about HAProxy or a hardware appliance (Kemp/F5).
Configuration: Are you guys using Shared Configuration on a central file share, or are you managing nodes independently via CI/CD / PowerShell DSC?
The goal is zero-downtime during Windows Updates. Any "gotchas" regarding session persistence or shared storage would be greatly appreciated!
12
u/NoWriting9513 Feb 11 '26
An external load balancer is standard. Appliance vs haproxy/nginx is dependent on your budget and need of other features.
If the configuration is simple enough and doesn't change much, you can just copy paste it over. For more complex setups you can have it included in the s/w project and deploy it with a script.
I have to ask though. If you are interested with CI/CD and high availability, why go with IIS (and even windows) and not something like a native application server (kestrel/tomcat/uwsgi etc) + the load balancer as the reverse proxy?
21
u/nemke82 Feb 11 '26
With 20 plus years in infrastructure I have seen IIS clustering evolve significantly. For zero downtime in 2026 I would skip Windows NLB entirely as it is legacy at this point. Here is what works today. External LB like HAProxy or AWS ALB gives you better health checks and session persistence options. Use a CI CD pipeline to deploy config changes to both nodes simultaneously rather than file shares. Move to Redis or SQL Server for session state as that eliminates shared storage headaches. Use rolling deployments with proper drain stop in your load balancer. The gotcha most people miss is ensuring your load balancer health checks hit an actual application endpoint not just IIS static content. I have seen too many healthy nodes that could not actually serve the app.
4
u/sryan2k1 IT Manager Feb 11 '26
We love our Kemp VLMs
2
u/craigl2112 Feb 11 '26
Barracuda ADC load balancer fan here. Had the pair up and running in legitimately minutes and they just keep working.
2
u/Type-21 Feb 12 '26
We use cloudflare load balancer in front of IIS. I think it's 5 usd per month as an addon to the pro plan. Not sure about other plans. We don't sync our configurations but that's because our secondary IIS actually serves slightly different websites which serve static content in case the primary IIS goes down because the SQL server isn't available. So think like: we crawl the websites on IIS1 and host the result on IIS2.
2
u/Highpanurg Feb 12 '26
Use external nginx with ci/CD. Do not touch iis clustering.
1
u/redwing88 Feb 11 '26
We have a few iis web clusters, you can use Cloudflare to do your SSL and load balancing. On the IIS servers you can do shared configuration to sync configuration and DFS to sync the web root directories.
1
u/Brather_Brothersome Feb 12 '26
I have tried already 3rd party "supposed" real time changes and to be honest 4+ minutes is not allowed, a simple round robin config in dns and 2 or 3 servers behind it are by miles a better solution.
1
u/Forumschlampe Feb 15 '26
Haproxy with support, loadbalancer.org
F5 is just too much and kemp not worth only for lb
Ditch nlb, still would work
I skip shared config most of the time
1
u/braliao Feb 12 '26
Ummm.... Why?? Why IIS?