Microsoft Enterprise Desktop Virtualization

Microsoft Enterprise Desktop Virtualization, a core component of the Microsoft Desktop Optimization Pack (MDOP) for Software Assurance, enables deployment and management of Microsoft Windows Virtual PC desktops to enable key enterprise scenarios. 

Incompatibility of applications with newer versions of Microsoft Windows can delay enterprise operating system (OS) upgrades. Testing and migrating applications can be time-consuming, and meanwhile users are unable to take advantage of the new capabilities and enhancements offered by the new OS.

By delivering applications in a Windows Virtual PC that runs a previous version of Windows XP, MED-V removes the barriers to OS upgrades and allows administrators to complete testing and to deal with incompatible applications after the upgrade.

From the user’s perspective, these applications are accessible from the standard desktop Start menu and appear side-by-side with native applications—so there is minimal change to the user experience.

MED-V helps enterprises upgrade to the latest version of Windows when some applications are not yet functional or supported.  MED-V enables customers to migrate to Windows 7 while still leveraging existing legacy Windows XP line of business applications.

1.1    What’s New in MED-V 2.0

MED-V 2.0 contains the following improvements since version 1.0.  If you are an experienced MED-V 1.0 administrator using this guide to evaluate MED-V 2.0, please take note.

MED-V Workspace Creation

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.

MED-V Workspace 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 PowerShell^TM. This functionality replaces some of the former console abilities and functionality that managed centralized functions of MED-V.

MED-V Workspace Distribution

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.

First Time Setup

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.

Application Publishing

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.

URL Redirection

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.

Troubleshooting

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.

 For More details Technet.microsoft.com