Trial Guide

This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of
publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of
Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS
TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this
document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic,
mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this
document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you
any license to these patents, trademarks, copyrights, or other intellectual property.

 2010 Microsoft Corporation. All rights reserved.

Microsoft, Windows, Windows Vista, Active Directory, Microsoft SQL Server are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
 Trial Guide

Contents
1 Evaluating Microsoft Enterprise Desktop Virtualization (MED-V) .............................................. 4
1.1 Introduction to Microsoft Enterprise Desktop Virtualization ..........................................................4
2 Part 1: Installing and Configuring MED-V ............................................................................ 6
2.1 System Requirements for MED-V 1.0 SP1 Trial ..........................................................................6
2.2 What Do I Need and Where Do I Get It? ..................................................................................7
2.3 Installing MED-V Management Server .......................................................................................8
2.4 Installing the MED-V Client and Management Console ............................................................. 11
2.5 Preparing a Virtual PC image for MED-V ................................................................................. 12
2.6 Importing a Policy to the Server ............................................................................................. 14
3 MED-V Administration ........................................................................................................ 15
3.1 Creating a MED-V Test Image ................................................................................................ 15
3.2 Associate Test Image with Workspace Policy .......................................................................... 16
3.3 Testing a MED-V Image Locally .............................................................................................. 17
3.4 Packing the MED-V Image ..................................................................................................... 17
4 Part 2: Evaluating Management Features of MED-V .......................................................... 18
4.1 Deploying a MED-V Workspace .............................................................................................. 18
4.2 Changing Trial Guide Settings ................................................................................................ 18
4.3 General Tab .......................................................................................................................... 19
4.4 Virtual machine - Assigned Image Tab ................................................................................... 19
4.5 Applications Tab ................................................................................................................... 20
4.6 Web Tab .............................................................................................................................. 20
4.7 VM Setup Tab ....................................................................................................................... 20
4.8 Network Tab ......................................................................................................................... 20
4.9 Deployment Tab ................................................................................................................... 21
4.10 Performance Tab .................................................................................................................. 21
5 Testing the MED-V Client and Workspaces ......................................................................... 22
5.1 Provisioning MED-V ............................................................................................................... 24
5.2 Expiring a MED-V Workspace ................................................................................................. 25
5.3 MED-V Workspace Domain Join ............................................................................................. 25
6 Demonstrating Troubleshooting Capabilities of MED-V ..................................................... 30
6.1 Settings Menu ....................................................................................................................... 30
6.2 Diagnostics ........................................................................................................................... 30
6.3 Diagnostic Reports ................................................................................................................ 30
6.4 Create a MED-V Installation Package ...................................................................................... 31
6.5 Monitoring and Troubleshooting ............................................................................................. 31

Evaluation Guide
 Trial Guide

6.6 Diagnostic Reports ................................................................................................................ 32

7 Next Steps ........................................................................................................................... 33
7.1 Planning a Full Infrastructure ................................................................................................. 33

Evaluation Guide
 Trial Guide

1 Evaluating Microsoft Enterprise Desktop Virtualization (MED-V)

®
This document provides instructions for the installation, configuration, and evaluation of a Microsoft
Enterprise Desktop Virtualization (MED-V) environment. The information in this guide enables IT
professionals to create a test environment or proof of concept to evaluate the features of MED-V. The
following documentation provides a detailed description of the setup of MED-V components to evaluate
the main features of the software. Step-by-step instructions will be provided from additional resources and
inline in the documentation.

CONCEPTS COVERED
®
This guide creates an environment where a Windows XP-based guest (virtual machine) with applications
can be integrated into a Windows 7 host (physical machine). The guide includes: installation of both the
server and client, preparing a Virtual PC-based virtual machine for MED-V, bringing prepared virtual
machine images into the MED-V infrastructure, working with Workspace Policies, testing MED-V
capabilities, troubleshooting, exploring the management features, and where to go next. After completing
this guide participants will have completed the following tasks:

 Set up MED-V Infrastructure (MED-V management server, IIS Server for image delivery, and a
SQL Database for reporting)

 Management of a MED-V Infrastructure (Image delivery and updates, setting first time setup,
defining unique applications and settings for different users, monitoring users, and
troubleshooting).

1.1 Introduction to 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 Virtual PC Windows
desktops to enable key enterprise scenarios. MED-V helps enterprises upgrade to the latest version of
Windows when some applications are not yet functional or supported.

MED-V builds on top of Virtual PC to run two operating systems on one device, adding virtual image
delivery, policy-based provisioning, and centralized management. With MED-V, you can easily create,
deliver, and manage corporate Virtual PC images on any Windows-based desktop.

ENABLE LEGACY APPLICATIONS AND ACCELERATE UPGRADES TO NEW OPERATING SYSTEMS

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 Virtual PC that runs a previous version of the OS (e.g., Windows XP or
Windows 2000), MED-V removes the barriers to OS upgrades and allows administrators to complete
testing and to deal with incompatible applications after the upgrade.

4
 Trial Guide

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.

5
 Trial Guide

2 Part 1: Installing and Configuring MED-V

This section will provide guidance for installing the required MED-V components to create an evaluation
or test environment. The information below assumes that the reader of this guide will have two physical
computers: one to act as the MED-V Server and the second as the Client and administrative machine.
®
In a production environment, the MED-V Server components will be installed on a Windows Server
computer, and there would be a separate management machine (Windows XP, Vista, or Windows 7) and
many MED-V Client computers (Windows XP, Vista, or Windows 7).

2.1 System Requirements for MED-V 1.0 SP1 Trial

The following computers are required to complete the MED-V Trial Guide.

Computer Minimum Hardware Software

MED-V Server  2 GB of RAM  Windows Server 2008 (32- or

 2 GHz CPU (32- or 64-bit) 64-bit) (SP2) or Windows
Server 2008 R2 (64 bit)
 40 GB of free space
 Active Directory Domain
Services and Microsoft DNS

MED-V Client  2 GB of RAM  Windows 7 Professional or

and greater (32- or 64-bit)
Administrative  2 GHz CPU (32- or 64-bit)
Workstation  40 GB of free space  Virtual PC 2007 SP1
 Virtual PC QFE KB974918

