In order to run old applications that not compatible with Windows 7, MED-V solution will help you to do that, you just need to create a package containing an image of Windows XP and MED-V will be responisble for installing and configuring the advanced option during the process of creating package.
All this can be done via MED-V Workspace Packager.
To create package with Microsoft Windows XP virtual machine, you need first to create a new virtual machine and install Microsoft Windows XP Professional with service pack 3, install and configure required prerequisites and install applications.
For more information about requirment and prerequisites, please click here
You have to do the following before starting the below procedure:
- Creating a Windows Virtual PC Image for MED-V
- Installing Applications on a Windows Virtual PC Image
- Configuring a Windows Virtual PC Image for MED-V
Create a MED-V workspace package:
A MED-V workspace is the Windows XP desktop environment where end users interact with the virtual machine provided by MED-V. The administrator creates and customizes the MED-V workspace. The workspace consists of an image and the Group Policy that defines the rules and functionality of the MED-V workspace.
Before you start to build your MED-V workspace deployment package, verify that you have access to the following items:
- A prepared Windows XP image
- A text file or list that contains URL redirection information
To Create workspace package, please follow the below steps:
1- Click Start, click All Programs, click Microsoft Enterprise Desktop Virtualization
2- On the MED-V Workspace Packager main panel, click Create a MED-V Workspace Package.
3- On the Package Information page, enter a name for the MED-V workspace and select a folder where the MED-V workspace package files are saved
4- On the Select Windows XP Image page, specify the location of your prepared MED-V Windows XP Virtual PC image (.vhd file).
5- On the First Time Setup page, select whether you want first time setup to run while attended or unattended and whether you want the MED-V workspace used separately or used by all end users on a shared computer.
I’ll select Unattended setup, without any notification in my example.
6- On the Naming Computers page, you can specify whether computer naming is managed by MED-V or by a system management tool, such as Sysprep. The default is that computer naming is managed by a system management tool.
If you specify that computer naming is managed by MED-V, select a predefined computer naming convention (mask) from the drop-down list. A preview of a sample computer name appears that is based on the computer that you are using to build the MED-V workspace package.
7- On the Copy Settings from Host page, you can select the following settings to specify how the MED-V workspace is configured:
8- On the Startup and Networking page, you can change the default behavior for the following settings:
9- On the Web Redirection page, you can enter, paste, or import a list of the URLs that are redirected to Internet Explorer in the MED-V workspace.
10- On the Summary page, you can review the packaging settings for this MED-V workspace.
11- If the MED-V workspace package is created successfully, the Completion page displays a list of the files that you created and their respective locations. The following is a list of the files that are created and their descriptions:
- setup.exe—an installation program that you deploy and run on end-user computers to install the MED-V workspaces.
- <workspace_name>.msi—an installer file that you deploy to the end-user computers. The setup.exe file will run this file to install the MED-V workspaces.
- <vhd_name>.medv—a compressed VHD file that you deploy to the end-user computers. The setup.exe file uses it when it installs the MED-V workspaces.
- <workspace_name>.reg—the configuration settings that are installed when the setup.exe, <workspace_name>.msi, and <vhd_name>.medv files are deployed and setup.exe is run.
- <workspace_name>.ps1—a Windows PowerShell script that you can use to rebuild the registry file and re-build the MED-V workspace package.
SC Configuration Manager/Windows 7 Deployment