← All work
VMware to Hyper-V migration automation
Outcome: Still in progress. The goal is a repeatable, automated migration path that does not depend on Hyper-V having vSphere's API, and that holds up against the permission and double-hop constraints unique to Windows.
The problem
The organization is moving off VMware, and Hyper-V is where it lands. The catch: Hyper-V has nothing like the rich, well-documented vSphere API. Automating it means driving Windows-native surfaces instead, a combination of WinRM, the native Hyper-V cmdlets, the failover clustering stack, and WMI, while working around tight permissions and the double-hop authentication traps that quietly break remote automation.
What I did
- Mapping Hyper-V's real automation surface, stitching together WinRM, the native Hyper-V cmdlets, the failover clustering stack, and WMI to build reliable paths where no REST API exists.
- Working out the permission and delegation model up front, including the double-hop gotchas, so automation runs securely without operators handling credentials by hand.
- Grounding the design in two decades of automating against Windows, so the patterns hold up once the migration runs at fleet scale.