Note: The requirements listed above are for the trial environment only.

6
 Trial Guide

2.2 What Do I Need and Where Do I Get It?

In order to complete the Trial Guide, the reader of this document will require the MED-V software,
appropriate hardware, and a virtual machine. The following list details what is needed to complete the
guide and where to get it:

What do I need? Where do I get it?

MED-V software and MED-V 1.0 SP1 software is part of MDOP 2010 Refresh DVD
Virtual PC MED-V virtual Microsoft Volume Licensing Site (MVLS)
machine additions update
It is available for evaluation to subscribers of
MSDN
TechNet

Virtual PC 2007 SP1 and Available with the installation bits of MED-V in the
hotfix package for Virtual PC Installers\VPC2007_SP1 directory from the MDOP DVD. The MDOP
2007 SP1 (KB974918) 2010 Refresh DVD includes both 32- and 64-bit versions of VPC 2007
SP1 and Hotfix. Install the appropriate one for the operating system
platform.

MED-V Planning, Deployment http://go.microsoft.com/fwlink/?LinkID=167079

and Operations Guide

SQL Server 2008 Express http://www.microsoft.com/express/Database

Edition R2

Virtual machine (IE6- http://www.microsoft.com/downloads/details.aspx?FamilyID=21eabb90

XPSP3.exe) or create your -958f-4b64-b5f1-73d0a413c8ef&DisplayLang=en
own virtual machine

Windows XP SP3 ISO Microsoft Volume Licensing Site (MVLS)

For evaluation to subscribers of
MSDN
TechNet

TrialGuide_Policy.xml http://go.microsoft.com/fwlink/?LinkId=194833

7
 Trial Guide

2.3 Installing MED-V Management Server

The first task in building a test environment is installing the MED-V Server. In this Trial Guide a single
MED-V server will be created with the MED-V Management Server, IIS, and SQL all running on a single
box. For a high number of MED-V users these components can be installed on separate servers. The
MED-V Management Server associates virtual images from the image repository along with administrator
usage policies to users or groups, the IIS server hosts the image repository, and the SQL server handles
reporting First the IIS server will be installed and configured, then the SQL server, and finally the MED-V
management server.

CONFIGURING THE IMAGE REPOSITORY

 On the Windows Server machine, install the IIS Role and the Bits Server Extension Feature. During
the installation of IIS ensure that the following Authentication Methods are selected for installation:

1. Basic Authentication
2. Windows Authentication
3. Client Certificate Mapping Authentication

After installing IIS and the Bits Server Extension, the following steps must be completed in order to finish
the configuration:

1. Start the Internet Information Services (IIS) Manager.

2. Right-click Default Web Sites and from the popup menu, click Add Virtual Directory.

3. In the Alias box, type MEDVImages.

4. In the Physical path box, type C:\MED-V Server Images.

Note: This folder must be created first.

5. Click OK.

6. From the Internet Information Services (IIS) Manager, double-click BITS Uploads.

7. Select the Allow clients to upload files check box and click Apply.

8. From the Internet Information Services (IIS) Manager, click MIME Types.

9. Add the following MIME types:

 .ckm (application/octet-stream)

 .index (application/octet-stream)

10. From the Internet Information Services (IIS) Manager, click Edit Permissions.

11. On the MED-V site, select Security and Add read permissions to Everyone.

8
 Trial Guide

12. Restart the IIS Service.

Note: Make sure that the relevant firewall ports are open.

PREPARING MED-V SERVER FOR REPORTING DATABASE

The report database is required for storing all workspace logs. The log database is then used for
generating MED-V reports. For the Evaluation Guide, the SQL Server is remote and the following steps
must be completed on the MED-V Server.
®
Note: If any previous version of SQL Server is installed, it will need to be removed prior to the
installation of SQL Server Express 2008 R2.

Install SQL Server Express 2008 R2 with Tools on MED-V Server from the link provided in the table in
Section 2.2 with the following settings.

1. Run SQLEXPRWT_x86.exe (or if you are using 64-bit, SQLEXPRWT.x64.exe) to begin the
installation of SQL Server Express 2008 R2.

2. Click on Installation in the left pain of the SQL Server Installation Center window.

3. Next Choose New installation or add features to an existing installation.

4. Read and accept the license agreement, and then click Next.

5. On the Feature Selection page, choose Database Engine Services and Management Tools –
Basic then click Next.

6. On the Instance Configuration page choose Named Instance, and then click Next.

7. On the Disk Space Requirements page click Next.

8. On the Server Configuration page, in SQL Server Database Engine Account Name, choose NT
Authority\System, then click the Startup Type drop down arrow for SQL Server Browser and
change it to Automatic, and then click Next.

9. On the Database Engine Configuration page, select Windows Authentication Mode, and then
click Next.

10. On the Error Reporting page, click Next.

11. On the Complete Your SQL Server 2008 installation completed successfully page, click close.

 Management Tools – Basic

 SQL Server Database Engine: NT Authority\System

 Windows authentication mode

9
 Trial Guide

 Specify SQL Server Administrators: Add Current User

MED-V MANAGEMENT SERVER INSTALLATION PROCEDURES

Use the MED-V Planning, Deployment, and Operations Guide steps to install the server. The steps are
detailed in the section How to Install and Configure the MED-V Server Components.

After completing the installation of the MED-V Server, the server’s Configuration Manager will launch.
Complete the following additional steps:

 Connections tab notice that the default communication port is HTTP (TCP port 80), but that HTTPS
can be enabled if a server certificate has been bound to the machine.

Note: Port 80 is the default for HTTP, but if another application is using it on the Server, choose an
unassigned port.

 Images tab the location of the virtual machine directory is listed. However, the URL for the virtual
