Windows Admin Center: Virtualization Mode (vMode) is now generally available and ready for your production environments! Released as part of Windows Admin Center version 2611, a single vMode instance can manage up to 1,000 Hyper-V hosts and 25,000 VMs. This release also adds Azure Arc onboarding, built-in backup and restore, and certificate management with Active Directory Certificate Services (AD CS).
Administration Mode (aMode) gets resilience and security fixes, plus a redesigned Azure registration experience that asks only for the permissions each task needs. Both modes now share one installer, so you can get started in one step. Just pick your mode during setup.
A huge thank you to our customers, partners, and fans—your feedback has shaped Windows Admin Center and vMode all the way to this GA milestone. Keep it coming! You can share your thoughts on this release through our official feedback portal.
What is Virtualization Mode?
Many organizations are rethinking their virtualization platform right now. Licensing changes and renewal uncertainty have pushed teams to look for alternatives, and not every workload is ready to move to the cloud. If you’re moving to Hyper-V, or already running it, vMode gives you the centralized management you’d expect from a modern virtualization platform, at no additional cost.
Today, you probably manage Hyper-V one piece at a time: Hyper-V Manager for one host, Failover Cluster Manager for another, and PowerShell scripts to fill the gaps. vMode brings all of this into one place. From a single gateway, your team can onboard Hyper-V hosts and clusters, apply consistent networking and storage configuration, and manage compute, storage, and networking as one environment, with role-based access so everyone can work together.
Because vMode keeps a central record of your environment, it can also protect itself with built-in backup and restore, certificate management through your existing PKI, and Azure Arc onboarding at scale. Administration Mode is still the right tool for hands-on work with individual servers. vMode is for running your virtualization environment as a whole.
We recommend reading more about the architectural differences between the modes before reading the rest of this article. Afterwards, check out the vMode documentation for more information.
What’s new in Windows Admin Center 2611
Virtualization mode
Navigation hierarchy
In vMode, everything you manage lives in a single navigation hierarchy on the left side of the screen. Instead of connecting to servers one at a time, you browse your whole environment at once: resource groups, plus the hosts, clusters, VMs, and storage they contain. Switch between the Compute, Storage, and Network views to focus on the part of your fabric you’re working on.
Resource groups are the top-level containers in the hierarchy, and they work like folders. Organize them however makes sense for your team, whether that’s by site, environment, or workload. Every resource belongs to a resource group, resource groups don’t nest, and each host belongs to exactly one resource group. Because access is assigned through role-based access control, each user only sees the resources they’ve been given access to.
Compute view
The Compute view brings your Hyper-V hosts, clusters, and VMs together, organized by resource group so you can browse your environment without switching between individual server connections. Select a host to open its management tools, or select a VM to see its details and current state. From here, you can get on with everyday tasks like creating VMs, starting them, and live migrating them between standalone hosts—all within the same experience you use to manage the rest of your virtualization environment.
Storage view
The Storage view brings your storage resources together, organized by resource group so you can find the storage your VMs depend on without browsing through individual hosts. Whether you’re using Windows Scale-Out File Servers, non-Windows SMB file servers, or SAN storage, you can manage your onboarded storage here and see which compute systems are linked to each resource. It’s a way to explore your environment from the storage side, with those connections in view as you move between your storage and compute resources.
Networking view
The Networking view is where you create and manage reusable Network ATC intent templates for your cluster networking. Define the traffic types and networking settings once, then select a template and map it to physical adapters in the Add resource wizard. This helps you apply consistent configurations across deployments without starting from scratch each time.
As your networking needs evolve, you can refine these templates for future deployments. In this release, template changes apply only to future deployments that use the template. Intents already configured on your hosts or clusters remain unchanged.
Use the Network ATC PowerShell cmdlets to manage deployed intents. For guidance on updating intent settings, changing assigned network adapters, or removing intents, see Manage Network ATC.
Add resource
Add resource is how you bring your infrastructure under vMode management. Instead of piecing together onboarding with separate tools and scripts, a single guided workflow adds your hosts to a resource group, applies consistent networking, storage, and compute configuration, and installs the vMode agent that keeps everything connected to the gateway.
Adding compute resources
Using the Compute profile, you can bring three kinds of Hyper-V infrastructure into vMode:
- Standalone hosts: Individual Hyper-V hosts that aren’t part of a failover cluster.
- Existing clusters: Enter the cluster’s fully qualified domain name (FQDN), and vMode automatically detects and onboards every member node.
- New clusters: Create a failover cluster from two or more standalone hosts as part of onboarding.
To get started, select the ellipsis (...) next to a resource group and choose Add Resource. The wizard then walks you through each part of the configuration before anything is applied:
- Getting started: Select the Compute profile, validate each host or cluster FQDN, and turn on Clustered to create a new cluster.
- Clustering (clusters only): Confirm existing cluster settings or name a new cluster and choose DHCP or static IPs.
- Networking: Bind Network ATC intent templates to physical adapters for clusters. Network ATC configuration is skipped for hosts that will remain standalone. To learn more about the changes we’ve made to this page since preview, read our dedicated blog post.
- Storage: Pick a storage option or use storage already connected to your hosts.
- Compute: Set host options like enhanced session mode, concurrent live migrations, and the default VM path.
- Review: Confirm your selections and select Submit.
Before you begin, review the prerequisites for machines managed by Windows Admin Center vMode.
Adding storage resources
Using the Storage profile, or the Storage step when you add compute resources, you can bring the storage your VMs run on into vMode. Like everything else in vMode, each storage resource belongs to a resource group. Today, vMode supports three types of storage:
- Windows Scale-Out File Servers (SOFS): Enter the SOFS share path, and vMode validates the share, installs the vMode agent on the file server, and can configure share permissions and SMB delegation for you so live migration works. If delegation can’t be configured automatically, such as when Active Directory permissions are missing, vMode tells you so you can set it up manually.
- Non-Windows SMB file servers: Enter the share’s UNC path (for example, \\storage01\share1), and vMode confirms the share exists and is accessible before registering it. Permission and delegation options aren’t available for non-Windows file servers. If you enter the share path while adding compute resources, vMode registers the storage for you automatically.
- SAN storage (Fibre Channel and iSCSI): Register a SAN by its hostname. When you add hosts or clusters connected to a SAN, the Storage step scans shared LUNs and shows which are ready to use, which vMode can configure automatically, and which need manual configuration. Network ATC Storage intents are optional for SAN deployments.
After onboarding, you can manage your storage from the Storage view, where you’ll also see which compute systems are linked to each storage resource.
Tracking deployment status
Onboarding can take a while, especially when hosts need to reboot, so vMode gives you a couple of ways to keep tabs on progress and get things back on track if something goes wrong.
Workflow status pane: Select the workflow status icon in the header bar to open the workflow status pane from anywhere in vMode. It lists your workflows, like Add resource, along with their current status and the progress of each step, including any required reboots. You can filter the list by status to quickly find workflows that need your attention, and open a workflow to see details and error information for any step that failed.
Deployment status: As soon as deployment begins, the machine you’re adding appears in the navigation hierarchy. If you select it before it’s ready, you’ll see its deployment status, similar to what’s shown in the workflow status pane. That way, even if you don’t make it back to the workflow for a while, you’ll know exactly where to look to check progress or address any issues.
Resuming and retrying workflows: Transient issues like lost connectivity, a gateway service restart, or configuration changes can interrupt a workflow. If a workflow is paused by a service disruption, you can resume it from where it left off. If a step fails, you can review the error, fix the underlying cause, and retry that step if rerunning it won’t disrupt anything else in the workflow.
Authentication and Role-based Access Control (RBAC)
vMode is built for teams, so access is checked in layers. Users sign in to the gateway with their Active Directory account through Windows authentication, and vMode RBAC then decides what each person can do and where. You can assign roles at the gateway root, a resource group, a cluster, or a host, and assignments flow down to everything beneath them. Today vMode includes three built-in roles:
- Global Administrator: Full control of the gateway, including access, resource group structure, certificates, and backup and restore.
- Fabric Manager: Day-to-day fabric management in their assigned scope, like adding hosts and clusters, managing templates, and onboarding to Azure Arc.
- Reader: View-only access to resources in their assigned scope.
Keep in mind that right after installation, only the account that installed vMode has access, so be sure to add other users and assign roles before rolling it out to your team. vMode roles also don’t replace Windows permissions on your hosts, so users still need administrative rights on the hosts they manage. Learn more about authentication and role-based access control in vMode.
Backup and restore
Because vMode keeps a central record of your environment, a failed gateway shouldn't mean rebuilding everything from scratch. Built-in backup and restore creates an encrypted, password-protected copy of the vMode management database, which holds your virtualization inventory, cluster metadata, gateway configuration, RBAC settings, templates, and operational state. Backup and restore is available to Global Administrators, and you can save backups to a local folder or a UNC share.
If you lose data or need to rebuild your gateway, you can restore from a backup and pick up where you left off. Before anything changes, vMode validates the backup’s password, checks it for unauthorized modifications, and confirms it’s compatible with your gateway. Restore recovers the management database only. It doesn’t roll back your servers, clusters, VMs, storage, or networks, and vMode picks up their current state as agents reconnect. Store your backup password separately from the backup file. If the password is lost, the backup can’t be restored.
To get started, go to Overview and select Backup & Restore. Learn more about backup and restoration in vMode.
Global search
When you’re managing hundreds of hosts and thousands of VMs, browsing the navigation tree to find one machine gets old fast. Global search lets you find any resource in your vMode environment from a single search bar, without needing to remember which resource group, cluster, or host it lives on.
Search spans the resources in your navigation hierarchy, including resource groups, hosts, clusters, and VMs. As you type, suggestions appear, and you can narrow results by object type. Select a result to jump straight to it and get to work, whether you’re checking on a VM during an incident or confirming that newly deployed machines landed on the right hosts.
Global search supports three search types, so you can be as broad or as targeted as you need:
| Search type | Syntax | Example |
| Basic | Type partial names or use * as a wildcard. Matching is case-insensitive. | uster0 finds Cluster01 and Cluster02; web-0* finds web-01 and web-02. |
| Hierarchical | Start with the full resource group path, use / between levels, and place : before the search term. Wildcards aren’t supported in the path. | /ResourceGroup1/Cluster1: web searches hosts and VMs under Cluster1. Leave the term blank to see everything under that location. |
| Object | Put the object type in square brackets followed by a colon, or select an object type icon. | [Virtual machine]: WS2025; [Network intent]: Intent1. Broad types include [Compute], [Storage], and [Network]. |
Keep in mind that search respects role-based access control, so you only see results for resources you have access to. Deleted resources and attached objects, such as virtual hard disks, aren’t included in search results.
Azure Arc onboarding
With vMode, you can connect the Hyper-V hosts you already manage to Azure Arc in bulk, right from the gateway. Azure Arc represents your on-premises servers as resources in Azure, so you can manage them with Azure services. Select multiple machines, apply one set of Azure settings (subscription, resource group, region, cloud environment, and optional tags), and vMode installs the Azure Connected Machine agent and connects each machine for you.
Getting connected starts in the Me control, where you register your vMode gateway with Azure and sign in to your Azure account—no trip to gateway settings needed. The redesigned registration flow requests only the permissions needed for the current user and registration task, without requiring tenant-level administrator consent. That means you can get started without coordinating with a highly privileged tenant administrator, while Azure role-based access control (Azure RBAC) lets administrators restrict who can perform Azure operations.
Each machine gets its own onboarding workflow, so a failure on one machine doesn’t stop the others. Track each machine’s progress in the workflow status pane as it downloads and installs the agent, connects to Azure Arc, and refreshes its status. Once onboarding completes, machines show as Connected on the Azure Arc page, along with their Azure resource group.
Once you’re signed in, select your navigation root, then Azure Arc to start onboarding your machines. In this release, machines connect through a public endpoint, either directly or through a proxy server. Learn more about onboarding to Azure Arc in vMode.
Using Administration Mode? You’ll find its redesigned Azure registration experience in gateway settings under Register. See Configuring Azure integration for more on connecting aMode to Azure.
Certificate lifecycle management
vMode uses certificates to secure communication between the gateway and managed hosts. Self-signed certificates are great for testing, since they don’t require an existing certificate authority or PKI. For production, you can now manage vMode certificates through Active Directory Certificate Services (AD CS), using centralized issuance, certificate templates, and automated renewal to align with your existing PKI policies and reduce the risk of outages from expired certificates.
To get started, go to your gateway settings and select the Certificates tab. To learn more, see our documentation.
Keeping vMode up to date
Staying current is how you get the latest features, reliability fixes, and security updates in vMode. The good news: updating vMode is a two-part story where you only have to do one part. You update the gateway, and the gateway takes care of the agents.
Updating the gateway
To update your gateway, run the latest Windows Admin Center installer on your vMode gateway machine and complete the upgrade wizard. When prompted, reuse your existing PostgreSQL credentials. The installer upgrades your gateway in place and keeps your existing database, inventory, and configuration, including resource groups, managed hosts and clusters, network intent templates, and access assignments.
Before you upgrade, we recommend taking a backup of your vMode environment (or a checkpoint, if your gateway runs in a VM) so you have a known-good restore point. After the upgrade completes, sign back in and confirm your gateway version by navigating to Settings > About.
Updating the agents
There’s no separate step for agents. Updating your gateway automatically triggers an update of the vMode agents on all hosts and clusters managed through vMode. The agent installer is delivered with the gateway installer, so you never need to download or deploy agent updates to each host yourself.
After the gateway upgrade, managed hosts reconnect and their agents upgrade or report healthy. You can track progress with the agent health indicators in the navigation hierarchy and in the workflow status pane. If an agent shows as disconnected after updating, check out our documentation for troubleshooting guidance.
Hyper-V Replication
You can now set up and manage Hyper-V Replica right in vMode, alongside your hosts, clusters, and VMs. Configure Replica Brokers and enable VM replication over HTTP or HTTPS, then choose which disks to replicate, how often replication runs, how many recovery points to keep, and how to handle the initial copy.
Once replication is configured, open VM details to check its health and statistics. Need to make a change? You can pause or resume replication, update replication or failover-network settings, or remove and re-enable replication. VM details also gives you access to checkpoint management and lets you move clustered VMs between nodes.
When it’s time to test your recovery plan, you can run a test failover on an isolated copy without interrupting the original VM. If you need to move or recover a workload, use planned or unplanned failover, then reverse replication to support failback. You can also set up extended replication to keep an additional copy at a third site.
Want to see which replicated workloads need attention across your environment? Replication Monitor, entering private preview alongside vMode GA, brings replication health and test-failover information for primary and extended replication into one view across your hosts and clusters. Dashboard cards and filters help you narrow in on workloads that need attention. To try it, sign up for the private preview with your email address, and we’ll send you the steps to enable Replication Monitor.
Check out our documentation to learn more about Hyper-V Replica.
Update on the VM Conversion tool
VM Conversion is coming to vMode in private preview, bringing VMware ESXi-to-Hyper-V migration into the same experience you use to manage your virtualization environment. This new appliance-based implementation replaces the earlier preview extension, with prechecks to help you prepare, data synchronization ahead of cutover to help limit downtime, and batch operations for moving multiple VMs. You can follow each VM’s progress in the workflow status pane, then keep managing the workload in vMode once it’s running on Hyper-V. For a closer look at how it works and how to express interest in the private preview through Windows Server TAP, read our companion blog.
New SDK — now with React support
The Windows Admin Center SDK has been updated to version 6.0.0! This new version features two major updates: commands for upgrading existing Windows Admin Center extensions to Angular 20 as well as commands for creating and testing React-based Windows Admin Center extensions. The documentation for preparing your development environment and creating a tool extension has been updated to reflect these changes.
Partner Ecosystem
The Windows Admin Center management experience wouldn’t be complete without our development partners, who make managing your hardware, storage, and firmware through Windows Admin Center a streamlined experience. Since the last generally available release of Windows Admin Center, three partners have made updates to their extensions.
- The Dell OpenManage Integration extension has been upgraded to version 3.8.0—this version contains the following improvements:
- Support for aMode and vMode: Dell OpenManage Integration now supports Windows Admin Center 2611 GA in both Administration Mode and Virtualization Mode. In vMode, you can manage and monitor infrastructure, perform lifecycle management operations, and use virtualization management experiences from a unified interface.
- 18G PowerEdge server support: Added support for the R9815 and R9825 platforms.
- Security improvements: Addressed security vulnerabilities and improved stability and compliance posture.
- Reliability improvements: Improved error handling and validation across multiple workflows for a better user experience and greater operational stability.
- The Dell APEX Cloud Platform extension has been upgraded to version 3.0.7—this version contains the following improvements:
- Security hardening
- Fix for a reported certificate expiry issue
- The Dell PowerPath extension has been upgraded to version 3.0.0—this version contains the following improvements:
- The Lenovo XClarity Integrator extension has been upgraded to version 5.2.1—this version contains the following improvements:
- New system support: Added support for FX650 V4 and FX630 V4 systems.
- Best Recipe support: Added support for ThinkAgile MX Best Recipe 2605.
- Software support: Added support for Lenovo XClarityEssentials OneCLI 5.4.0 and Windows Admin Center 2511.
- Cluster consistency fix: Fixed a failure to compute cluster consistency when all nodes are not using a Host Bus Adapter.
- Best Recipe compliance fix: Fixed an issue where Best Recipe compliance results ignored capacity disks.
- Security improvements: Addressed CVE-2026-65949, CVE-2025-4947, CVE-2025-5025, and LEN-223105.
- The Everpure FlashArray extension has been upgraded to version 1.1.180—this version contains the following improvements:
- A new array must be registered by a gateway administrator before anyone can connect to it. A new Registered Arrays page provides this.
- Arrays with self-signed certificates require a one-time administrator approval.
- Unregistering an array signs out everyone currently using it.
- Existing connections are migrated automatically on upgrade and continue to work without administrator action.
Known issues
Visit our documentation to learn about the current known issues with this version. Additionally, check out our documentation for additional troubleshooting information.
Download today!
Thanks for reading along! Virtualization mode going GA is a big moment for us, and we can’t wait for you to try it. We hope you love this new version and everything it brings.
Download now!
As always, thanks for your ongoing support, adoption, and feedback. Your contributions through user feedback continue to be vital and valuable to us, helping us prioritize our investments.
vMode GA is a big step, but it’s not the finish line. Windows Admin Center keeps growing as both a tool and a platform, and we’re beyond thrilled to have you along for the ride. Stay tuned—there’s plenty more to come!
Thank you,
Windows Admin Center Team (@servermgmt)