Windows 7 Migration
Learn the Differences Between App-V and MED-V
In past months we've talked a lot about virtualization tools App-V and MED-V: what's new in the latest versions, how they're being used in various enterprise...
In past months we've talked a lot about virtualization tools App-V and MED-V: what's new in the latest versions, how they're being used in various enterprise environments, and so on.
But if you're new to these tools, you might be wondering just what separates one from the other. After all, they both share the same "capital-V" suffix!
Microsoft's Rob Waggoner tackles that question in, What's the difference between App-V and MED-V. (He left out the question mark, not us.) Here's an excerpt from the section on the latter tool:
MED-V uses a virtual machine to host your application. Use MED-V when the application you want to deploy does not run on your host OS. Let's say you want to move to Windows 7, but you still have a legacy application that requires Windows XP and Windows 2000. MED-V leverages a virtual machine to deliver your application to your users. The best part about MED-V is that the users don't see or interact with the virtual machine itself, just the application.If there's a better description of MED-V, we haven't read it. Waggoner also provides some great real-world examples of how the tool works, particularly from an end-user perspective. So if you're new to App-V/MED-V and/or uncertain about which tool you should be using under which circumstances, this is required reading.