machines is not set.
a. On the Images tab, configure the URL for the appropriate name of your server and
virtual directory (e.g. http://servername/virtual directory. Use the name or IP address
of the local server (FQDN) and virtual directory name created previously.

 Permissions tab has the users or groups that have been assigned Management Permissions.
Additional users or groups can be configured. This setting affects which users can connect and
manage or administer the server.

 Reports tab allows configuration of the reporting database. This option will not be configured for the
test environment being created, but would be important for a production environment.
a. On the Reports tab, ensure that the Enable Reports option has a check box next to
it.
b. Data Source=localhost\sqlexpress;Initial Catalog=medv;Integrated Security=True
c. Select Create Database and then Test Connection to verify it is working properly.

 After reviewing the information, click on OK and Yes to restart the MED-V Management
Server service.

10
 Trial Guide

2.4 Installing the MED-V Client and Management Console

The next step to get the environment prepared for testing is to install the MED-V Client and the
Management Console for image preparation and testing. This will be done on the MED-V Client
computer. The MED-V Client and Management Console will be used to prepare and create and test
images, as well as create and edit policies, and finally walk through a working MED-V Workspace.

There are two MED-V components contained within the client MSI:

1. MED-V Client - The MED-V software which must be installed on end-point machines for running
MED-V Workspaces.

2. MED-V Management Console - The administrative tools, where administrators can create and
maintain images, Workspaces and their policies.

MED-V Management Console and the MED-V Client are both installed from the MED-V Client MSI;
however, MED-V Management Console is not installed by default. It is installed by checking the Install
the MED-V Management application check box during the installation.

 NOTE: Virtual PC 2007 SP1 and KB974918 must be installed prior to the installation of the MED-V
Client. (Software available from the MDOP 2010 Refresh DVD in the \MED-
V\Installers\VPC2007_SP1 directory)

MED-V CLIENT AND MANAGEMENT INSTALLATION PROCEDURES

The following steps will install the MED-V Client and Management Console for subsequent steps in
the process:

 Detailed instructions for installing the MED-V Client and Management Console are available in the
MED-V Installation and Configuration Manual in the section How to Install MED-V Client and
MED-V Management Console.

 Ensure that you use the MED-V Server name as the server name during the MED-V Client
installation.

 Ensure that you select Install the MED-V Management application check box during the
installation

After completing the steps for installation, the Start Workspace dialog will open. Cancel out of the Start
Workspace dialogue.

11
 Trial Guide

2.5 Preparing a Virtual PC image for MED-V

MED-V requires preparation of Virtual PC virtual machines images before incorporating them into the
image repository. For the Trial Guide, readers of the document can create their own virtual machine or
download a prebuilt virtual machine. The prebuilt virtual machine is available at the following location so
that the reader will not have to create a virtual machine for the environment. Please choose one of the
two options for creating a Virtual PC image for MED-V.

OPTION 1: CREATING YOUR OWN VIRTUAL MACHINE REQUIREMENTS

 Host computer with Virtual PC 2007 SP1 and KB974918 installed (Software available from the MDOP
2010 Refresh DVD in the \MED-V\Installers\VPC2007_SP1 directory)

 Windows XP SP2 or SP3 32-bit Volume License Version (required)

 .NET Framework 2.0 SP1 or newer (required) available at:

http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-
A7633F706BA5&displaylang=en

 Virtual PC additions (required) need to be installed on the Virtual PC image being prepared for use in
MED-V.
Note: The virtual machine additions should only be installed after updating the host machine with
KB974918. This is an update to the virtual machine additions. If additions are currently installed on
virtual machine they will need to be updated.

 Additional software (optional): Applications can be installed that would be typical for a user.

 Install the MED-V Workspace software (MED-V Workspace_1.0.105.msi from the Installers
directory).

OPTION 2: USING THE PREBUILT VIRTUAL MACHINE

The prebuilt virtual machine for the Trial Guide is a Windows XP 32-bit machine that is running Internet
Explorer 6. This machine does not have any additional software installed. The reader of the guide might
want to add additional software to test real software from the production environment.

Prebuilt virtual machine available at:

http://www.microsoft.com/downloads/details.aspx?FamilyID=21eabb90-958f-4b64-b5f1-
73d0a413c8ef&DisplayLang=en
Note: Download the IE6-XPSP3.exe virtual machine from the link above.
The following tasks must be completed on the prebuilt virtual machine to enable use with the Trial Guide.

 After downloading and extracting the prebuilt virtual machine, create a new virtual machine using the
VHD file that was extracted.

 Start the virtual machine.

Note: Make sure you open the readme file in the directory the VHD was extracted to, as it contains
the password information for the virtual machine.

12
 Trial Guide

 Open the registry editor from within the prebuilt virtual machine.

 HKEY_CURRENT USER\Software\Microsoft\Windows\ Current Version\Policies \uninstall

o Delete the line "noaddremoveprograms."

 Add any optional software to simulate a normal user environment.

 Upgrade the virtual machine additions.

The Virtual PC 2007 virtual machine additions update (KB974918) is an updated version of the
default virtual machine additions included with Virtual PC 2007 SP1. This update is a required
update that needs to be installed on the MED-V Management machine with an existing instance of
Virtual PC 2007 SP1. After installing the update, the virtual machine that is being prepared will
have to be started and the virtual machine additions will have to be updated by choosing Actions |
Install or Update Virtual Machine Additions.

 Install the MED-V Workspace software (MED-V Workspace_1.0.105.msi from the Installers
directory).

 Create a new user and ensure that it has a password for use with the precreated web-based
Windows XP image.

Important: Leaving the virtual machine with Internet Explorer 6 will demonstrate a good example for the
use of MED-V. In many organizations, moving to Windows Vista and Windows 7 has been delayed due
to the dependencies on Internet Explorer 6. Using a virtual machine with Internet Explorer 6 will provide
a useful demonstration of web redirection where certain web sites can be configured in a workspace to
use the workspace (Windows XP) browser for certain sites that are not compatible with the host (Vista
and Windows 7) browser (Internet Explorer 8).

Note: Windows 2000 SP4 is also supported as a virtual machine for MED-V.

MANDATORY: IMAGE PREPARATION PROCEDURES

The MED-V Workspace will need to be installed in the virtual machine being prepared. This package
includes the Virtual Machine Prerequisites Tool that is executed to prepare the virtual machine. Use
the steps provided in the section Creating a Virtual PC Image for MED-V of the MED-V Planning,
Deployment, and Operations Guide to run the MED-V Virtual Machine Prerequisites Tool.

Note: When installing the MED-V Workspace in the prebuilt virtual machine, the administrator will be
prompted for the Windows XP installation files.

13
 Trial Guide

2.6 Importing a Policy to the Server

The initial installation of the MED-V Management Server includes a generic workspace policy. This
default policy requires additional configurations before the MEDV test environment is usable. A MED-V
policy is used to define a workspace, which is a virtual image associated with a set of usage policies and
provisioned to specific users. The following configurations are included in a usage policy:

 Provision the workspace to users and groups.

 Set usage policies (e.g., expiration, permissions to work offline) and data transfer permissions (e.g.,
file transfer, copy-paste, and printing) to various users and groups.

 List of applications from the virtual machine image made available to the end user through standard
desktop Start menu.

 List of web sites that should be viewed inside the virtual machine browser, and that are redirected
from the host browser to the virtual machine by the MED-V Client.
Using the MED-V Management Console, policies can be imported into the server. For the test
environment, a sample policy (TrialGuide_policy.xml) is provided and will be imported to demonstrate
MED-V functionality. The following steps import the sample policy that will be used throughout
the document:

POLICY IMPORT PROCEDURES

1. Open the MED-V Management Console from All Programs | MED-V Management.

2. Log on with a domain account.

3. Click the Policy button.

4. On the toolbar, click Policy | Import…

5. In the Import policy dialog, find and select the TrialGuide_Policy.xml and click Open.

6. Review the two workspaces that are part of the policy and click on Policy | Commit and Yes for
saving changes that are different from the default server policy.

Note: These workspaces will be modified and described in greater detail in section 4 of this document.

14
 Trial Guide

3 MED-V Administration
After successfully preparing a virtual machine for MED-V, the image will need to be configured and tested
before deploying to users. Using the MED-V Management Console, the image will enter the MED-V
image repository and the following tasks will be completed:

 Add the prepared MED-V image to the local test repository.

 Associate test Image with workspace policy.

 Test the MED-V image locally

 Pack the image.

These tasks are essential for developing a working test or production environment. The tasks described
in the following sections walk-through these tasks for ensuring successful image preparation and
configuration for a MED-V infrastructure.

3.1 Creating a MED-V Test Image

The first administrative task in creating a MED-V image is creating a local test image. This image can be
used locally and changes to the workspace settings can be made without affecting any users. Use the
virtual machine image that was prepared on the Management Server in the previous sections.

TEST IMAGE CREATION PROCEDURES

The following steps will take the prepared image and make it a local test Image:

1. Use the MED-V Management Console on the MED-V Client and select the Images button.

2. Under Local Test images select New and enter the following information:
a. Browse to the path for the prepared virtual machine image VMC file.
b. Enter a name: e.g., TrialGuideTest.

Detailed steps for this procedure are available in the MED-V Planning, Deployment, and Operations
Guide in the section How to Create and Test a MED-V Image.

15
 Trial Guide

3.2 Associate Test Image with Workspace Policy

The policy that was imported earlier in this document created two workspaces (TrialGuide and
TrialGuide_no_web_redirection). Before implementing those workspace policies with the new image in
production, test the workspace settings to ensure that they work properly. The following steps will describe
creating a test workspace:

TEST WORKSPACE CREATION PROCEDURES

1. Using the MED-V Management Console, select the Policy button.

2. Under Workspaces select TrialGuide.

3. On the Deployment tab ensure that Enable Workspace for Everyone is enabled.

4. Assign the MED-V test image to the TrialGuide workspace by doing the following:
a. Click the Virtual Machine tab.
b. In the Assigned Image field, select the MED-V test image you created. If your test image is not
in the list, click Refresh.

5. On the Applications tab, under Published Applications click Add and enter the following information:
a. Enabled: Checked
b. Display Name : XP Notepad
c. Command line: c:\windows\system32\notepad.exe

6. From the toolbar, click Save changes.

Detailed steps are available for creating a workspace in the MED-V Planning, Deployment, and
Operations Guide in the section Creating a MED-V Workspace.

16
 Trial Guide

3.3 Testing a MED-V Image Locally

The prepared image has now been entered into the local test repository on the Management Server and
a workspace has been associated to the image. The next step is to test the image and the workspace
settings together. The following steps will start the test image and allow for testing of the settings to
ensure that they are correct.

IMAGE TEST PROCEDURES

1. Start the MED-V Client and provide credentials for a local user.

2. When prompted, select the TrialGuide workspace and click on OK.

3. On the Confirm Running Test, choose Use Test Image.

4. After the test workspace is loaded (green check box on the MED-V icon in the Notification Area),
browse All Programs and note that XP Notepad is listed in MED-V Applications.

5. Shutdown the workspace by right clicking on the MED-V icon and selecting Stop Workspace.

3.4 Packing the MED-V Image

After successfully testing the image, the next step is to pack the image. Packing the image will make it
smaller for transport across the network or for including in an installation package used with removable
media. This process will take some time as MED-V is compressing and encrypting the image.

IMAGE PACKING PROCEDURES

1. In the MED-V Management Console click on the Images button.

2. Under Local Test Images, right-click TrialGuideTest and choose Pack test image.

17
 Trial Guide

4 Part 2: Evaluating Management Features of MED-V

To provide a managed, scalable solution for running virtual Windows XP applications, MED-V addresses
many of the IT challenges around deployment and management including:

 Deployment – deliver virtual Windows images and customize per user and device settings.

 Provisioning – define which applications and websites are available to different users.

 Control – assign and expire usage permissions and Virtual PC settings.

 Maintenance and Support - update images, monitor users and remotely troubleshoot.

4.1 Deploying a MED-V Workspace

In part one of the Trial Guide, a sample workspace was prepared and tested. In part two of the Trial
Guide we will use the image repository server to deliver the workspace to the MED-V Client to look at a
more production-based method of deploying the workspace. This guide will focus on using an image
repository server (IIS) to distribute MED-V packages.

UPLOADING THE PACKED IMAGE

In part two of the Trial Guide, the packed image created during part one will need to be uploaded to the
MED-V Server that was configured as an image repository server.

1. From the MED-V Client open the MED-V Management Console and select the Images button.

2. From the Local Packed Images area, right-click the TrialGuideTest image and choose Upload to
server.

3. Open the MED-V Management Console and select Policy.

a. Select the TrialGuide workspace and the Virtual Machine tab.

b. Select Refresh and select the TrialGuideTest (server) image and save the policy.

4.2 Changing Trial Guide Settings

This section will focus on configuring settings in the workspace usage policies, and the next section will
demonstrate how these changes influence the workspace. This description will provide definition and
changes for commonly configured settings. Previously in this document, a policy was imported that had
two workspaces defined. The following steps, using the imported policy, are a walk-through of common
MED-V Workspace settings.

18
 Trial Guide

4.3 General Tab

Configuring workspace policies allows the administrator the capability of affecting how the image and
applications interact with the host machine. There are two options for the end user experience, which are
configured on the General Tab. Seamless Integration brings all the legacy applications onto the host
desktop so they behave as if they were installed directly on the host. Full Desktop presents the entire
desktop of the workspace guest OS in a separate window on the host.

Use the two workspace policies that were imported earlier to review and modify the Workspace UI settings.

GENERAL TAB PROCEDURES

1. Use the MED-V Management Console to review the settings for both the TrialGuide and
TrialGuide_no_web_redirection policies.

2. From the General tab, change the setting for the TrialGuide_no_web_redirection policy from
Seamless Integration to Full Desktop.

3. Click Save Changes.

4.4 Virtual machine - Assigned Image Tab

This tab is used to bind the workspace policies with the inducted base image. Click Refresh to update the
list of available images. Select the appropriate local image to associate with the Legacy Application
Workspace. Assign the workspaces to the image that was packaged and uploaded to the server in
previous steps.

VIRTUAL MACHINES TAB PROCEDURES

Use the MED-V Management Console to change the Virtual Machine | Assigned Image to the
TrialGuideTest(server) image for both the TrialGuide and TrialGuide_no_web_redirection
workspace policies.

19
 Trial Guide

4.5 Applications Tab

The applications tab can be configured to have specific applications and entire menus be published from
the workspace to the host computer. When using seamless integration, the published applications and
menus will appear in All Programs | MED-V Applications folder.

On the Applications tab, review the published applications and menus. These may not all be present in
the image that was created. However, several are Windows components and will be present.

APPLICATIONS TAB PROCEDURES

®
Add the Outlook Express (―C:\Program Files\Outlook Express\msimn.exe”) application to the list for
both policies (TrialGuide and TrialGuide_no_web_redirection).

4.6 Web Tab

The web tab can be used to configure specific web sites to use either the host or the workspace browser.
This feature will allow administrators to identify sites that only work in older versions of the browser to be
run from the legacy workspace browser instead of the host’s incompatible browser.

WEB TAB PROCEDURES

1. Verify the TrialGuide policy is enabled so that medvdemo.com will browse from the workspace.

2. Add a second web site that will be used within the workspace browser.

4.7 VM Setup Tab

The VM Setup tab enables an administrator to configure the image to perform tasks to further configure
the virtual machine. The image is based off of a single virtual machine that will be used by numerous
users, so renaming the virtual machine is essential for proper operation on the network.

VM SETUP TAB PROCEDURES (OPTIONAL)

1. Review and modify (optional) the VM Computer Name Pattern for both of the policies.

2. Ensure that a Computer Restart task is added after the computers rename operation.

4.8 Network Tab

The Network tab configures the network settings in the image. By default, the network will be configured
for Network Address Translation (NAT). In environments where it is required, the network setting can be
adjusted to include the following settings:

 Bridged and multiple network adapters

 DNS – manual or automatic assignment

 DNS Suffixes
Review both policies and the network settings.

20
 Trial Guide

4.9 Deployment Tab

The deployment tab controls many usage-based requirements. This allows an administrator to control
who can have access to the workspace and also, optionally, how long it can be used for and whether or
not it can be used offline.

Additional usage policies for controlling access between the workspace and the host are as follows:

 Clipboard between the workspace and host.

 File transfer between the workspace and host. This can be configured in one direction or both.

 Printing from the workspace to the host.

 Access to CD/DVD drive on the host from the workspace.

DEPLOYMENT TAB PROCEDURES

1. In the TrialGuide workspace under Device Control, check Enable printing to printers connected
to the host.

2. In the TrialGuide_no_web_redirection workspace under General, check Enable Workspace

for ‘Everyone’.

4.10 Performance Tab

The workspace policies Performance tab adjusts the virtual machine memory allocation based on the
amount of physical memory on the host computer. These settings can be adjusted to address all
configurations and provide acceptable levels of performance for the workspace and host.

On both workspace policies, add an additional virtual machine memory configuration and modify it with
the following information:

 Host Memory : Above 2200 MB

 VM Memory : Assign 512 MB

Important: Ensure after completing all of these steps that you click on Save Changes or Policy | Commit.

21
 Trial Guide

5 Testing the MED-V Client and Workspaces

This section of the Trial Guide will use all of the steps and settings that have been imported or configured
in this document and test a working MED-V installation. The following table will outline tasks to be
performed and what the expected result for the feature is for the user.

START THE WORKSPACE

Now that everything has been prepared, a user on the MED-V Client can start the MED-V Workspace.
The process will download the image from the image repository server and be configured per the
TrialGuide policy.

1. Launch the MED-V Client program and log on to begin the download of the workspace image.

2. After the workspace launches, verify that the workspace is running properly by running some of the
MED-V applications or testing some internet sites that are configured to use the workspace in the
policy.

Feature Explanation Test

Authentication In the trial environment two Start the MED-V Client and log on with
and choosing workspaces were assigned to the a local account. When prompted
a workspace same image. This feature will show choose the TrialGuide workspace.
how to authenticate and then choose
the appropriate workspace.

First Time Setup This feature occurs on the initial This feature automatically occurs and
launch of the virtual machine to make will require no user interaction.
any necessary adjustments to the
virtual machine, including network
settings and assigning a unique ID.
This one-time process is skipped
during subsequent runs.

Seamless The TrialGuide workspace, which is Go to Start menu | All Programs |

Applications configured for seamless UI, will MED-V Applications | Outlook
present applications in the user’s Express. This will launch Outlook
Start menu. The policy that was Express from the TrialGuide
imported earlier contained a list of Workspace.
applications that are published to the Note: Even the notification area icon
end user. for Outlook Express will be present on
the host machine and can be used.

22
 Trial Guide

Feature Explanation Test

Web Redirection The TrialGuide workspace is Open Internet Explorer on the host
configured to redirect any web machine. This will be Internet Explorer 8.
request for www.medvdemo.com and Type http://www.medvdemo.com in the
another user-configured web site to address bar and Click on Go or
use the workspace browser. This hit Enter.
feature will redirect any request for
these sites to the workspace browser. A new Internet Explorer window should
open and display the web page. Check
to see that this is the web browser
from the TrialGuide workspace (IE 6).

Printing from Based on the administrator-defined Open an application from the

the Workspace policy, the user may print workspace workspace and choose print. The user
documents using any local or network will be prompted to select a printer
printer that is connected to the host, configured on the host.
without installing the printer in the
virtual machine. Note: A printer could be installed in the
virtual machine image to allow printing.

File Transfer Based on the administrator- Right click the MED-V icon in the
configured workspace policy, file Notification area and select
transfers can be enabled between the Tools | File Transfer.
workspace and host computers. This
configuration can be a one-way or Copy files from the workspace to the
two-way operation. host computer and from the host
computer to the workspace.
The TrialGuide workspace is
configured to allow for two-way file
transfers from the workspace and
host computers.

Clipboard The workspace settings can be Open Internet Explorer from the MED-V
enabled to allow sharing of the Workspace and browse to a web site.
clipboard between the workspace and
host. The TrialGuide workspace was Open notepad on the local host
configured to allow for clipboard computer.
sharing.
Perform a copy and paste from
Internet Explorer to notepad.

23
 Trial Guide

Feature Explanation Test

Workspace Lock Based on administrator-configured Wait for 5 minutes. The workspace

workspace policy, a workspace can dialogue will present itself asking for
be configured to lock after a period of credentials to continue using the
time. This will prompt the user for workspace.
credentials again as when they
started the workspace.

Working Offline Workspace policies can be configured Stop the TrialGuide Workspace by
to allow for the offline usage of a right clicking the MED-V icon in the
workspace. This will allow users to Notification area.
use the workspace when they are
away from the MED-V Server. The Open Services on the host computer
TrialGuide workspace was enabled and stop the MED-V Server.
for offline usage.
Next, start the TrialGuide workspace.

Note: This is only for lab purposes;

normally a user would be connected to
the server on the network. The service
would not be shut down for offline
usage.

Full Desktop UI This feature is configured as part of a Shutdown the TrialGuide workspace if
workspace policy and enables users to it is running.
have access to the entire workspace
desktop and not just the applications Start the workspace again, choosing
that have been published. the TrialGuide_no_web_redirection

Notice full Windows XP desktop

presented to the user.

5.1 Provisioning MED-V

MED-V provides management features to reduce the number of workspace images that are required to
support an organization. MED-V allows administrators to create multiple policies for one workspace
image and assign different user accounts or groups to different policies. Those policies can be assigned
different settings, applications, and the other settings outlined earlier in this document.

CONFIGURING DIFFERENT APPLICATIONS TO DIFFERENT WORKSPACE USERS

The following tasks should be completed to configure different applications to different users of the same
workspace.
®
1. From the MED-V Server, create two user accounts in Active Directory .

2. From the MED-V Client, open the MED-V Management Console and select Policy.

24
 Trial Guide

3. Right-click the TrialGuide policy and choose Clone and note the name of the cloned policy.

4. Assign the two user accounts to the two different policies and remove Everyone.

5. Modify the applications assigned to each of the policies and verify that they are using the same
Virtual Machine image.

6. Save the policy.

7. If a current MED-V workspace is running, stop the workspace.

8. Start the MED-V workspace and log on as the user associated with the original policy.

9. After the workspace is running, verify the applications available.

10. Repeat the steps logging on as the user account assigned the cloned policy, and note the differences
in available applications.

Assigning different users or groups to multiple policies will allow organizations to create fewer workspace
images and reduce the management of MED-V.

5.2 Expiring a MED-V Workspace

Removing a MED-V workspace may be required to decommission a workspace when it is no longer
necessary. There are two ways that workspace expiration can be configured. The first example is to
specify the workspace policy with an expiration date. This is useful when the administrators know how
long the workspace should be active. The second option is to delete the workspace policy for immediate
expiration of the workspace.

The second option will be explored as it is much easier to simulate than waiting for a future date. Perform
the following tasks to immediately expire a workspace.

 Ensure that the workspace being used on the MED-V Client is the one associated with the
cloned policy.

 Open the MED-V Management console and select the cloned policy, delete it, and save the
policy change.

 From the notification area, right-click the MED-V icon and select Workspace Diagnostics.

 Refresh the policy. A message should be presented that the workspace has expired and can be
shut down or it will be shut down in two minutes.

5.3 MED-V Workspace Domain Join

MED-V allows administrators to customize every deployment of a virtual image. This procedure can
include allocating a unique computer name for the virtual image (according to user name, endpoint
parameters, or simply a random ID) so that, for instance, administrators can assign the virtual machine an

25
 Trial Guide

identifier that is based on the host computer name, and therefore easily identify this virtual machine in
software management systems. Other customizations include Sysprep to allocate a unique SID for the
virtual machine, joining the virtual machine to the corporate Active Directory domain, or running an
administrator script.

Using MED-V to join the workspace to the Active Directory is recommended to allow for proper
management of the workspace with the current infrastructure tools and policies. Joining each workspace
to the domain will allow for it to be managed like any other desktop in the infrastructure. This will include
any security based software (anti-virus, anti-malware, etc,) as well as Group Policies that are typically
managing the current infrastructure. Updating the workspace can be accomplished by installing any
management tools (software distribution agents: e.g., System Center Configuration Manager, or other
third-party tools) that are typically used to keep any other desktop up to date.

The MED-V Client handles first-time setup automatically and transparently for the end user, including
repeating failed steps or the whole process, and reporting back to the Management Server in case
troubleshooting is required.

The first-time setup behavior is controlled by using the virtual machine setup settings in the workspace
policies. The following steps can be completed to customize the deployment of a workspace image after
it is delivered to the MED-V Client.

VIRTUAL MACHINE SETUP FOR FIRST-TIME SETUP

From the MED-V Client in Virtual PC

1. Start Virtual PC and start the virtual machine that was used to create the workspace image.

Note: All workspaces must be stopped prior to starting Virtual PC.

2. Log in to the virtual machine.

3. Create a directory at the root of the system drive called sysprep.

4. Extract the deployment tools from the deploy.cab file located in the Support\Tools directory of a
Windows XP CD or download the deployment tools located at:
http://www.microsoft.com/downloads/details.aspx?FamilyID=3e90dc91-ac56-4665-949b-
beda3080e0f6&displaylang=en&Hash=Dn4VPlbkx2owVcc2oY1NXDRuDtLi2ZedF3tcf4V%2fox5ct%2f
MYSuYgzdFteqWOodt2AWgZ2PvKTRMYnc4dfNA%2fNA%3d%3d to the sysprep directory created
in the step above.

5. From the sysprep directory, launch the setupmgr.exe program.

6. Click Next on the Welcome screen.

7. Select Create new and then click Next on the New or Existing Answer File.

8. Select Sysprep setup on the Type of Setup screen and click Next.

9. On the Product screen, select Windows XP Professional and click Next.

26
 Trial Guide

10. On the License Agreement screen, select Yes, fully automate the installation and click Next.

11. Complete the answer file questions with the following information:

a. Name and Organization: Enter the name and organization appropriate for destination
computers.

b. Display Settings: Leave the defaults.

c. Time Zone: Select the appropriate time for destination computers.

d. Product Key: Enter valid Volume License Product Key.

NOTE: The product key is not validated in this form and you will not be warned if entered
incorrectly. Make sure to check to ensure that the key is correct.

e. Computer Name: Select Automatically generate computer name.

f. Administrator Password: Select Use the following Administrator password and

type the password for the Administrator account on all destination computers. Also,
select When a destination computer starts, automatically log on as Administrator
and set the Number of times to log on automatically to 99.

g. Networking Components: Select Typical Settings.

h. Workgroup or Domain: Select Workgroup.

i. Telephony: Click Next, unless telephony settings are required by an application in the
workspace. If required, set the appropriate settings.

j. Regional Settings: Click Next, unless specific regional settings are required.

k. Languages: Select any languages required to support end users.

l. Install Printers: Click Next, unless there are printers required to support the workspace.

m. Run Once: Click Next, unless there are commands required to support the workspace.

n. Additional Commands: Click Next, unless there are commands required to support the
workspace.

o. Identification String: No text is required but this text can be used later to identify
machines created with this script.

12. After completing the answer file select Finish. A message box appears stating that Setup Manager
created an answer file with the settings provided.

27
 Trial Guide

13. Save the answer file in the C:\sysprep directory created earlier and select OK. Click cancel on the
Setup Manager screen or File and Exit.

14. From the Sysprep folder located in the root of the system drive, execute the System Preparation Tool
(Sysprep.exe).

15. Select OK when the warning prompt appears.

16. The Sysprep Properties dialog appears.

a. Select Don’t reset grace period for activation.

b. Select Use Mini-Setup.

17. Click Reseal. A confirmation prompt appears. Select OK. Sysprep will complete and the machine
will shut down.

Open MED-V Management Console.

18. From the MED-V Management Console go to Images and select New in Local Packed Images:.
Browse to the VMC file of the virtual machine that sysprep was on and type in the Image name
TrialGuideFinal and click OK.

19. Under Local Test Images, right-click TrialGuideFinal and choose Pack Final Image.

20. After the packing operation is complete, right-click the new packed image and select Upload to
Server.

21. From the MED-V Management console, go to Policy and clone the TrialGuide policy and rename it
TrialGuideFinalPolicy.

22. From the Virtual Machines tab of the TrialGuideFinalPolicy, update the following settings:

a. Assigned Image set to TrialGuideFinal (server).

b. Select Logon to Windows in VM using MED-V credentials (SSO).

c. Select Synchronize Workspace time zone with host.

23. Assign the user that was assigned to the previous cloned policy and delete everyone from the
Deployment tab.

24. Select VM Setup and ensure that Run VM Setup is checked.

25. Modify the VM Computer Name Pattern by placing the cursor at the end of the name and then
clicking Insert Variable and select User Name.

28
 Trial Guide

26. Launch the Script Editor and note that Rename Computer and Restart Windows are in the list. If
they are not, add them with Rename Computer above Restart Windows.

27. Enable adding the workspace to the test domain.

a. Select Join Domain from the Script Actions area and use the following settings:

i. Credentials to use when joining the virtual machine to the domain: Use the
following Credentials:

1. Specify a valid user name and password: Domain\Username and

Password that can join computers to the domain.

ii. Domain to join: Use the following domain name.

1. Specify the Domain Name both fully qualified (contoso.com) and

NetBios (contoso).

28. Save the policy.

29. Delete any current images from c:\MED-V Images on the MED-V Client.

30. Start the workspace with the user account associated with the cloned policy that has the new VM
setup options.

31. Select Details from the Workspace Setup screen to view the tasks that are being performed.

32. Go to Start | MED-V | Tools and start MED-V Diagnostics Tool.

33. Select Enable diagnostic mode.

NOTE: Enable diagnostic mode will allow you to see the first-time setup of the virtual machine. At any
time you can choose to disable diagnostic mode and it will hide the virtual machine from view.

34. After the workspace is running, launch the MED-V Management Console and select Reports.

35. Generate the Status report and use the default of 7 days.

36. View the Workspace Computer Name field. After the first-time setup is completed this value will be
the new computer name of the MED-V Workspace. If you run this before completion of first time
setup you may need to refresh the report.

29
 Trial Guide

6 Demonstrating Troubleshooting Capabilities of MED-V

In the event that there are problems with starting, downloading, or running a workspace on a MED-V
client there are several tools that can be used to troubleshoot the environment.

6.1 Settings Menu

The settings menu that is available by right-clicking the MED-V icon in the Notification area will allow
support personnel to modify the MED-V Client settings. The following settings are available:

 Start Options

 Load on Windows Startup (MED-V Client)

o Automatically start Workspace

 Server Properties

 Server Address (IP or Host name of MED-V Management Server)

 Server port (Option for using secure HTTPS connections)

6.2 Diagnostics
The diagnostics screen is available from the MED-V icon help MED-V diagnostics in the Notification
Area. This screen will show information about the host system, the policy that is on the client, workspace
information, and the image store. Direct links to the following tools is available:

 Gather Diagnostics Logs: This tool is also available thought the Start menu and will capture all
diagnostics logs and create a compressed archive on the desktop.

 Update Policy: This will initiate a refresh of the policy from the server.

 Enable diagnostic mode: Shows a seamless workspace in a virtual machine window for
troubleshooting. However, it doesn’t present a user-friendly interface. It is only used for
troubleshooting where the workspace appears to be hung and this would reveal any dialogues or user
input screens.

 Browse Image Store: This opens the directory where the images are stored.

6.3 Diagnostic Reports

If the server has been configured with a SQL Server and a reporting database has been created, there
will be reports that can be run for status, activity, and errors. Viewing these reports is available in the
MED-V Management Console.

30
 Trial Guide

6.4 Create a MED-V Installation Package

The deployment package installation provides a method of installing MED-V Client together with all its
required prerequisites as well as any settings pre-defined by the administrator.

The Packaging wizard walks you through the creation of a package by creating a folder on your local
computer and transferring all the required installation files to the single folder. The contents of the folder
can then be moved to multiple removable media drives for distribution.

The Evaluation Guide focused on setting up a working MED-V environment to demonstrate management
capabilities. In a production environment with many computers, administrators will also have to deploy the
client installation files and images. This guide has provided the detailed steps to perform this using an
image repository server. An alternate way is to create installation packages that include Virtual PC,
Virtual PC hotfix, MED-V Client, and packed image. These packages can be placed on removable media
or made available on file server or web servers for alternate distribution. As mentioned earlier in this
document, the MED-V Planning, Deployment and Operations Guide provides detailed descriptions of
creating a MED-V Installation Package (with or without an image) in the section How to Pack a MED-V
Image).

