Domain Controller VMWare to Hyper-V

[Szymon]

Hi,

I want to migrate VMware Machine to Hyper-V - it's Active Directory Domain Controller.

Has anyone been running conversion of DC? Domain was working fine after conversion?

Thanks everyone for help,

Best Regards

Szymon

[yaroslav (staff)]

Welcome to StarWind Forum. It should be OK as that is just a VM. If the converted VM does not start, you still have the old one (V2V does not remove the old one).
Let me know if assistance is required.

[ConTimKO]

Hi,
I want to migrate VMware Machine to Hyper-V - it's Active Directory Domain Controller.
Has anyone been running conversion of DC? Domain was working fine after conversion?

Hi, I am looking for an answer to the same question.
Did you ever complete that job succesfully?

To someone @StarWind:
Does V2V add anything to proces that a Veeam Backup and Restore does not?
(besides the easier handling, and direct copying)

Thanks!

[yaroslav (staff)]

ConTimKO,

Welcome to StarWind Forum V2V and Veeam B&R serve different purposes. V2V does conversion and allows for P2V and converts VM formants while Veeam B&R serves for backups.
You can V2V and P2V your DCs.

[ConTimKO]

ConTimKO,
V2V does conversion and allows for P2V and converts VM formants while Veeam B&R serves for backups.

Yes, that is obvious... but Veeam can backup from VSphere an restore to HyperV, converting drives more or less the same way V2V does.
I was just wondering what extra stuff V2V does, to guarantee smooth transition. Also virtual hardwarewise.

ConTimKO,
You can V2V and P2V your DCs.

I tried our Database server first. Probably less prone to problems, I thought. It is a simple W2012 install with only a Unit4 database installed.
I have connected it to a private switch, to not have it interfere with the running original on the VSphere.
But the clone refuses to to boot to the desktop. It starts booting alright, but after two attempts it goes into troubleshooting mode.
Repair routines do not find any problems that can be repaired.

EDIT:
I was able to read the error message by filming the bootsequence:
Inaccessible boot device

[yaroslav (staff)]

Try converting the disk alone with repair mode enabled.

[ConTimKO]

Try converting the disk alone with repair mode enabled.

I tried a new conversion and made sure gen2 was selected. I made sure Windows repair mode was selected.
It generates a VHDX now instead of a VHD, and it gets connected over SCSI automagically.
But a booterror, probably the UEFI equivalent of the gen1 BIOS message:

BootErrorA.jpg (64.81 KiB) Viewed 3086 times

[yaroslav (staff)]

Did you select explicitly selected VHD (not VHDX) while converting the disk?