{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/", "slug": "dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point", "url": "https://update.dsesecurity.com/updates/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/" }, "title": "Treat the cluster functional-level update as a rolling-upgrade decision point", "summary": "What must be verified before finalizing a cluster OS rolling upgrade?", "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:02+00:00", "modified_at": "2026-09-08T18:23:27+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 198, "potentially_affected": "Administrators upgrading supported Windows Server Hyper-V or Scale-Out File Server clusters.", "dse_recommendation": "Record an acceptance checkpoint before raising the functional level.", "primary_source": { "name": "Upgrade the OS of a Windows Server failover cluster by performing a cluster OS rolling upgrade", "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/Cluster-Operating-System-Rolling-Upgrade", "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 rolling-upgrade procedure advances a cluster by one Windows Server version at a time. The process is reversible until all nodes run the new release and the cluster functional level is updated. Before upgrading, the source calls for checking that storage, compute, and network capacity remain sufficient with a node removed. Microsoft documentation.

\n

Applicability

\n

Check the supported workload, version path, VM configuration, storage design, and management tooling. Review the source’s exclusions and special instructions rather than applying this procedure to every cluster workload.

\n

DSE recommendation

\n

Record an acceptance checkpoint before raising the functional level. Have workload owners review service tests, node versions, remaining capacity, and unresolved incidents from the mixed-version phase. Keep the decision to finalize separate from the completion of the last node installation.

\n

Verification

\n

Verify every node’s release and cluster state, then test representative workload moves and client transactions. Reconcile failures and backup readiness before the owner authorizes finalization. Preserve the before-and-after functional level and the accepted workload results so the irreversible transition has a clear evidence record.

\n

Official references

\n

Microsoft Learn: Upgrade the OS of a Windows Server failover cluster by performing a cluster OS rolling upgrade. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft’s rolling-upgrade procedure advances a cluster by one Windows Server version at a time. The process is reversible until all nodes run the new release and the cluster functional level is updated. Before upgrading, the source calls for checking that storage, compute, and network capacity remain sufficient with a node removed. Microsoft documentation.\nApplicability\nCheck the supported workload, version path, VM configuration, storage design, and management tooling. Review the source’s exclusions and special instructions rather than applying this procedure to every cluster workload.\nDSE recommendation\nRecord an acceptance checkpoint before raising the functional level. Have workload owners review service tests, node versions, remaining capacity, and unresolved incidents from the mixed-version phase. Keep the decision to finalize separate from the completion of the last node installation.\nVerification\nVerify every node’s release and cluster state, then test representative workload moves and client transactions. Reconcile failures and backup readiness before the owner authorizes finalization. Preserve the before-and-after functional level and the accepted workload results so the irreversible transition has a clear evidence record.\nOfficial references\nMicrosoft Learn: Upgrade the OS of a Windows Server failover cluster by performing a cluster OS rolling upgrade. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft’s rolling-upgrade procedure advances a cluster by one Windows Server version at a time. The process is reversible until all nodes run the new release and the cluster functional level is updated. Before upgrading, the source calls for checking that storage, compute, and network capacity remain sufficient with a node removed. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/failover-clustering/Cluster-Operating-System-Rolling-Upgrade).\n\n## Applicability\n\nCheck the supported workload, version path, VM configuration, storage design, and management tooling. Review the source’s exclusions and special instructions rather than applying this procedure to every cluster workload.\n\n## DSE recommendation\n\nRecord an acceptance checkpoint before raising the functional level. Have workload owners review service tests, node versions, remaining capacity, and unresolved incidents from the mixed-version phase. Keep the decision to finalize separate from the completion of the last node installation.\n\n## Verification\n\nVerify every node’s release and cluster state, then test representative workload moves and client transactions. Reconcile failures and backup readiness before the owner authorizes finalization. Preserve the before-and-after functional level and the accepted workload results so the irreversible transition has a clear evidence record.\n\n## Official references\n\n[Microsoft Learn: Upgrade the OS of a Windows Server failover cluster by performing a cluster OS rolling upgrade](https://learn.microsoft.com/en-us/windows-server/failover-clustering/Cluster-Operating-System-Rolling-Upgrade). 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-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/", "url": "https://update.dsesecurity.com/updates/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Treat the cluster functional-level update as a rolling-upgrade decision point", "item": "https://update.dsesecurity.com/updates/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/", "url": "https://update.dsesecurity.com/updates/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/", "headline": "Treat the cluster functional-level update as a rolling-upgrade decision point", "description": "What must be verified before finalizing a cluster OS rolling upgrade?", "abstract": "What must be verified before finalizing a cluster OS rolling upgrade?", "articleBody": "Source facts\nMicrosoft’s rolling-upgrade procedure advances a cluster by one Windows Server version at a time. The process is reversible until all nodes run the new release and the cluster functional level is updated. Before upgrading, the source calls for checking that storage, compute, and network capacity remain sufficient with a node removed. Microsoft documentation.\nApplicability\nCheck the supported workload, version path, VM configuration, storage design, and management tooling. Review the source’s exclusions and special instructions rather than applying this procedure to every cluster workload.\nDSE recommendation\nRecord an acceptance checkpoint before raising the functional level. Have workload owners review service tests, node versions, remaining capacity, and unresolved incidents from the mixed-version phase. Keep the decision to finalize separate from the completion of the last node installation.\nVerification\nVerify every node’s release and cluster state, then test representative workload moves and client transactions. Reconcile failures and backup readiness before the owner authorizes finalization. Preserve the before-and-after functional level and the accepted workload results so the irreversible transition has a clear evidence record.\nOfficial references\nMicrosoft Learn: Upgrade the OS of a Windows Server failover cluster by performing a cluster OS rolling upgrade. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:15:02+00:00", "dateModified": "2026-09-08T18:23:27+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/" }, "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-129-treat-the-cluster-functional-level-update-as-a-rolling-upgrade-decision-point/#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": "Treat the cluster functional-level update as a rolling-upgrade decision point" }, "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": 198, "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 the OS of a Windows Server failover cluster by performing a cluster OS rolling upgrade", "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/Cluster-Operating-System-Rolling-Upgrade" } } ] } }