CREATE MED-V INSTALLATION PACKAGE

Use the guidance in the MED-V Planning, Deployment, and Operations Guide in the section How to
Pack a MED-V Image to create a MED-V installation package that has the following components:

 Virtual PC 2007 SP1

 Hotfix package for Virtual PC2007 SP1

 .NET Framework 2.0 SP1

 MED-V Client

This package will include everything required to install a MED-V Client. It can include a packed image.
This package could be used to install all the necessary components for a MED-V Client as well as any
settings from the administrator. This package could be placed on a removable drive. If a packed image
was included, that would also populate the first workspace image so it would not need to be downloaded
prior to running.

6.5 Monitoring and Troubleshooting

In the event that there are problems with starting, downloading, or running a workspace on a MED-V
Client there are several tools that can be used to troubleshoot the environment.

SETTINGS MENU
The settings menu that is available by right-clicking the MED-V icon in the Notification area will allow
support personnel to modify the MED-V Client settings. The following settings are available:

31
 Trial Guide

 Start Options

 Load on Windows Startup (MED-V Client)

o Automatically start workspace

 Server Properties

 Server Address (IP or host name of MED-V Management Server)

 Server Port (Option for using secure HTTPS connections)

DIAGNOSTICS
The diagnostics screen is available from the MED-V icon  help  MED-V diagnostics in the Notification
Area. This screen will show information about the host system, the policy that is on the client, workspace
information, and the image store. Direct links to the following tools is available:

 Gather Diagnostics Logs: This tool is also available through the Start menu and will capture all
diagnostics logs and create a compressed archive on the desktop.

 Update Policy: This will initiate a refresh of the policy from the server.

 Enable Diagnostic Mode: Shows a seamless workspace in a virtual machine window for
troubleshooting. However, it doesn’t present a user-friendly interface. It is only used for
troubleshooting where the workspace appears to be hung and this would reveal any dialogues or
user input screens.

 Browse Image Store: This opens the directory where the images are stored.

6.6 Diagnostic Reports

There are three types of reports that can be created by administrators in MED-V:

 Status - Use the status report to review the current status of all active users and all workspaces
of each user based on a defined period of time. This includes viewing machines that are currently
connected to the server, or if they are not currently connected, the date and time they were last
connected to the server, the status of each machine, and other relevant information.

 Activity Log - Use this report to review specific workspace events in a defined date range.

 Error Log - Use this report to view specific workspace errors in a defined date range.

The report results can be sorted by any column by clicking the appropriate column name.

The report results can be grouped by dragging a column header to the top of the report. Drag multiple
column headers to group one column after another. Additional details on specific reports and how to
generate are available in Section 10 of the MED-V Planning, Deployment and Operations Guide.

32
 Trial Guide

7 Next Steps
The test environment that was created in this guide was optimized to showcase the management features
utilizing minimal time and minimal hardware usage. The goal of this guide was to allow an IT Pro to
quickly evaluate the features of MED-V and provide a test environment for an organization.

Next, an IT Pro will need to perform additional tasks to prepare for a pilot or production environment.
Also, additional preparation for images and additional configuration options are available for production
environments.

7.1 Planning a Full Infrastructure

After completing the Evaluation Guide, the next step is to begin planning your infrastructure. Please
reference the following materials to help you plan the environment.

Microsoft Enterprise Desktop Virtualization Infrastructure Planning and Design Guide at:
http://download.microsoft.com/download/5/B/C/5BC966BC-47D8-41DF-95F2-FA9A2D816258/MED-V.zip

Microsoft Enterprise Desktop Virtualization Architecture Guide at:

http://www.microsoft.com/med-v

http://www.microsoft.com/technet/mdop

33