Managing Software Updates for MED-V Workspaces
Updated: March 10, 2011
Applies To: Microsoft Enterprise Desktop Virtualization 2.0
You have several different options available to you for providing software updates for the applications in the deployed MED-V workspace.
|For information about how to specify the configuration settings that define how MED-V receives automatic updates, see Managing Automatic Updates for MED-V Workspaces.|
Updating Software in a MED-V Workspace
Using an Electronic Software Distribution System
If your organization uses an Electronic Software Distribution System (ESD) system to deploy software, you can use it to provide software updates for applications on MED-V workspaces just as you provide updates for applications on physical computers.
Using Group Policy
If your organization deploys software by using Group Policy, you can use it to provide software updates for applications on MED-V workspaces just as you provide updates for applications on physical computers.
Using Application Virtualization (APP-V)
If you use MED-V together with App-V, you can provide software updates to applications in the MED-V workspace by following the steps that are required by App-V for updating software. For more information, see Application Virtualization (http://go.microsoft.com/fwlink/?LinkId=122939).
Updating Software in the Core Image
Although not considered a MED-V best practice, you can install software updates to applications on the core image. After you have installed the updates, you can then redeploy the MED-V workspace back out to your enterprise just as you deployed it originally.
Important We do not recommend this method of managing software updates. In addition, if you update software in the core image and redeploy the MED-V workspace back out to your enterprise, first time setup must run again, and any data saved in the virtual machine is lost.
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.