

I installed mine on a Windows 10 laptop despite having the OS complain about it. Other than that, the installation process is dead simple.

Once downloaded, you can install the software on either a physical machine or a virtual one running Windows. The tools can be download from here provided you have a valid VMware account. To do this, we will be using a free tool called VMware vCenter Converter Standalone. Today, I’ll show you how to convert a virtual machine running on Hyper-V to one hosted on a VMware platform such as ESXi or VMware Workstation. With this in mind, it is perhaps time to revisit some old preconceptions and give the MS product a thorough look.īut I digress. With Windows Server 2016 released last September 2016, things now look pretty interesting on the Hyper-V front. I think people tend to waste too much time bashing one product over the other. The fact remains, however, that both vSphere and Hyper-V have their strong points. One might infer that I am a VMware fanboy which is only partly true, at least when it comes to hypervisors and virtualization in general.
