We're planning to migrate our infrastructure from VMware to Hyper-V in the next few months. Currently, we have no domain controllers for Server 2025 and just one 2025 file server, which is functioning smoothly. Our setup consists of a straightforward three-node cluster with shared storage; all the hardware is identical and fully licensed. We intend to use Veeam for the migration but are considering either removing VMware tools beforehand or scripting it post-migration. Moving everything to the cloud isn't an option for us right now. While we have most of our migration plan in place, I'm reaching out for advice, especially from those who have already gone through this process. Here are my questions: Did you choose Server 2022 or 2025? If you went with 2025, did you face any particular issues or gotchas? Also, did you do a core or full installation (we're leaning towards core)? If you chose a core installation, have you encountered any patching issues, especially since we're transitioning to Action1 from WSUS? Thanks in advance for any insights you can share!
1 Answer
I did a similar migration a little over a year ago, moving to Server 2022 with a full install. To be honest, the migration went surprisingly smoothly, and we've had no problems with either the hosts or the VM guests since then, aside from typical Windows quirks. We opted for Synology instead of Veeam, but the process seemed quite similar, involving a full backup of the guest followed by a restore to the Hyper-V host. Just remember to check your network setup after the restore!
Did you migrate from a vSAN environment to Hyper-V with storage spaces direct, or are you using traditional storage? We've had issues with Storage Spaces before, and I’m curious if SSDs have made a difference for those of us using HCI.