QUOTE (steltek @ 1-19-09, 8:18pm)

I perused through the datasheets. Apparently, VirtualPC2007 SP1 is installed within the desktop OS. A client Microsoft OS is running within VirtualPC 2007 in such a manner that the applications installed on the virtual machine image are made available from the start menu of the host desktop machine.
VMware already has this capability under VMware Workstation 6.5. It's called "Unity" mode. There are limitations to this though. The apps that get launched in Unity Mode see the disk drives of their corresponding VM, not the outter OS. (You can MAP the physical/outter machine's drives to the VM though so that the real machine's drives can be viewed from within the VM apps).
QUOTE (steltek @ 1-19-09, 8:18pm)

The datasheets also state that MED-V v1 can only run on managed desktops and requires both Active Directory and separate management servers, so I suspect that the initial release will probably be of interest to only large or enterprise level customers.
VMware doesn't require this.
QUOTE (steltek @ 1-19-09, 8:18pm)

I could see the federal agency where I work going with this if for no other reason than security. It has an installation option which allows reversion of the virtualized image to a clean one at the end of the day, eliminating any changes to the virtualized OS or its installed applications. I can just see our security Nazis drooling (virtually speaking

) over this.
VMware has, for many years now, supported "non-persistent" virtual hard drives. When a VMware HD is set to "non-persistent," as soon as you power off the VM, any changes made during the previously powered on session are gone.

QUOTE (steltek @ 1-19-09, 8:18pm)

It doesn't say whether the virtual OS within the image requires a separate license. However, we are talking about Micro$oft here -- of course it will require a second license! Who are we kidding???
Agreed, but running XP inside of a VMware virtual machine also requires a separate license.