I previously mentioned Vmware ACE, but not to any great detail.

VMware ACE is a product that you use to wrap virtual machines into, along with various permission. It then bundles this into an installer which you can pass to those that need it. Permissions include network policy, user policy, time outs (after which you can’t use it) and device control. It’s great for creating a setup that you want to pass out, but still keep control.

Imagine a demo of a product that needs access to your database over the internet. Easy. Just set the network policy to only connect to your database server, set the expiry date and add a password protected user. Then post on your web site. Customers can download and install it, then because of the network policy it can only talk to your server, it will time out after a certain time, and only customers can use it. It’s much harder to use the virtual machine to attack you because of the network policy, the general public can’t use it, and custemers can have a real trial of your latest killer application – but not get it for life for free!

I hope you can see the advantages of doing this. But due to the nature and intention of the product it has its limits. The biggest draw back for me is the lack of networking flexibilty. The point of this product though is not to wrap all the great features and as such shouldn’t be seen as a minus point when looking at it, but instead you must look at how you are going to use it.

For this reason I have decided not to use VMware ACE, but to remove it from my list of products that I will be recommending and using in my dissertation. It has great potential for the future use and it’s certainly one that I will be keeping in the back of my mind.

But for now it’s between VMware Workstation and Microsoft Virtual PC.

Having now had a good look that the questionnaire results in more detail I can say that VMware is only just ahead of Microsoft for two reasons.

1. Linux Support
2. Experience and age of product