Previously on our epic saga: we unlocked Virtualization Mode, traversed the lore of two modes, and upgraded our management platform to vMode. With these three pieces in hand, we can begin onboarding machines to their newfound home.
Preparing for the journey
Before onboarding hosts into vMode, we should take a moment to make sure our machines are set up for a smooth and predictable experience.
Whether you’re onboarding standalone HyperV hosts or multi-node clusters, vMode ensures your machines are ready for their quest to management by validating a small set of prerequisites up front. These quick readiness checks help vMode apply configuration consistently across hosts and clusters, so you get reliable outcomes from day one, without surprises midway through onboarding.
Supported host operating systems
vMode currently follows an N‑1 host support model, supporting Windows Server 2025 and Windows Server 2022 for host machines.
We focused on these versions so we could backport key capabilities like Network ATC and deliver the most reliable onboarding experience possible. As vMode continues to evolve, support for additional Windows Server versions is something we plan to expand over time.
Note: These OS requirements apply only to host machines and cluster nodes being onboarded into vMode. Guest virtual machines running on those hosts are not subject to these requirements.
Domain requirements
To ensure secure communication and consistent configuration, all hosts and cluster nodes being onboarded must be domain-joined and reside in the same Active Directory domain as the vMode instance.
At this time, vMode does not support onboarding for:
- workgroup machines
- cross‑domain scenarios
- untrusted domains
These constraints allow vMode to reliably authenticate, configure, and manage hosts as a unified fabric. We know your party’s environments vary, and your feedback will help guide how we evolve these capabilities over time.
Temporary firewall access for onboarding
During onboarding (and removal), vMode needs temporary access to copy the files required to install its lightweight management agent. For this reason, SMB inbound traffic (TCP 445) must be allowed on each host or cluster node during these operations.
You can enable this with the following PowerShell command:
Enable-NetFirewallRule -DisplayName 'File and Printer Sharing (SMB-In)'This access is used solely to install or uninstall the vMode agent, which enables stateful, scalable, and secure management of your virtualization fabric.
Note: Once the agent has been installed or removed, you may disable this firewall rule again if desired.
Ready to hit the road
We know how hard it’s been to get here. Getting hosts and clusters stood up the “right” way is rarely clean or straightforward. It usually means long nights, tribal knowledge, brittle scripts, and the constant worry that one node isn’t quite configured like the others.
vMode is built to take that burden off your plate by ensuring your machines are ready to be managed before we start their onboarding quest. With clear requirements and validation that takes seconds, you can proceed through the wizard without worry.
Choosing a path: host profiles
Managing hosts and clusters at scale means understanding what role each system plays and ensuring the right tools are available for that role. In vMode, we organize onboarded systems using host profiles.
A host profile is a primary classification assigned during onboarding. It determines:
- where a system appears in the navigation,
- which tools and workflows are available, and
- which operations can be performed from that view.
This role-based approach helps you focus on what matters most for each type of system, without clutter or unnecessary options.
Today, vMode recognizes three host profiles:
- Compute (Hyper‑V hosts)
The Compute view focuses on virtualization workloads and day‑to‑day host operations. From here, you can manage VM lifecycle operations such as live migration and Hyper‑V Replica, apply host updates, configure firewall settings, and review event logs. All from a centralized, consistent experience. - Storage
The Storage profile is designed for systems that provide storage for virtual machines, including SAN, NAS, or hyperconverged infrastructure using Storage Spaces Direct. While this profile view is not available yet, it is planned for a future release and will provide storage‑specific management and visibility once enabled. - Networking
The Networking profile is intended for managing network configuration and services that support virtualization workloads, including Network ATC intents, ATC intent template management, and Software Defined Networking (SDN) components. Although the dedicated Networking profile view is not available today, vMode already supports configuring Network ATC during onboarding, and additional networking capabilities and workflows are planned for a future release.
Note: The Storage and Networking profile view are still in progress and planned for the general availability release of vMode.
By organizing hosts around clear, role-based profiles, vMode makes it easier to manage complex environments consistently. While ensuring each system is governed and operated according to its intended purpose. Selecting your machine’s classification profile is essential for completing their quest.
Facing the onboarding wizard
Now that your environment is ready, let’s take on the resource onboarding wizard in vMode. This guided flow validates your setup, applies configuration consistently, and gives you visibility into every step along the way.
Create a resource group
Start by creating a resource group to organize your hosts and clusters. Resource groups help you manage related systems together and keep your environment easy to navigate as it grows.
Add a resource
Next, add a resource to the resource group. vMode automatically runs validation checks in the background, so you don’t have to manually verify prerequisites before moving forward. This is also where you select your profile.
If the host is part of a cluster, vMode detects this automatically and adds the entire cluster on your behalf—saving time and eliminating manual discovery steps.
Coming soon: You’ll be able to create clusters directly from this wizard, including creating new host VMs and clustering them as part of the same flow.
Configure networking
Configure Network ATC and create the necessary network intents to automatically configure, validate, and maintain the required networking for hosts or clusters.
Coming soon: Expanded networking experiences are in active development to provide deeper visibility and control as vMode approaches general availability.
Configure storage
In the Storage step, you select how storage is configured for your hosts or clusters. This step ensures your virtualization workloads have the right storage foundation before onboarding completes.
Coming soon: Expanded storage experiences, including support for SAN‑based storage and file shares.
Configure compute settings
In the Compute step, you can fine-tune host configuration, including:
- removing non‑essential Windows Server features,
- enabling Enhanced Session Mode,
- configuring up to four concurrent live migrations, and
- setting a custom virtual machine storage path.
These options help ensure your hosts are optimized for performance, scalability, and reduced operational overhead.
Review and onboard
Before onboarding begins, you’ll review all selected settings to ensure everything looks correct. Once confirmed, vMode kicks off the onboarding process.
Track progress in real time
The workflow status page shows onboarding progress in real time:
- broken down per step
- visible per node
If issues arise, this detailed view makes it easier to troubleshoot and pinpoint exactly where attention is needed.
Start managing your resources
Once onboarding completes, your newly onboarded hosts or clusters appear in the left navigation, ready for day-to-day management.
Quest completed! For now…
Your quest “Resource onboarding using vMode” has been completed! You made sure your machines were ready for their journey by following the onboard prerequisites, chose your machine’s profile (or “class”) carefully, and defeated the onboarding wizard.
Along the way, vMode ensured your experience was straightforward and that the onboarding experience was consistent, easing worries about misconfigured nodes or roles you’d forgotten to install. We make sure nodes are consistent if you’re onboarding a cluster and machine configuration doesn’t necessarily require a complex automation script. Think of vMode as your game onboarding master, invested in the success of your characters machines.
Thank you for following along as we continue to build vMode. Your feedback plays a critical role in shaping what comes next, and we’d love to hear what workflows, capabilities, or improvements matter most to you as we move toward general availability.
Thank you for stopping by,
Theo (Just Theo)
Microsoft