{"id":1131,"date":"2026-11-13T22:40:32","date_gmt":"2026-11-13T22:40:32","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/?p=1131"},"modified":"2026-11-13T22:40:32","modified_gmt":"2026-11-13T22:40:32","slug":"windows-update-policy-production-rds-host","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/","title":{"rendered":"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">An always-on RDS host is the worst possible candidate for the default Windows Update behaviour. Servers that run 24\/7 never hit &#8220;active hours&#8221;, so the update engine can start servicing at any hour, reboot on its own schedule, and \u2014 with Delivery Optimization on by default in some configurations \u2014 decide that the VPS is a good peer to serve patch content from. This guide configures WUfB policy for a production Remote Desktop Session Host: deferral rings, a maintenance window, Delivery Optimization limits, and the pre-flight checks that stop a patch Tuesday from becoming an outage.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why the Default Settings Break an RDS Host<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Three defaults are hostile to a session host. Active hours assume the machine is off overnight; a session host is not. Automatic restarts do not check for active sessions the way administrators assume. And Delivery Optimization treats every Server 2019+ machine as a potential peer, which on a metered link consumes egress and makes the host serve megabytes to other machines on the provider network. These are desktop assumptions applied to server hardware.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">WUfB policy lives in the registry under <em>HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\WindowsUpdate<\/em>. For a single host a script is easier to review and roll back than a GPO, and the keys are identical either way.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Deferral Rings: Quality vs Feature Updates<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Split the two update classes. Quality updates (monthly cumulative patches) should land within days; feature updates on a session host should be deferred for months and tested on a clone first. The policy keys that matter:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$wu = 'HKLM:\\SOFTWARE\\Policies\\Microsoft\\Windows\\WindowsUpdate'\nNew-Item -Path $wu -Force | Out-Null\n\n# Quality (security\/cumulative) updates: defer 3 days\nNew-ItemProperty $wu -Name 'DeferQualityUpdates' -Value 1 -PropertyType DWord -Force\nNew-ItemProperty $wu -Name 'DeferQualityUpdatesPeriodInDays' -Value 3 -PropertyType DWord -Force\n\n# Feature updates: defer 120 days, pin the current release\nNew-ItemProperty $wu -Name 'DeferFeatureUpdates' -Value 1 -PropertyType DWord -Force\nNew-ItemProperty $wu -Name 'DeferFeatureUpdatesPeriodInDays' -Value 120 -PropertyType DWord -Force\nNew-ItemProperty $wu -Name 'BranchReadinessLevel' -Value 16 -PropertyType DWord -Force\n\n# Do not auto-restart while anyone is logged on\nNew-ItemProperty $wu -Name 'NoAutoRebootWithLoggedOnUsers' -Value 1 -PropertyType DWord -Force<\/code><\/pre>\n\n\n\n\n\n<h2 class=\"wp-block-heading\">Restricting Restarts to a Maintenance Window<\/h2>\n\n\n<p class=\"wp-block-paragraph\">A deferral ring controls when patches are downloaded and installed. It does not control when the machine reboots \u2014 and on an RDS host, the reboot is the visible outage. Combine an explicit install window, a forced restart window outside business hours, and a scheduled task that drains the host first.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Install window: Tue 03:00-04:00 ; restart window: Tue 04:00-05:00 (UTC)\n$ux = \"$wu\\UX\"\nNew-Item -Path $ux -Force | Out-Null\nNew-ItemProperty $ux -Name 'SetAutoRestartDeadline' -Value 1 -PropertyType DWord -Force\nNew-ItemProperty $ux -Name 'AutoRestartDeadlinePeriodInDays' -Value 2 -PropertyType DWord -Force<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then add the session-aware part no policy key provides: warn every session at 03:30, block new logons at 04:00, restart after a grace period.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Two lines are enough for the drain step: <em>msg * \/TIME:1800<\/em> with a warning text, then <em>change logon \/disable<\/em> followed by a short wait and <em>Restart-Computer -Force<\/em>. Put them in a scheduled task that runs only when no interactive administrator is logged on, or you will be rebooting out from under yourself during maintenance.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Delivery Optimization: Stop the Egress Bill and the Peer Role<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Delivery Optimization exists so many machines on one LAN can share downloads. On a single VPS the benefit is minimal and the cost is real: peer traffic leaves the box, and on metered plans that is billable egress. Set DO to HTTP-only with a bandwidth ceiling so an update cannot saturate the link that also carries RDP:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$do = 'HKLM:\\SOFTWARE\\Policies\\Microsoft\\Windows\\DeliveryOptimization'\nNew-Item -Path $do -Force | Out-Null\n\n# 0 = HTTP only, no peer-to-peer\nNew-ItemProperty $do -Name 'DODownloadMode' -Value 0 -PropertyType DWord -Force\n\n# Cap background download bandwidth; 1% = 10 Mbps of a 1 Gbps link\nNew-ItemProperty $do -Name 'DOPercentageMaxBackgroundBandwidth' -Value 10 -PropertyType DWord -Force\nNew-ItemProperty $do -Name 'DOPercentageMaxForegroundBandwidth' -Value 30 -PropertyType DWord -Force\nNew-ItemProperty $do -Name 'DOMaxCacheAge' -Value 259200 -PropertyType DWord -Force<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Disk Space: The Failure Mode Nobody Plans For<\/h2>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cleanup after updates:<\/strong> <em>DISM \/Online \/Cleanup-Image \/StartComponentCleanup \/ResetBase<\/em> monthly \u2014 reclaims superseded components but makes installed updates non-removable.<\/li>\n<li><strong>Cleanup before updates:<\/strong> clear <em>C:\\Windows\\SoftwareDistribution\\Download<\/em> after stopping <em>wuauserv<\/em>, not while it is running.<\/li>\n<li><strong>Watch the alert:<\/strong> a PerfMon\/disk alert at 12% free space gives you days of warning.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Pre-Flight Checklist the Night Before Patch Tuesday<\/h2>\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Free space on C:<\/strong> Get-Volume C \u2014 pass if above 20% used.<\/li>\n<li><strong>Pending reboot already?<\/strong> Test-Path &#8216;HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WindowsUpdate\\Auto Update\\RebootRequired&#8217; \u2014 pass if False.<\/li>\n<li><strong>Snapshot exists:<\/strong> a provider or Hyper-V snapshot younger than 24 hours.<\/li>\n<li><strong>Sessions at 04:00:<\/strong> qwinsta or Get-RDUserSession \u2014 every user known and notified.<\/li>\n<li><strong>Backup verified:<\/strong> last successful backup job under 24 hours old.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If any item fails, delay the ring by a week. Plenty of hosts reboot on schedule; few are patched and stable on the same night. The <a href=\"https:\/\/windows-vps.org\/\">Windows VPS hosting plans and specifications<\/a> page lists disk sizes that leave room for update staging without squeezing the database files.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verifying the Policy Actually Applied<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Registry values can be overridden by an existing GPO or the update client&#8217;s own state. Reboot once and verify through the update API rather than trusting regedit:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Effective policy as seen by the update client\nGet-ItemProperty 'HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WindowsUpdate\\Auto Update\\RebootRequired' -ErrorAction SilentlyContinue\n\n# When the next scan and install are scheduled\nGet-ScheduledTask -TaskPath '\\Microsoft\\Windows\\WindowsUpdate\\*' |\n  Get-ScheduledTaskInfo | Format-Table TaskName,NextRunTime,LastRunTime\n\n# Recent update events\nGet-WinEvent -LogName 'Microsoft-Windows-WindowsUpdateClient\/Operational' -MaxEvents 30 |\n  Select-Object TimeCreated,Id,Message<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the next run times in that folder do not match your intended window, a policy is being overridden \u2014 find the GPO before changing anything else. The restart deadline is the one setting that will bite you: if it is set to 0, the host can reboot as soon as installation finishes, window or no window. You can cross-check the scheduled-task and WUfB policy paths against the <a href=\"https:\/\/windows-vps.org\/\">Windows Server administration guides<\/a> we keep alongside the hosting comparison.\n","protected":false},"excerpt":{"rendered":"<p>An always-on RDS host is the worst possible candidate for the default Windows Update behaviour. Servers that run 24\/7 never hit &#8220;active hours&#8221;, so the update engine can start servicing at any hour, reboot on its own schedule, and \u2014 with Delivery Optimization on by default in some configurations \u2014 decide that the VPS is &#8230; <a title=\"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows\" class=\"read-more\" href=\"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/\" aria-label=\"Read more about Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":0,"footnotes":""},"categories":[9,5],"tags":[],"class_list":["post-1131","post","type-post","status-publish","format-standard","hentry","category-hosting-workflows","category-tutorials-guides"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows - Windows VPS Blog<\/title>\n<meta name=\"description\" content=\"An always-on RDS host is the worst possible candidate for the default Windows Update behaviour. Servers that run 24\/7 never hit &quot;active hours&quot;, so the\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows\" \/>\n<meta property=\"og:description\" content=\"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows\" \/>\n<meta property=\"og:url\" content=\"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/\" \/>\n<meta property=\"og:site_name\" content=\"Windows VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-13T22:40:32+00:00\" \/>\n<meta name=\"author\" content=\"windows-vps\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@myxiechengxuan\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"windows-vps\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/\",\"url\":\"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/\",\"name\":\"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows - Windows VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\"},\"datePublished\":\"2026-11-13T22:40:32+00:00\",\"author\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\"},\"description\":\"An always-on RDS host is the worst possible candidate for the default Windows Update behaviour. Servers that run 24\/7 never hit \\\"active hours\\\", so the\",\"breadcrumb\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/windows-vps.org\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\",\"url\":\"https:\/\/windows-vps.org\/blog\/\",\"name\":\"Windows VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/windows-vps.org\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\",\"name\":\"windows-vps\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"caption\":\"windows-vps\"},\"sameAs\":[\"https:\/\/windows-vps.org\/blog\",\"https:\/\/x.com\/myxiechengxuan\"],\"url\":\"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows - Windows VPS Blog","description":"An always-on RDS host is the worst possible candidate for the default Windows Update behaviour. Servers that run 24\/7 never hit \"active hours\", so the","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/","og_locale":"en_US","og_type":"article","og_title":"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows","og_description":"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows","og_url":"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/","og_site_name":"Windows VPS Blog","article_published_time":"2026-11-13T22:40:32+00:00","author":"windows-vps","twitter_card":"summary_large_image","twitter_creator":"@myxiechengxuan","twitter_misc":{"Written by":"windows-vps","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/","url":"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/","name":"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows - Windows VPS Blog","isPartOf":{"@id":"https:\/\/windows-vps.org\/blog\/#website"},"datePublished":"2026-11-13T22:40:32+00:00","author":{"@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58"},"description":"An always-on RDS host is the worst possible candidate for the default Windows Update behaviour. Servers that run 24\/7 never hit \"active hours\", so the","breadcrumb":{"@id":"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/windows-vps.org\/blog\/windows-update-policy-production-rds-host\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/windows-vps.org\/blog\/"},{"@type":"ListItem","position":2,"name":"Windows Update Policy on a Production RDS Host: Delivery Optimization and Maintenance Windows"}]},{"@type":"WebSite","@id":"https:\/\/windows-vps.org\/blog\/#website","url":"https:\/\/windows-vps.org\/blog\/","name":"Windows VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/windows-vps.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58","name":"windows-vps","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","caption":"windows-vps"},"sameAs":["https:\/\/windows-vps.org\/blog","https:\/\/x.com\/myxiechengxuan"],"url":"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/"}]}},"_links":{"self":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1131","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/comments?post=1131"}],"version-history":[{"count":1,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1131\/revisions"}],"predecessor-version":[{"id":1132,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1131\/revisions\/1132"}],"wp:attachment":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/media?parent=1131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/categories?post=1131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/tags?post=1131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}