{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/", "slug": "dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change", "url": "https://update.dsesecurity.com/updates/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/" }, "title": "Update Network ATC intents when cluster adapters change", "summary": "How should Network ATC intent membership be maintained after a hardware change?", "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:16:36+00:00", "modified_at": "2026-09-08T18:17:14+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 213, "potentially_affected": "Use this review for a cluster already managed by Network ATC.", "dse_recommendation": "Maintain an intent-to-adapter worksheet and compare it with the physical change request.", "primary_source": { "name": "Manage Network ATC", "url": "https://learn.microsoft.com/en-us/windows-server/networking/network-atc/manage-network-atc", "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 documents ongoing Network ATC administration through PowerShell after deployment. A newly added cluster node receives the same intent and must meet the documented requirements. When physical adapters change, Update-NetIntentAdapter updates the adapters assigned to the relevant intents. Network ATC also permits environment-specific management and storage VLAN values instead of its defaults. Microsoft documentation.

\n

Applicability

\n

Use this review for a cluster already managed by Network ATC. Identify the current intent, node set, adapter mapping, and selected VLANs before changing hardware or membership. Keep initial deployment readiness as a separate prerequisite review.

\n

DSE recommendation

\n

Maintain an intent-to-adapter worksheet and compare it with the physical change request. Have the network and server owners approve the intended mapping on every affected node. Include management access and workload connectivity in the test plan. Record the existing intent configuration and a supported recovery route before using the applicable management operation.

\n

Verification

\n

After the approved update, inspect intent state and adapter membership across the cluster. Test the management and workload paths that depend on the changed adapters. Check a newly added node against the existing nodes rather than reviewing it in isolation. Record inconsistent mappings, failed intents, or unexpected VLAN behavior before proceeding with another hardware change.

\n

Official references

\n

Microsoft Learn: Manage Network ATC. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft documents ongoing Network ATC administration through PowerShell after deployment. A newly added cluster node receives the same intent and must meet the documented requirements. When physical adapters change, Update-NetIntentAdapter updates the adapters assigned to the relevant intents. Network ATC also permits environment-specific management and storage VLAN values instead of its defaults. Microsoft documentation.\nApplicability\nUse this review for a cluster already managed by Network ATC. Identify the current intent, node set, adapter mapping, and selected VLANs before changing hardware or membership. Keep initial deployment readiness as a separate prerequisite review.\nDSE recommendation\nMaintain an intent-to-adapter worksheet and compare it with the physical change request. Have the network and server owners approve the intended mapping on every affected node. Include management access and workload connectivity in the test plan. Record the existing intent configuration and a supported recovery route before using the applicable management operation.\nVerification\nAfter the approved update, inspect intent state and adapter membership across the cluster. Test the management and workload paths that depend on the changed adapters. Check a newly added node against the existing nodes rather than reviewing it in isolation. Record inconsistent mappings, failed intents, or unexpected VLAN behavior before proceeding with another hardware change.\nOfficial references\nMicrosoft Learn: Manage Network ATC. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft documents ongoing Network ATC administration through PowerShell after deployment. A newly added cluster node receives the same intent and must meet the documented requirements. When physical adapters change, Update-NetIntentAdapter updates the adapters assigned to the relevant intents. Network ATC also permits environment-specific management and storage VLAN values instead of its defaults. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/networking/network-atc/manage-network-atc).\n\n## Applicability\n\nUse this review for a cluster already managed by Network ATC. Identify the current intent, node set, adapter mapping, and selected VLANs before changing hardware or membership. Keep initial deployment readiness as a separate prerequisite review.\n\n## DSE recommendation\n\nMaintain an intent-to-adapter worksheet and compare it with the physical change request. Have the network and server owners approve the intended mapping on every affected node. Include management access and workload connectivity in the test plan. Record the existing intent configuration and a supported recovery route before using the applicable management operation.\n\n## Verification\n\nAfter the approved update, inspect intent state and adapter membership across the cluster. Test the management and workload paths that depend on the changed adapters. Check a newly added node against the existing nodes rather than reviewing it in isolation. Record inconsistent mappings, failed intents, or unexpected VLAN behavior before proceeding with another hardware change.\n\n## Official references\n\n[Microsoft Learn: Manage Network ATC](https://learn.microsoft.com/en-us/windows-server/networking/network-atc/manage-network-atc). 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-035-update-network-atc-intents-when-cluster-adapters-change/", "url": "https://update.dsesecurity.com/updates/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Update Network ATC intents when cluster adapters change", "item": "https://update.dsesecurity.com/updates/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/", "url": "https://update.dsesecurity.com/updates/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/", "headline": "Update Network ATC intents when cluster adapters change", "description": "How should Network ATC intent membership be maintained after a hardware change?", "abstract": "How should Network ATC intent membership be maintained after a hardware change?", "articleBody": "Source facts\nMicrosoft documents ongoing Network ATC administration through PowerShell after deployment. A newly added cluster node receives the same intent and must meet the documented requirements. When physical adapters change, Update-NetIntentAdapter updates the adapters assigned to the relevant intents. Network ATC also permits environment-specific management and storage VLAN values instead of its defaults. Microsoft documentation.\nApplicability\nUse this review for a cluster already managed by Network ATC. Identify the current intent, node set, adapter mapping, and selected VLANs before changing hardware or membership. Keep initial deployment readiness as a separate prerequisite review.\nDSE recommendation\nMaintain an intent-to-adapter worksheet and compare it with the physical change request. Have the network and server owners approve the intended mapping on every affected node. Include management access and workload connectivity in the test plan. Record the existing intent configuration and a supported recovery route before using the applicable management operation.\nVerification\nAfter the approved update, inspect intent state and adapter membership across the cluster. Test the management and workload paths that depend on the changed adapters. Check a newly added node against the existing nodes rather than reviewing it in isolation. Record inconsistent mappings, failed intents, or unexpected VLAN behavior before proceeding with another hardware change.\nOfficial references\nMicrosoft Learn: Manage Network ATC. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:36+00:00", "dateModified": "2026-09-08T18:17:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-035-update-network-atc-intents-when-cluster-adapters-change/" }, "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-035-update-network-atc-intents-when-cluster-adapters-change/#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": "Update Network ATC intents when cluster adapters change" }, "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": 213, "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": "Manage Network ATC", "url": "https://learn.microsoft.com/en-us/windows-server/networking/network-atc/manage-network-atc" } } ] } }