Introduction

Before users begin to use the old applications you need to create a package containing an image of Windows XP. MED-V will be responsible for installing and configuring the advanced options during the process of creating the package. All this is done via the Workspace Package MED-V, as explained below.

Procedure

To create a package containing a virtual machine (VM) in MED-V Workspace, log on as administrator and open the Workspace Packager MED-V on the path Start> All Programs> Microsoft Enterprise Desktop Virtualization> MED-V Workspace Packager. Then click Create MED-V Workspace Package.


Figure 1 - MED-V Workspace Packager

In Package Information, specify the virtual machine name that is displayed to the user and the installation path. In this way files are created related to the package of the VM. Then click Next.


Figure 2 - Installation package name and path

In Select Windows XP Image you have to put the virtual disk file (VHD) image path with an existing Windows XP installed. You can use the Windows XP mode image that can be found at the link below:

http://www.microsoft.com/windows/virtual-pc/download.aspx

It would be interesting if this file already contains the applications that will be used by MED-V, but this procedure can be done after creating the package as well. After choosing the file, click Next.

 
Figure 3 - The path of the virtual disk containing Windows XP

During the VM first use you have to make some adjustments over the Sysprep. in Initial Configurations you can choose to set up Unattended or Attended Setup. Unattended Setup in the process is automated and you can choose whether the user can change these settings or not. With the Attended option the user will have to interact during the process to configuring the VM.

If you want to install the package for all users or only the user who is logged in, choose the desired option in the second half and then click Next.

 
Figure 4 - Initial Configurations

During the package installation is possible to customize the main message, error message and URL information on the MED-V, as shown in Figure 5.


 
Figure 5 - Custom Messages

On the next screen you must create a rule for naming the virtual machine. There are several default rules as used in Figure 6 or you can create your own rules. After the name conversion setting, click Next.


Figure 6 - Virtual Machine Naming

If the applications used by MED-V 2.0 need regional settings, user settings or even the domain, select them and click Next.


Figure 7 - Host Settings

Under Startup and Networking can be assigned for users to manage MED-V startup or configure automatic startup, and the options and network credentials.

If the VM needs to access the Internet choose Shared and the next option is possible to enable to store the user credential.

 
Figure 8 - Startup and Networking

For applications and web pages that require earlier versions of Internet Explorer, like versions 6 and 7, specify the URLs and the IE Web Redirections appearance. To help, you can use a text file to import more than one URL.


Figure 9 - Web Redirections

Confirm the selected options and click Create to create the package.


Figure 10 – Summary



Figure 11 - Completion

In the path specified are displayed files from the virtual machine installation package, as shown in the procedures above. They are created with the following specifications:

Setup.exe - Used for manual installation.

<package Name>. msi - Used to be installed via GPO or System Center Configuration Manager.

<package Name>. MEDV - Contains the compacted VHD.

<package Name>. ps1 and <package name>. reg - Archives with MED-V settings .



Figure 12 - MED-V Package Files

Now just select the best option for their users who must use the legacy applications and start using manual installation, GPO or System Center Configuration Manager 2007 R2.

The following PowerShell cmdlets can also be used in the above process.

• New MedvConfiguration

• Export-MedvConfiguration

• New MedvWorkspace

• Export-MedvWorkspace


With these commands you can create several scripts to automate all processes.

For those commands to work, you must load the library MED-V with the following cmdlet in PowerShell:

Import-Module microsoft.medv

Leandro Carvalho
MCSA+S+M | MCSE+S | MCTS | MCITP | MCBMSS | MCT | MVP Virtual Machine
MSVirtualization | Wordpress | Winsec.org | LinhadeCodigo | MVP Profile
Twitter: LeandroEduardo | LinkedIn: Leandroesc