Thank you yes what we saw in the lab was that it throws and error and were wondering that we should remove them before conversion to avoid the errors it throws.

Thanks and understand, how about VMware tools should we remove those before conversion?

Quick question converted a 2 VM's to a temp hyper v host as we needed to reload the current ESX server with windows. We booted up the VMs on the temp hyper v host to make sure we could boot and test all is good. The old server was reloaded and we copied the VM's from the temp Hyper V to the new Hype...

Thank you all for the help and responses and the tool.

You can configure HyperV to do Live migrations natively, even if they aren't in a cluster. There may be some nuance to the networking setup or authentication setup depending on how you've done things. But generally you can enable Live Migrations on both boxes, make sure your virtual switches have t...

Yes, the IP issue is expected. In VMWare you probably had a VMXNet3 or emulated Intel adapter. HyperV will create a HyperV adapter. Windows does not automatically translate the network configuration from one adapter to another. The Starwinds converter will not touch the OS, just translate the disk....

Thank you for the reply on the ESX server the dc had a static ip once we ran the converter and booted it up on the Hyper V box went into control panel and the IP address on the nic was gone it was set to DHCP, so we had to reset the ip on the migrated DC to the correct one but got the this ip is in ...

After migrating the VM, I noticed that all server NICs reset to defaults—is this normal? Also, once migration is complete, can files simply be copied from the temporary Hyper-V server to the newly formatted Hyper-V server without needing a v2v process?