{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/", "slug": "dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan", "url": "https://update.dsesecurity.com/updates/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/" }, "title": "Include RDS component and template handling in a Site Recovery plan", "summary": "What RDS-specific actions should be included in an Azure Site Recovery recovery plan?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-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:55+00:00", "modified_at": "2026-09-08T18:23:27+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 203, "potentially_affected": "Administrators planning disaster recovery for Remote Desktop Services components.", "dse_recommendation": "Create an ordered recovery worksheet that distinguishes component startup from template handling and host registration.", "primary_source": { "name": "Create your disaster recovery plan", "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-disaster-recovery-plan", "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’s RDS guidance places all component VMs into an Azure Site Recovery recovery plan to automate failover. The plan identifies its source and target, which can be another RDS site or Azure. In the pooled-VM example, a recovered generalized template is shut down because RDS requires a stopped template to create the pooled configuration. The example identifies the template by VM ID when names are shared between sites. Microsoft documentation.

\n

Applicability

\n

Inventory the actual RDS deployment type, component VMs, templates, target site, and dependent services. Review which example actions apply to the deployment before incorporating them into the plan.

\n

DSE recommendation

\n

Create an ordered recovery worksheet that distinguishes component startup from template handling and host registration. Ask the RDS owner to identify the template and workload instances unambiguously. Review script assumptions, pending restarts, and the expected management endpoint at the target site.

\n

Verification

\n

Exercise the plan in the approved recovery-test environment and verify both service access and the intended template state. Test the relevant desktop creation or reconnection workflow after recovery. Record component failures and identity mismatches separately, and reconcile them before calling the RDS recovery plan complete.

\n

Official references

\n

Microsoft Learn: Create your disaster recovery plan. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft’s RDS guidance places all component VMs into an Azure Site Recovery recovery plan to automate failover. The plan identifies its source and target, which can be another RDS site or Azure. In the pooled-VM example, a recovered generalized template is shut down because RDS requires a stopped template to create the pooled configuration. The example identifies the template by VM ID when names are shared between sites. Microsoft documentation.\nApplicability\nInventory the actual RDS deployment type, component VMs, templates, target site, and dependent services. Review which example actions apply to the deployment before incorporating them into the plan.\nDSE recommendation\nCreate an ordered recovery worksheet that distinguishes component startup from template handling and host registration. Ask the RDS owner to identify the template and workload instances unambiguously. Review script assumptions, pending restarts, and the expected management endpoint at the target site.\nVerification\nExercise the plan in the approved recovery-test environment and verify both service access and the intended template state. Test the relevant desktop creation or reconnection workflow after recovery. Record component failures and identity mismatches separately, and reconcile them before calling the RDS recovery plan complete.\nOfficial references\nMicrosoft Learn: Create your disaster recovery plan. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft’s RDS guidance places all component VMs into an Azure Site Recovery recovery plan to automate failover. The plan identifies its source and target, which can be another RDS site or Azure. In the pooled-VM example, a recovered generalized template is shut down because RDS requires a stopped template to create the pooled configuration. The example identifies the template by VM ID when names are shared between sites. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-disaster-recovery-plan).\n\n## Applicability\n\nInventory the actual RDS deployment type, component VMs, templates, target site, and dependent services. Review which example actions apply to the deployment before incorporating them into the plan.\n\n## DSE recommendation\n\nCreate an ordered recovery worksheet that distinguishes component startup from template handling and host registration. Ask the RDS owner to identify the template and workload instances unambiguously. Review script assumptions, pending restarts, and the expected management endpoint at the target site.\n\n## Verification\n\nExercise the plan in the approved recovery-test environment and verify both service access and the intended template state. Test the relevant desktop creation or reconnection workflow after recovery. Record component failures and identity mismatches separately, and reconcile them before calling the RDS recovery plan complete.\n\n## Official references\n\n[Microsoft Learn: Create your disaster recovery plan](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-disaster-recovery-plan). 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-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/", "url": "https://update.dsesecurity.com/updates/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Include RDS component and template handling in a Site Recovery plan", "item": "https://update.dsesecurity.com/updates/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/", "url": "https://update.dsesecurity.com/updates/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/", "headline": "Include RDS component and template handling in a Site Recovery plan", "description": "What RDS-specific actions should be included in an Azure Site Recovery recovery plan?", "abstract": "What RDS-specific actions should be included in an Azure Site Recovery recovery plan?", "articleBody": "Source facts\nMicrosoft’s RDS guidance places all component VMs into an Azure Site Recovery recovery plan to automate failover. The plan identifies its source and target, which can be another RDS site or Azure. In the pooled-VM example, a recovered generalized template is shut down because RDS requires a stopped template to create the pooled configuration. The example identifies the template by VM ID when names are shared between sites. Microsoft documentation.\nApplicability\nInventory the actual RDS deployment type, component VMs, templates, target site, and dependent services. Review which example actions apply to the deployment before incorporating them into the plan.\nDSE recommendation\nCreate an ordered recovery worksheet that distinguishes component startup from template handling and host registration. Ask the RDS owner to identify the template and workload instances unambiguously. Review script assumptions, pending restarts, and the expected management endpoint at the target site.\nVerification\nExercise the plan in the approved recovery-test environment and verify both service access and the intended template state. Test the relevant desktop creation or reconnection workflow after recovery. Record component failures and identity mismatches separately, and reconcile them before calling the RDS recovery plan complete.\nOfficial references\nMicrosoft Learn: Create your disaster recovery plan. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:55+00:00", "dateModified": "2026-09-08T18:23:27+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/" }, "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-136-include-rds-component-and-template-handling-in-a-site-recovery-plan/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Include RDS component and template handling in a Site Recovery plan" }, "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": 203, "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": "Create your disaster recovery plan", "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-disaster-recovery-plan" } } ] } }