You’ve built the case, validated the hardware, configured the hosts, and connected the storage. Now comes the part everyone’s been waiting for (and dreading): actually moving the virtual machines.

VM migration from VMware to Hyper-V is not a single-click operation. Disk formats differ (VMDK vs. VHDX). Virtual hardware differs (VMware paravirtual drivers vs. Hyper-V synthetic drivers). Guest integration tools differ (VMware Tools vs. Hyper-V Integration Services). But the tooling has improved dramatically, and in 2026, you have more options than ever, including a free, Microsoft-supported tool that performs online migration with minimal downtime.

Not everything needs to be hyper-converged.

There’s a strong narrative in the infrastructure world that three-tier architecture, separate compute, network, and storage tiers, is outdated. That hyper-converged infrastructure (HCI) is the only path forward. That separating your storage from your compute is a legacy pattern.

That narrative is incomplete.

Three-tier architecture remains the right answer for many workloads and many organizations. If you have an existing SAN investment, if your workloads require deterministic storage performance, if you need storage-level replication for disaster recovery, or if your team has deep storage operations expertise, three-tier isn’t just viable, it’s often superior.

This is where the keyboards come out.

Posts 1 through 4 made the business case, dismantled the myths, and confirmed your hardware is ready. Now it’s time to build something. In this fifth post of the Hyper-V Renaissance series, we’re going to take a bare-metal server, or a freshly wiped former VMware host, and turn it into a production-ready Hyper-V node that’s fully validated for cluster membership.

Every step is scripted. Every configuration is documented. If you can’t reproduce it with PowerShell, it doesn’t belong in a production deployment.

The servers sitting in your datacenter right now, the Dell PowerEdges, the HPE ProLiants, and the Lenovo ThinkSystems, were designed to run hypervisors, not a specific hypervisor. Any hypervisor.

This might seem obvious, but it’s worth stating clearly: enterprise server hardware is hypervisor-agnostic. The same CPUs, memory, storage controllers, and network adapters that run ESXi today will run Hyper-V tomorrow. You’re not abandoning hardware investments when you change virtualization platforms; you’re simply loading different software.

“Hyper-V? That’s legacy tech. It can’t compete with VMware. ‘Hyper-V is dead,’ isn’t it?”

I’ve heard this sentiment more times than I can count. In hallway conversations at conferences, in architecture review meetings, in vendor comparison spreadsheets filled with red X marks in the Hyper-V column. For years, this perception has been the default position, sometimes justified, often not.

In this third post of the Hyper-V Renaissance series, we’re going to dismantle this myth systematically. Not with marketing claims, but with verified specifications, feature-by-feature comparisons, and honest assessments of where Hyper-V excels and where it still trails.

The invoice arrived, and the meeting quickly followed.

For nearly two decades, the “cost of virtualization” was a line item we grumbled about but accepted. It was the “VMware Tax,” the price of admission for a stable, feature-rich datacenter. But in the wake of the Broadcom acquisition and the subsequent licensing overhaul, that tax has, for many organizations, turned into a ransom.

This isn’t just about price hikes. It’s about a fundamental shift in how infrastructure is consumed. We are forcibly moving from a world of perpetual licenses and optional support to a world of mandatory subscriptions and bundled software stacks.

Introduction

A Perfect Storm Creates Opportunity

If you’ve been watching the virtualization market over the past eighteen months, you’ve witnessed something extraordinary: a once-stable industry thrown into chaos by a single acquisition. When Broadcom completed its $69 billion purchase of VMware in November 2023, few anticipated how dramatically, and rapidly, the landscape would shift. What followed wasn’t just a pricing adjustment; it was a fundamental restructuring that has sent shockwaves through data centers worldwide.

The Enterprise Reality Check

As we’ve established in previous posts, the post-Broadcom VMware landscape has fundamentally shifted the conversation around enterprise virtualization. No longer can organizations simply renew their vSphere licenses and move on—pricing has increased dramatically, licensing models have changed, and many customers are being pushed toward VMware Cloud Foundation whether they need all its components or not.

But beyond cost considerations lies a critical question: Does Windows Server Failover Clustering with Hyper-V actually deliver the enterprise features that keep VMware entrenched in so many data centers?

(Note: AVS – Azure VMware Solution – is not covered in detail here since it’s essentially outsourcing VMware onto Azure’s hardware. That involves a different calculus: you avoid buying hardware entirely, but you pay cloud rental fees and must fit into Azure’s instance constraints. In this post, we focus on on-premises alternatives where you control the hardware.)

Hardware Considerations: Build Your Cloud on Your Terms

Series Recap: In Part 1 of this series, we examined the total cost of ownership (TCO) implications of different post-VMware paths, comparing capital expenditure vs. subscription models across on-premises Hyper-V, Azure Local (formerly Azure Stack HCI), and Azure VMware Solution (AVS). In Part 2, we dove into licensing – analyzing how VMware vSphere licensing stacks up against Microsoft’s offerings (Windows Server and Azure Local) in 2025, and what those licensing differences mean for choosing a virtualization platform. These earlier posts highlighted that organizations leaving VMware have viable Microsoft-based alternatives that can reduce costs and simplify licensing. Now, in Part 3, we turn to the infrastructure question: What are your hardware options when “rethinking virtualization” away from VMware? Can you reuse your existing servers and storage, or are you forced into buying new, validated hardware nodes? How do Microsoft’s two on-premises solutions – Windows Server Hyper-V with Failover Clustering (WSFC) and Azure Local – compare in terms of hardware requirements? We’ll explore scenarios for customers looking to leave VMware, whether they’re not ready for a hardware refresh or planning a refresh alongside the migration, and we’ll also briefly touch on upcoming VMware Cloud Foundation 9.0 hardware needs.

Introduction

In our previous blog post, we explored why organizations are reconsidering their virtualization strategy post-VMware and highlighted the often-overlooked value of Windows Server Failover Clustering with Hyper-V. Now, in this first follow-up post of the "Beyond the Cloud: The Case for On-Premises Virtualization" series, we dive into the financial side of that decision. Specifically, we will compare the five-year Total Cost of Ownership (TCO) for three possible platforms to run a 100-Virtual Machine (VM) workload: