{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/", "slug": "dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles", "url": "https://update.dsesecurity.com/updates/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/" }, "title": "Plan the RD Connection Broker outage before upgrading RDS roles", "summary": "In what order should RDS roles be upgraded, and where is an outage expected?", "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:14:32+00:00", "modified_at": "2026-09-08T18:26:31+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 185, "potentially_affected": "Administrators planning Windows Server upgrades for an RDS deployment.", "dse_recommendation": "Build a role-by-role sequence with an explicit broker outage window.", "primary_source": { "name": "Upgrade Remote Desktop Services deployments", "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/upgrade-to-rds", "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 upgrades RD Connection Broker first. In an active/active deployment, it removes all but one broker, upgrades that broker in place, upgrades the others offline, and adds them back. The deployment is unavailable during the broker upgrade. All brokers must be upgraded; mixed broker versions are unsupported. License servers should be upgraded before Session Host servers. Microsoft documentation.

\n

Applicability

\n

Inventory every RDS role, its release, redundancy configuration, and allowed upgrade path. Review the source’s role-specific limitations and known upgrade issues before scheduling the work.

\n

DSE recommendation

\n

Build a role-by-role sequence with an explicit broker outage window. Have the RDS owner agree on user communication, session handling, recovery checkpoints, and the conditions for advancing to the next role. Preserve the deployment inventory and required recovery material before the first upgrade.

\n

Verification

\n

After the broker stage, confirm that all brokers run the intended release and test the required session workflows. Repeat appropriate checks after the licensing and Session Host stages. Record failures and mixed-version exceptions before declaring the overall deployment upgraded.

\n

Official references

\n

Microsoft Learn: Upgrade Remote Desktop Services deployments. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft upgrades RD Connection Broker first. In an active/active deployment, it removes all but one broker, upgrades that broker in place, upgrades the others offline, and adds them back. The deployment is unavailable during the broker upgrade. All brokers must be upgraded; mixed broker versions are unsupported. License servers should be upgraded before Session Host servers. Microsoft documentation.\nApplicability\nInventory every RDS role, its release, redundancy configuration, and allowed upgrade path. Review the source’s role-specific limitations and known upgrade issues before scheduling the work.\nDSE recommendation\nBuild a role-by-role sequence with an explicit broker outage window. Have the RDS owner agree on user communication, session handling, recovery checkpoints, and the conditions for advancing to the next role. Preserve the deployment inventory and required recovery material before the first upgrade.\nVerification\nAfter the broker stage, confirm that all brokers run the intended release and test the required session workflows. Repeat appropriate checks after the licensing and Session Host stages. Record failures and mixed-version exceptions before declaring the overall deployment upgraded.\nOfficial references\nMicrosoft Learn: Upgrade Remote Desktop Services deployments. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft upgrades RD Connection Broker first. In an active/active deployment, it removes all but one broker, upgrades that broker in place, upgrades the others offline, and adds them back. The deployment is unavailable during the broker upgrade. All brokers must be upgraded; mixed broker versions are unsupported. License servers should be upgraded before Session Host servers. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/upgrade-to-rds).\n\n## Applicability\n\nInventory every RDS role, its release, redundancy configuration, and allowed upgrade path. Review the source’s role-specific limitations and known upgrade issues before scheduling the work.\n\n## DSE recommendation\n\nBuild a role-by-role sequence with an explicit broker outage window. Have the RDS owner agree on user communication, session handling, recovery checkpoints, and the conditions for advancing to the next role. Preserve the deployment inventory and required recovery material before the first upgrade.\n\n## Verification\n\nAfter the broker stage, confirm that all brokers run the intended release and test the required session workflows. Repeat appropriate checks after the licensing and Session Host stages. Record failures and mixed-version exceptions before declaring the overall deployment upgraded.\n\n## Official references\n\n[Microsoft Learn: Upgrade Remote Desktop Services deployments](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/upgrade-to-rds). 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-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/", "url": "https://update.dsesecurity.com/updates/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Plan the RD Connection Broker outage before upgrading RDS roles", "item": "https://update.dsesecurity.com/updates/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/", "url": "https://update.dsesecurity.com/updates/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/", "headline": "Plan the RD Connection Broker outage before upgrading RDS roles", "description": "In what order should RDS roles be upgraded, and where is an outage expected?", "abstract": "In what order should RDS roles be upgraded, and where is an outage expected?", "articleBody": "Source facts\nMicrosoft upgrades RD Connection Broker first. In an active/active deployment, it removes all but one broker, upgrades that broker in place, upgrades the others offline, and adds them back. The deployment is unavailable during the broker upgrade. All brokers must be upgraded; mixed broker versions are unsupported. License servers should be upgraded before Session Host servers. Microsoft documentation.\nApplicability\nInventory every RDS role, its release, redundancy configuration, and allowed upgrade path. Review the source’s role-specific limitations and known upgrade issues before scheduling the work.\nDSE recommendation\nBuild a role-by-role sequence with an explicit broker outage window. Have the RDS owner agree on user communication, session handling, recovery checkpoints, and the conditions for advancing to the next role. Preserve the deployment inventory and required recovery material before the first upgrade.\nVerification\nAfter the broker stage, confirm that all brokers run the intended release and test the required session workflows. Repeat appropriate checks after the licensing and Session Host stages. Record failures and mixed-version exceptions before declaring the overall deployment upgraded.\nOfficial references\nMicrosoft Learn: Upgrade Remote Desktop Services deployments. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:32+00:00", "dateModified": "2026-09-08T18:26:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/" }, "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-159-plan-the-rd-connection-broker-outage-before-upgrading-rds-roles/#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": "Plan the RD Connection Broker outage before upgrading RDS roles" }, "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": 185, "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": "Upgrade Remote Desktop Services deployments", "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/upgrade-to-rds" } } ] } }