You should NOT perform a Live running VM migration of Active Directory Domain Controllers. I have always powered mine off. This help prevent issues with how snapshots of AD occur and then replicate during the migration. App servers it can vary and depends on the application on the source server. Dat...

Thing I have seen to help. Source: 1. Increase read cache. (only helps short term) 2. Power off the VM 3. Execute during low off peak IOPS times (reminder on backups after hours could hit disk hard) Destination: 1. Have a fast CPU higher single thread rating helps. 2. Use SSD is possible. 3. Increas...

So in some testing. ESXi VM with PVSCSI on source VM as only controller for only 1 VMDK for C:\ does migrate. Some others in same configuration do not. So strange. I can boot into OS repair mode. use disk part and assign a C: drive and execute chkdsk on C: and file systems is good. I did note that t...

So in some testing. ESXi VM with PVSCSI on source VM as only controller for only 1 VMDK for C:\ does migrate. Some others in same configuration do not. So strange. I can boot into OS repair mode. use disk part and assign a C: drive and execute chkdsk on C: and file systems is good. I did note that t...

Further on this.
If I do start another starwind conversion in another GUI window the network throughput goes up double.
So it seems the speed per conversion is 1Gb/s

I wonder if there limitations in process throughput?

Hi All I am looking for a check list on what to do to the source VM before conversion to Hyper-V. We have many VM's and almost all of them are tune with using the following VM hardware configurations. Source ESXi VM's * OS - Windows 2016 & higher * Controller - Paravirtual SCSI * Disks - Mostly ...

Is this fixed in the latest build?
I have many thick VMDK on ESXi needing to go to Hyper-V

I wish when selecting the Hyper-V you could select/specify the destination VHDX type.