Please provide your feedback in this short Flings' survey.
Jan 02, 2020

Thanks to each of you for creating this fling, it has made life easier at my previous job as well as my current gig; I've migrated nearly 1000 VMs without issue using this fling.

Jan 27, 2020

Thank you for your appreciation. It gives us great encouragement to do better for this tool.

Jun 23, 2018

Hello! Have problem. On every VM get eroor:
State = ERROR | Error = Currently connected network interface 'Network adapter 1' uses network 'DVSwitch: 50 37 66 8e 3f 16 0d 37-03 78 07 08 87 73 ec d9', which is not accessible. | Result = null

Jun 26, 2018

It seems the source and destination esx hosts have different network and the network(on source host) the vm is connected to is not accessible from destination host.
Could you please confirm the following information?
1) ensure that source and destination hosts are connected to same network.
2) are you passing -dnw parameter to specify destination network(vDS portgroup)?

Jun 14, 2018

Can you please give the source and destination esx hosts version details?
This error is not specific to cross vCenter migration, this issue may occur in single VC too if EVC settings are not properly configured .
Can you please try adding the destination host to source vc (or vice versa) and see if migration succeeds.

Jun 12, 2018

Relocate works great for powered off VMs. I can't get powered on VMs to work. Source is vSphere 6.0 U3 and destination is vSphere 6.7. I keep getting "The target host does not support the virtual machine's current hardware requirements." Both sites have EVC set to Ivy Bridge, so I am not sure what it means by hardware requirements. Any ideas?

Jun 14, 2018

Can you please provide/confirm on below items?
- Source VC/ESXi build details
- Destination VC/ESXi build details
- If possible source cluster details like is it mixed version hosts etc.
or any other info would be helpful.

Jun 14, 2018

Here you go.

All hosts have Broadwell processors with EVC set to Ivy Bridge. I haven't tried this, but I can almost guarantee if I remove a 6.0 host and add it to the 6.7 cluster, I will be able to vMotion without any issues.

Jun 26, 2018

I hope this issue is not specific to the fling and it is tracked in above community forum.