So a few months ago I finally got tired of MS Virtual PC inability to support multiple monitors (and yes there are way – I even have an article on this site explaining how it can be done, but they aren’t up to par) and purchased VMware WorkStation Pro 12 and must say I love this software application!!! Below are my findings this far.
Pros
- Converter to convert MS Virtual PC VMs to VMWare format (so you can minimize to time spent switching!)
- True multi-monitor support (high resolution)
- Very quick OS installation
- Very quick Clone VM creation
- You can change most VM settings dynamically while in use (unlike MS Virtual PC which requires being shutdown and then changed and then restarted)
- I can install games within VMWare VMs (for some reason they would not install in MS Virtual PC, yet there is no such issue with VMWare)
- Allows full integration with the host while a VPN connection was running (this was not possible with MS Virtual PC, my post entitled Cisco AnyConnect – VPN establishment capability from remote desktop is disabled for all the details)
- Supports multiple CPU cores
- Support direct integration of printers (nothing to install just a check box to check off)
- You can pause your VM (similar to MS Virtual PC’s hybernate function but I find VMWare’s to be much faster)
Cons
- Does not auto-expand the Virtual Hard disk so you have to determine the size allocated when creating the Virtual Machine.
For instance, I created a 25GB VM and installed Windows 7 and a few very small utilities (NotePad++, Irfanview, installed an Antivirus, …), then I created a few clones based on this master VM so I could create isolated VMs for different versions of MS Office for my development purposes. When I installed Office, my 25GB was almost all used up and I started getting page file errors due to not having enough free space. So I then said to myself, no big deal, I’ll just expand the VM. WRONG! you can’t expand a clone and you can’t expand the master VM as long as clones based upon it exist!!! So I had to delete all my child clones, delete the snapshots, expand the master VM and then restart the entire clone creation process, Office installation, … countless hours lost. This is a MAJOR PITA. This is the only point I’ll say MS Virtual PC does, by far, much better since their VMs simply expand as you need them to. No configuration, no expanding, … it just takes more room as you require it.
Pro/Con depending how you like things
- You have to mapped the host PC’s drives (unlike MS’ Virtual PC which they just appeared automatically). Some people will like this because it give them 100% control. For someone like me, I enjoyed Virtual PC’s way of working, but I am not used to VMWare’s so it is all the same to me.
I will post more as I get more experience with this application, but all of the above to say I should have made the move years ago as it would have made me much more productive.





