Hey all,
First time poster, so go easy on me! 
I'm performing a number of V2V migration using standalone convertor 4.1 from an old ESX 3.5 cluster sat on HP BL585s to a ESX 4.0 cluster on HP BL680 G5s.
I have a single VM left to move across. It's an old NT4 domain controller.
Can anyone give me any ideas of any potential pitfalls? I know i'm going to have to move it over with standalone convertor 3.03 (can this be installed alongside 4.1 on the same machine?). What's the best practice regarding hardware version (update or keep on 4?), changing the NIC (use an E1000, or will it take a vnxnet NIC?)?
Also, will i run into any other issues with regard the hardware?
Any help would be greatly appreciated
Thanks
Jason
Accepted Solutions
Welcome to the Community,
First time poster, so go easy on me!
That's no excuse 
I assume you don't have any snapshots on this VM!? In this case, don't use the converter, but just power off the VM and use e.g. Veeam's FastSCP to copy the virtual machine's folder from the old host to the new one. Then add the VM to the inventory.
Once done, you can decide whether to update the VMware Tools and the virtual hardware. Personally I would probably only update the tools on NT to keep it easy. Upgrading the hardware will most likely require some additional work, like installing SP6 again, ...
André
Welcome to the Community,
First time poster, so go easy on me!
That's no excuse
I assume you don't have any snapshots on this VM!? In this case, don't use the converter, but just power off the VM and use e.g. Veeam's FastSCP to copy the virtual machine's folder from the old host to the new one. Then add the VM to the inventory.
Once done, you can decide whether to update the VMware Tools and the virtual hardware. Personally I would probably only update the tools on NT to keep it easy. Upgrading the hardware will most likely require some additional work, like installing SP6 again, ...
André
