But it does matter to me because all my servers are running on ESX, which will be a huge benefit to me if I can create Virtual Machines that can be seamlessly used on the server platform.īesides, it has the ability to run the Virtual Machines that are created by Windows Virtual PC. Reason #4: Support upstream VMware Products It may not be benefit to you if you don’t use ESX or VSphere to run your servers. So here you go, having this feature back makes me like VMware Player a little bit more over Windows Virtual PC. Sounds quite cool but it misses one feature that I particularly liked before, file drag and drop. So it’s actually not running a real virtual client on the desktop, rather, just a RDP session that connects to the VM running at the backend. Reason #5: Support file drag and drop between host and guest machine If you look at Windows Virtual Machine more closely, you will find that it’s actually integrating RDP client with the Virtual PC. It seems like, as long as you are not installing a customize-type of OS, you don’t need to interact with the installation process that much. A new virtual machine is up and running, and ready for you to play with.

Reason #6: The process of creating new VM is easier Just go through the wizard, fill in necessary information, start the VM, and 30 minutes later, done. You can turn it on or off from the Preferred mode dropdown menu in Virtual Machine Settings window if you want to. Reason #7: hardware requirements are lower There is no Virtualization Technology or AMD-V limitation on processor level that keeps those who don’t have them from using it. It’s just these reasons that keep me using VMware Player most of the time.

I still like and use both of them on my main working Windows 7 machine occasionally, and I do keep my eyes on them for future developments. Windows Virtual PC or Sun VirtualBox, but don’t get me wrong that I hate the others. I like VMware products and prefer using them over the other products, e.g.

Vmware player 7