{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/", "slug": "dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway", "url": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/" }, "title": "Review load-balancer membership when expanding RD Web and Gateway", "summary": "What should be checked when adding a server to the RD Web and RD Gateway front end?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:15:16+00:00", "modified_at": "2026-09-08T18:23:26+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 210, "potentially_affected": "Administrators adding availability to an existing Remote Desktop Services web front end.", "dse_recommendation": "Document which server will handle new connections and how it enters the existing pool.", "primary_source": { "name": "Add high availability to the RD Web and Gateway web front", "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-rdweb-gateway-ha", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Microsoft describes adding RD Web Access and RD Gateway servers as a way to expand an RDS front-end farm. The added server is prepared with domain membership and remote management enabled. The guidance calls for load balancing the long-lived client connections through RD Gateway. It describes an external Azure load balancer for Azure deployments and a separate hardware or software load balancer elsewhere. Microsoft documentation.

\n

Applicability

\n

Identify the existing deployment, current load balancer, backend pool, service name, and added server. Review the applicable role, certificate, and network settings in the full deployment procedure before changing traffic distribution.

\n

DSE recommendation

\n

Document which server will handle new connections and how it enters the existing pool. Ask the RDS and network owners to approve the traffic transition and a test that includes long-lived sessions. Preserve the original pool membership and specify the condition for removing the added server if validation fails.

\n

Verification

\n

Connect through the published front-end name and confirm which server receives the request. Test new and existing sessions during an approved backend maintenance event. Record the web and gateway results separately, and reconcile any connection failure before accepting the expanded farm.

\n

Official references

\n

Microsoft Learn: Add high availability to the RD Web and Gateway web front. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft describes adding RD Web Access and RD Gateway servers as a way to expand an RDS front-end farm. The added server is prepared with domain membership and remote management enabled. The guidance calls for load balancing the long-lived client connections through RD Gateway. It describes an external Azure load balancer for Azure deployments and a separate hardware or software load balancer elsewhere. Microsoft documentation.\nApplicability\nIdentify the existing deployment, current load balancer, backend pool, service name, and added server. Review the applicable role, certificate, and network settings in the full deployment procedure before changing traffic distribution.\nDSE recommendation\nDocument which server will handle new connections and how it enters the existing pool. Ask the RDS and network owners to approve the traffic transition and a test that includes long-lived sessions. Preserve the original pool membership and specify the condition for removing the added server if validation fails.\nVerification\nConnect through the published front-end name and confirm which server receives the request. Test new and existing sessions during an approved backend maintenance event. Record the web and gateway results separately, and reconcile any connection failure before accepting the expanded farm.\nOfficial references\nMicrosoft Learn: Add high availability to the RD Web and Gateway web front. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft describes adding RD Web Access and RD Gateway servers as a way to expand an RDS front-end farm. The added server is prepared with domain membership and remote management enabled. The guidance calls for load balancing the long-lived client connections through RD Gateway. It describes an external Azure load balancer for Azure deployments and a separate hardware or software load balancer elsewhere. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-rdweb-gateway-ha).\n\n## Applicability\n\nIdentify the existing deployment, current load balancer, backend pool, service name, and added server. Review the applicable role, certificate, and network settings in the full deployment procedure before changing traffic distribution.\n\n## DSE recommendation\n\nDocument which server will handle new connections and how it enters the existing pool. Ask the RDS and network owners to approve the traffic transition and a test that includes long-lived sessions. Preserve the original pool membership and specify the condition for removing the added server if validation fails.\n\n## Verification\n\nConnect through the published front-end name and confirm which server receives the request. Test new and existing sessions during an approved backend maintenance event. Record the web and gateway results separately, and reconcile any connection failure before accepting the expanded farm.\n\n## Official references\n\n[Microsoft Learn: Add high availability to the RD Web and Gateway web front](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-rdweb-gateway-ha). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/", "url": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Review load-balancer membership when expanding RD Web and Gateway", "item": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/", "url": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/", "headline": "Review load-balancer membership when expanding RD Web and Gateway", "description": "What should be checked when adding a server to the RD Web and RD Gateway front end?", "abstract": "What should be checked when adding a server to the RD Web and RD Gateway front end?", "articleBody": "Source facts\nMicrosoft describes adding RD Web Access and RD Gateway servers as a way to expand an RDS front-end farm. The added server is prepared with domain membership and remote management enabled. The guidance calls for load balancing the long-lived client connections through RD Gateway. It describes an external Azure load balancer for Azure deployments and a separate hardware or software load balancer elsewhere. Microsoft documentation.\nApplicability\nIdentify the existing deployment, current load balancer, backend pool, service name, and added server. Review the applicable role, certificate, and network settings in the full deployment procedure before changing traffic distribution.\nDSE recommendation\nDocument which server will handle new connections and how it enters the existing pool. Ask the RDS and network owners to approve the traffic transition and a test that includes long-lived sessions. Preserve the original pool membership and specify the condition for removing the added server if validation fails.\nVerification\nConnect through the published front-end name and confirm which server receives the request. Test new and existing sessions during an approved backend maintenance event. Record the web and gateway results separately, and reconcile any connection failure before accepting the expanded farm.\nOfficial references\nMicrosoft Learn: Add high availability to the RD Web and Gateway web front. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:15:16+00:00", "dateModified": "2026-09-08T18:23:26+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-115-review-load-balancer-membership-when-expanding-rd-web-and-gateway/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Review load-balancer membership when expanding RD Web and Gateway" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 210, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Add high availability to the RD Web and Gateway web front", "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-rdweb-gateway-ha" } } ] } }