This tool give you the ability to convert remote client/Server too and executing post migration task (like disk resize, network changes and so on )
here they are official documentation and Vmware Converter download link:
https://my.vmware.com/web/vmware/evalcenter?p=converter&cmd=displayKC&externalId=1004588
VMware vCenter Converter Standalone User's Guide
https://www.vmware.com/go/converter-user-guide
VMware vCenter Converter Standalone Documentation
https://www.vmware.com/support/pubs/converter_pubs.html
With this article I wouuld like to focalize on some il limitation and best practices that are well explained here:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004588
- If the source is a domain controller, special considerations must be made. VMware does not recommend virtualizing an active domain controller with Converter. For more information, see Virtualizing existing domain controllers (1006996).
- If the source is Microsoft Exchange, SQL, or other database server, VMware recommends that the application (Microsoft Exchange/SQL) and database services be shut down prior to conversion. This minimizes any chance of corrupted database tables or stale data in the destination virtual machine.
- Disable the real-time antivirus scanning during the conversion.
- Read the VMware Converter Release Notes. The release notes review important limitations or issues that may affect the conversion process.
- Verify that you are using or have downloaded the latest version of VMware Converter. ........
... - If the NIC on the source machine is compatible with TOE (TCP Offload Engine), you need to disable it by running this command in a command prompt on the source machine:
netsh int tcp set global chimney=disabled
For additional information, see the Microsoft Knowledge Base article 951037.
Note: The preceding link was correct as of November 21, 2014. If you find the link is broken, provide feedback and a VMware employee will update the link.