Windows Admin Center: Virtualization Mode (vMode) is now generally available with Windows Admin Center version 2611, bringing centralized management of Hyper-V hosts, clusters, virtual machines, storage, and networking into a unified experience. In this blog, we're taking a closer look at the networking improvements that help you bring those resources under a single pane of glass.
If you're new to vMode, the Add resource wizard is where you onboard Hyper-V hosts and existing clusters or create a new cluster from standalone hosts. For clustered compute resources, its networking step uses Network ATC to configure networking based on intents that specify the traffic types and settings to apply to your adapters. Network intent templates provide reusable configurations for these intents.
Based on the feedback from preview testing, we have focused on taking the guesswork out of networking. With earlier Network ATC validation, clearer error messages, and improvements to cluster creation, you can catch configuration issues sooner and understand how to resolve them as you configure networking in the Add resource workflow.
Simpler onboarding for standalone hosts
If you're adding Hyper-V hosts that will remain standalone, you no longer need to configure Network ATC intents as part of the Add Resource workflow. You can continue onboarding without applying the intent requirements used for clusters. If you're creating a new cluster from those hosts, the cluster networking workflow still applies.
Preparing networking before cluster creation
When you create a new cluster, vMode creates and verifies the configured network intents on the selected hosts before clustering begins. If existing standalone intents are detected, the wizard prompts you to remove them before continuing.
Removing an intent doesn’t undo the networking it configured. Objects such as virtual switches remain in place and may conflict with the new intents if the configuration changes. Review the existing configuration and address any conflicts before proceeding.
Earlier validation and clearer next steps
We’ve added Network ATC pre-validation to help catch networking configuration issues before intent provisioning begins. Errors and warnings explain what needs attention so you can make changes and revalidate before continuing.
If network intent verification fails during deployment, the workflow can also surface recent Network ATC error events from cluster nodes, when available. This gives you more context for troubleshooting without first having to collect logs from each node.
Clearer intent requirements
For cluster onboarding, your configuration needs exactly one intent that includes Management and at least one that includes Compute. A single intent can satisfy both requirements, and existing healthy, symmetric cluster intents count toward them.
We continue to recommend Storage intents for Storage Spaces Direct (S2D) and Ethernet-based storage such as SMB. They’re optional for external SAN storage, so you can onboard those deployments without adding a Storage intent.
Building on public preview
These changes build on the networking capabilities added in the last public preview release. You can review existing intent status, refresh the Networking page in Add Resource to retrieve host-side changes without restarting the wizard, and specify Storage VLANs when creating network intent templates. Network ATC Event Logs are also included in vMode Agent logs for deeper troubleshooting.
Get started
Whether you're onboarding standalone hosts or preparing a cluster, vMode simplifies the process with clearer networking requirements, earlier validation, and more actionable troubleshooting information.
Network changes can interrupt connectivity, so review their impact before applying them. For the full workflow and prerequisites, see Add compute resources in Windows Admin Center Virtualization Mode. If you're new to vMode, start with What is Windows Admin Center Virtualization Mode?.
Thank you to everyone who shared feedback during public preview. Your experiences helped shape these improvements, and we look forward to hearing your feedback as you start using the generally available version of Virtualization Mode!