{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/",
        "slug": "dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/"
        },
        "title": "Test a new RDS session after disabling automatic reconnection",
        "summary": "How should administrators verify that an RDS automatic-reconnection change actually applies?",
        "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:13+00:00",
        "modified_at": "2026-09-08T18:26:31+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 2,
        "word_count": 222,
        "potentially_affected": "Administrators setting automatic reconnection behavior for Remote Desktop clients and session hosts.",
        "dse_recommendation": "Record the current setting and the exact configuration surface to be changed.",
        "primary_source": {
            "name": "Disable Automatic Reconnection in Remote Desktop Service for Windows Server",
            "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/automatic-reconnection-lock-screen",
            "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": "<h2>Source facts</h2>\n<p>RDS can preserve connection information and reconnect a locked session without asking the user to authenticate again; Microsoft says the remote lock screen is not a security boundary. Disabling automatic reconnection at the server prevents clients from using it regardless of their client setting. A changed reconnection setting applies to newly created sessions, while existing sessions retain their original setting. <a href=\"https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/automatic-reconnection-lock-screen\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Decide which session population and connection paths require the change. Review client, session-host, collection, and Group Policy configuration as applicable. Include user continuity expectations and security requirements in the same decision, with an owner for each.</p>\n<h2>DSE recommendation</h2>\n<p>Record the current setting and the exact configuration surface to be changed. Tell pilot users how their next connection should behave during a brief network interruption. Require a newly established session for acceptance rather than relying on a session that predates the change. Keep an approved reconnect procedure available so users can regain access during the exercise.</p>\n<h2>Verification</h2>\n<p>Create a new session, lock it, and perform a controlled interruption. Record reconnection behavior and any authentication interaction. Compare with a pre-existing session only as a separate observation. Verify the intended setting on each relevant host and investigate inconsistent behavior before extending the policy.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/automatic-reconnection-lock-screen\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Disable Automatic Reconnection in Remote Desktop Service for Windows Server</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nRDS can preserve connection information and reconnect a locked session without asking the user to authenticate again; Microsoft says the remote lock screen is not a security boundary. Disabling automatic reconnection at the server prevents clients from using it regardless of their client setting. A changed reconnection setting applies to newly created sessions, while existing sessions retain their original setting. Microsoft Learn.\nApplicability\nDecide which session population and connection paths require the change. Review client, session-host, collection, and Group Policy configuration as applicable. Include user continuity expectations and security requirements in the same decision, with an owner for each.\nDSE recommendation\nRecord the current setting and the exact configuration surface to be changed. Tell pilot users how their next connection should behave during a brief network interruption. Require a newly established session for acceptance rather than relying on a session that predates the change. Keep an approved reconnect procedure available so users can regain access during the exercise.\nVerification\nCreate a new session, lock it, and perform a controlled interruption. Record reconnection behavior and any authentication interaction. Compare with a pre-existing session only as a separate observation. Verify the intended setting on each relevant host and investigate inconsistent behavior before extending the policy.\nOfficial references\nMicrosoft Learn: Disable Automatic Reconnection in Remote Desktop Service for Windows Server. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nRDS can preserve connection information and reconnect a locked session without asking the user to authenticate again; Microsoft says the remote lock screen is not a security boundary. Disabling automatic reconnection at the server prevents clients from using it regardless of their client setting. A changed reconnection setting applies to newly created sessions, while existing sessions retain their original setting. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/automatic-reconnection-lock-screen).\n\n## Applicability\n\nDecide which session population and connection paths require the change. Review client, session-host, collection, and Group Policy configuration as applicable. Include user continuity expectations and security requirements in the same decision, with an owner for each.\n\n## DSE recommendation\n\nRecord the current setting and the exact configuration surface to be changed. Tell pilot users how their next connection should behave during a brief network interruption. Require a newly established session for acceptance rather than relying on a session that predates the change. Keep an approved reconnect procedure available so users can regain access during the exercise.\n\n## Verification\n\nCreate a new session, lock it, and perform a controlled interruption. Record reconnection behavior and any authentication interaction. Compare with a pre-existing session only as a separate observation. Verify the intended setting on each relevant host and investigate inconsistent behavior before extending the policy.\n\n## Official references\n\n[Microsoft Learn: Disable Automatic Reconnection in Remote Desktop Service for Windows Server](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/automatic-reconnection-lock-screen). 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-178-test-a-new-rds-session-after-disabling-automatic-reconnection/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Test a new RDS session after disabling automatic reconnection",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/",
                "headline": "Test a new RDS session after disabling automatic reconnection",
                "description": "How should administrators verify that an RDS automatic-reconnection change actually applies?",
                "abstract": "How should administrators verify that an RDS automatic-reconnection change actually applies?",
                "articleBody": "Source facts\nRDS can preserve connection information and reconnect a locked session without asking the user to authenticate again; Microsoft says the remote lock screen is not a security boundary. Disabling automatic reconnection at the server prevents clients from using it regardless of their client setting. A changed reconnection setting applies to newly created sessions, while existing sessions retain their original setting. Microsoft Learn.\nApplicability\nDecide which session population and connection paths require the change. Review client, session-host, collection, and Group Policy configuration as applicable. Include user continuity expectations and security requirements in the same decision, with an owner for each.\nDSE recommendation\nRecord the current setting and the exact configuration surface to be changed. Tell pilot users how their next connection should behave during a brief network interruption. Require a newly established session for acceptance rather than relying on a session that predates the change. Keep an approved reconnect procedure available so users can regain access during the exercise.\nVerification\nCreate a new session, lock it, and perform a controlled interruption. Record reconnection behavior and any authentication interaction. Compare with a pre-existing session only as a separate observation. Verify the intended setting on each relevant host and investigate inconsistent behavior before extending the policy.\nOfficial references\nMicrosoft Learn: Disable Automatic Reconnection in Remote Desktop Service for Windows Server. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:14:13+00:00",
                "dateModified": "2026-09-08T18:26:31+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-178-test-a-new-rds-session-after-disabling-automatic-reconnection/"
                },
                "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-178-test-a-new-rds-session-after-disabling-automatic-reconnection/#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": "Test a new RDS session after disabling automatic reconnection"
                },
                "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": 222,
                "timeRequired": "PT2M",
                "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": "Disable Automatic Reconnection in Remote Desktop Service for Windows Server",
                    "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/automatic-reconnection-lock-screen"
                }
            }
        ]
    }
}