Hello,
We are currently migrating our virtual machines from VMware ESXi to Microsoft Hyper-V (Windows Server 2025) using StarWind V2V Converter Free, version 9.0.1.848 (build 848).
We need to migrate a production Windows Server 2016 Active Directory Domain Controller with two virtual disks:
C: Operating system
D: Active Directory database (NTDS) and SYSVOL
The source VM will be completely powered off during the conversion, and both disks will be converted directly from ESXi to Hyper-V.
We have already transferred the FSMO roles to another Domain Controller and verified that Active Directory replication is healthy.
Before proceeding, we would appreciate clarification on the following points:
Is migrating an Active Directory Domain Controller supported or recommended with StarWind V2V Converter build 848?
Does the converter correctly handle the VM-Generation ID when migrating from VMware to Hyper-V?
Are there any specific precautions for converting a Domain Controller with multiple virtual disks?
Are there any known issues with this version that could affect Active Directory after the migration?
Any guidance from the StarWind team or users who have performed a similar migration would be greatly appreciated.
Thank you.
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software