Microsoft today announced the general availability of MDOP 2011, which includes among other things the long awaited MED-V 2.0!
So what’s new in MED-V 2.0:
MED-V Workspace Packages must be created by using Windows Virtual PC. Existing Virtual PC 2007 images must be migrated. The virtual machine Prep tool is not included in MED-V 2.0 and administrators should configure, update, and optimize their images according to the MED-V 2.0 help file. Running Sysprep on the MED-V image is a required step and must be performed prior to packaging.
The MED-V Workspace Packager packages the virtual hard drive with the appropriate settings and image so that it can be easily deployed by administrators. Advanced features are provided in the background using Windows PowerShellTM. This functionality replaces some of the former console abilities and functionality that managed centralized functions of MED-V.
Dedicated server infrastructure is no longer required for MED-V 2.0 and the client pull method for deploying MED-V workspaces has been removed. MED-V workspaces are now deployed using electronic software distribution (ESD) infrastructure and can be stored on common shares that are used for other installation packages.
The first time setup process is now integrated with the standard imaging convention of Sysprep. The MED-V workspace first time setup process can dynamically apply settings specified in the MED-V Workspace Packager to the image as it begins Mini-Setup. The scripting tool in the console has been removed and the first time setup process is now based on options that are specified in the sysprep.inf file and configured in the MED-V Workspace Packager by the administrator.
Administrators can install applications on the MED-V image either prior to packaging, after the MED-V workspace has been deployed, or by using a combination of both. MED-V no longer looks at MED-V workspace policy to publish applications, but instead refers to what is actually installed on the guest. As applications are installed on the guest, they are automatically detected and published to the host Start menu and are ready to be started by the end user.
MED-V 2.0 provides seamless host-to-guest web address redirection based on the settings configured and managed by the administrator. After a URL is redirected to the guest browser, the default experience is to attempt to limit the user to that redirected site. This minimizes the browsing activities that a user can perform that are not intended by the administrator. Guest-to-host browser redirection was removed.
MED-V now leverages standard host-based processes for troubleshooting. Because the MED-V workspace in no longer encrypted, it can be opened in full-screen mode within the Windows Virtual PC console, where it can be viewed and worked with as a standard workstation. In addition, the logs are no longer encrypted locally or logged centrally. MED-V now makes extensive use of the local event logs, and the logging level of the output – from informational to debug levels – is easily configured. Finally, a troubleshooting toolkit is now provided so administrators and help-desk personnel can have a graphical, aggregated view of all the troubleshooting options, and they can effortlessly select the activities that best suit their needs.
MED-V is no longer run as a system service. Instead, it is run as user-owned processes and it only runs when a user is logged on. Functionality that was formerly provided by the system-owned service is now provided in the user-side processes.
Check out all the details over on the MDOP blog here.
The Microsoft Enterprise Desktop Virtualization v2 Beta Refresh is now available for download on the Microsoft Connect site. The updated software provides fixes to customer reported issues and new features including
Workspace packager updates which add additional options for customizing the MED-V computer names
Changes to first time setup process to automate the installation of the MED-V Guest agent into the Windows XPSP3 image. (See Release Notes for more information)
Use the following links to read the release notes and begin evaluating in your environment.
Beta Refresh Release Notes
Download Beta Refresh software
Microsoft Enterprise Desktop Virtualization (MEDV) provides companies with a way to provide virtual machines to end users that are managed centrally. It helps solve application compatibility problems - you can give users a virtual machine with their legacy apps, and the apps appear to run seamlessly side by side with other apps on their Windows 7 desktop.
The MEDV team is working hard on a new version, here is a sneak preview of the next version of MED-V.
You can find out more about MEDV at http://www.microsoft.com/medv
Last week MED-V 1.0 SP1 was released as part of the Microsoft Desktop Optimization Pack (MDOP) 2010 refresh. This update adds some key new functionality:
Note that MED-V 1.0 SP1 still only supports Virtual PC 2007 SP1, so you will be running Virtual PC 2007 SP1 on Windows 7 (not Windows Virtual PC). It also means that Microsoft now can use native VHD booting for a MED-V demo environment.
Existing MDOP customers can download the MDOP 2010 Refresh at the Volume Licensing Service Center (VLSC). For people with MSDN / TechNet subscriptions, the MDOP 2010 Refresh can be downloaded from MSDN and TechNet.
If you do not know what MED-V is or why you should care – if you need to use Virtual PC to solve an application compatibility problem on more than half-a-dozen computers – you need to be looking at MED-V to provide a deployment and management solution for your virtual machines. More details hare here: www.microsoft.com/med-v