MED-V: Installing server and client components

Learn the steps for installing and configuring the Microsoft Enterprise Desktop Virtualization (MED-V) server and client components and check out MED-V's system requirements.

Solutions provider takeaway: Installing Microsoft Enterprise Desktop Virtualization (MED-V) properly for your customers requires you to have a good understanding of how to install both the server and client components in a MED-V environment. Follow these server and client installation steps to ensure your MED-V installation goes smoothly. You will also learn the steps to configure the MED-V server components.

About the book
This chapter excerpt on Deploying Microsoft Enterprise Desktop Virtualization (download PDF) is taken from the book Mastering Microsoft Virtualization.

Solutions providers will get detailed information on Microsoft's virtualization products and expert advice on how to deploy a complete virtualization stack with Microsoft's server virtualization offerings. This book also covers topics such as Hyper-V in Windows Server 2008 R2, installing and configuring Remote Desktop Services and the best practices for working with virtualized desktop infrastructures.

Installing the MED-V Solution

The process of implementing the MED-V solution consists of installing and configuring several Microsoft software services on servers running Windows Server 2008 and personal computers running Windows Vista or Windows XP operating system. In the next two sections we will review the main installation steps required to be performed on the servers and clients that make up the MED-V solution. Figure 16.2 shows an example of the MED-V solution architecture that we will be installing.

Figure 16.2 Simple MED-V solution architecture

The architecture used for this MED-V solution example consists of three servers and three clients. The reason for using three servers is to provide an example of how to isolate the required server components — MED-V Management Server, Web/Repository Server, and SQL Server — on separate servers. This may be useful in supporting scenarios that require higher performance, greater scalability, and distributed client locations. It is possible to implement all of the MED-V server components on one server running on a single instance of the server operating system or distributed on VMs, as we did for our POC.

The system requirements for the MED-V version 1 are listed in Table 16.1. For the latest MED-V information, please review the Microsoft MED-V website at www.microsoft.com/medv.

We're making a key assumption regarding the existence of infrastructure services that are needed to support this solution, that is, AD, DNS, and DHCP. A list of the servers and clients used in this installation example is provided below. In addition, other Microsoft products, technologies, and updates may also need to be installed either before or during the installation of the solution components. Examples of these include .NET Framework 3.0 SP 1, Windows Installer 4.5, and the SQL Server Native Client and SQL Server Management Objects. Please refer to the Microsoft Windows Server 2008, MED-V, Windows Vista, and Windows XP installation instructions related to prerequisites for more information.

Servers

For this solution example, we will use three Windows Servers named ServerA, ServerB, and ServerC. A description of each server follows.

ServerA Image Repository Server, running Windows Server 2008 (32- or 64-bit), Web Server (IIS), and BITS Server Extensions. This server provides the platform to store and deploy MED-V Workspace images to MED-V clients.

ServerB Database Server, running Windows Server 2008, SQL Server 2008 (32- or 64-bit). This server provides the database that is used to store MED-V client information that is collected by the MED-V Management Server. Reports can then be created from this data.

ServerC MED-V Server, running Windows Server 2008 (32- or 64-bit), MED-V Management Server V1. This server stores MED-V Server settings and Workspace policies, communicates with Active Directory to assign users and groups to Workspace images, authenticates and authorizes MED-V clients, and manages policy and Workspace deployment and updates.

Table 16.1: MED-V system requirements

Management Server
Processor Dual processor, 2.8 GHz.
Memory 4 GB RAM.
Operating system Windows Server 2008 Standard or Enterprise.
Database Microsoft SQL Server 2005 Enterprise SP2 or Microsoft SQL Server 2008 Express, Standard, or Enterprise.
Repository Server
Web server Microsoft IIS.
File server Windows Server 2008. Note that disk space requirements are determined by the size and number of VM images that will be stored in the repository.
Client System
Memory 1 GB for Windows XP, 2 GB for Windows Vista.
Disk space Note that disk space requirements are determined by the size and number of guest VMs.
Host OS Windows XP SP2/SP3 (32-bit), Windows Vista SP1/SP2 (32-bit)
Guest OS Windows 2000 SP4 (32-bit), Windows XP SP2/SP3 (32-bit).
Desktop virtualization software Microsoft Virtual PC 2007 SP1.

Personal Computers

For this solution example, we will use three Windows PCs named PC1, PC2, and PC3. A description of each PC is provided below.

PC1 MED-V Client and Management Console, running Windows Vista SP2 (32-bit) and MED-V Client and Management Console software. This personal computer will be used to manage the MED-V environment and test MED-V Workspace images.

PC2 MED-V Client running Windows Vista SP2 (32-bit) and MED-V Client software. This personal computer will be used to download and run MED-V Workspaces.

PC3 MED-V Client running Windows XP SP3 (32-bit) and MED-V Client software. This personal computer will be used to download and run MED-V Workspaces.

Installation of the MED-V Solution Server Components

The server architecture used for this MED-V solution example comprises three servers: ServerA, the Image Repository Server; ServerB, the Database Server; and ServerC, the MED-V Management Server. The installation process begins with installing IIS and BITS Server Extensions on ServerA. The next step is to install SQL Server 2008 Express on ServerB. We then install the MED-V Management Server on ServerC. Administrator rights are required for all of these operations. As mentioned before, a key assumption made regarding the installation environment is the existence of AD, DNS, and DHCP infrastructure services that are required to support this solution. A flowchart of the server installation process is shown in Figure 16.3.

Figure 16.3 MED-V Server installation process flowchart

ServerA — Image Repository Server

The first installation step is to install the Windows Server 2008 (32- or 64-bit) on this server. Installation instructions for Windows Server 2008 can be found on technet.microsoft.com.

The second installation step is to add the Web Server/Internet Information Service (IIS) role. The instructions for installing Internet Information Server are listed below:

  1. Open Windows Server 2008 Server Manager on ServerA.
  2. Select Roles on the Server Manager hierarchy.
  3. On the Roles Summary page, select Add Roles.
  4. Review the Before You Begin page and click Next.
  5. On the Select Server Roles page, select the Web Server (IIS) check box. Click the Add Required Features For Web Server (IIS) pop-up screen, and click Next.
  6. Review the Introduction To Web Server (IIS) page, and click Next.
  7. On the Select Role Services page, under the Security section, select Basic Authentication, Windows Authentication, and Client Certificate Mapping Authentication, and click Next.
  8. On the Confirm Installation Selections page, review the results and click Install. The installation process will begin.
  9. On the Installation Results page, review the results and click Close.

The third installation step adds the BITS Server Extensions feature to the server. The steps for installing this feature are as follows:

  1. Open Windows Server 2008 Server Manager on ServerA.
  2. Select Features on the Server Manager hierarchy.
  3. On the Features Summary page, click Add Feature.
  4. On the Select Features page, select the BITS Server Extensions check box. The Add Role Services Required For Background Intelligent Transfer Service (BITS)? pop-up screen will appear. Click Add Required Role Services, and then click Next.
  5. On the Introduction To Web Server (IIS) page, click Next.
  6. On the Select Role Services page, click Next.
  7. On the Confirm Installation Selections page, review the results and click Install. The installation process will begin.
  8. On the Installation Results page, review the results and click Close.

The installation steps for ServerA, the Image Repository Server are now complete. The con-figuration steps for this server are provided in the upcoming section called ''Configuration of the MED-V Solution Server Components.''

ServerB — Database Server

The first step is to install the Windows Server 2008 (32- or 64-bit) on this server. Installation information for Windows Server 2008 can be found on technet.microsoft.com.

The second step is to install SQL Server. For this installation example we will use SQL Server 2008 Express. Note that SQL Server 2005 Enterprise and SQL Server 2008 Standard and Enterprise may also be used and are a better choice for production deployments. The steps for installing the SQL Server 2008 Express are listed below:

  1. Install .NET Framework 3.0 SP 1. SQL Server 2008 Express Setup requires .NET Framework 3.0 SP1 to be installed. .NET Framework 3.0 SP1 can be downloaded at www.microsoft.com/downloads.
  2. Install Windows Installer 4.5. SQL Server 2008 Express Setup requires Windows Installer 4.5 to be installed. Windows Installer 4.5 can be downloaded at www.microsoft.com/downloads.
  3. The next step is to install SQL Server 2008 Express. SQL Server 2008 Express can be down-loaded from www.microsoft.com/downloads. Follow these installation steps:
    1. Run SQL Server Express Setup.
    2. On the SQL Server Installation Center page, select Installation.
    3. Select New SQL Server Stand-alone Installation or Add Features To An Existing Installation. The Setup Support Rules process will run and identify any problems. If any failures are identified, correct the issues and rerun this process. If no problems are identified, click OK.
    4. On the Product Key page, click Next since SQL Server Express is a free product.
    5. Review the License Terms, and if you accept them, select the I Accept The License Terms check box.
    6. On the Setup Support Files page, click Install.
    7. For the Setup Support Rules step, see if failures were identified. If failures were identified, correct the issues and rerun this process. If no problems were identified, click Next.
    8. For the Feature Selection step, select the Database Engine Services check box and click Next.
    9. For the Instance Configuration step, accept the default settings and click Next.
    10. For the Disk Space Requirements step, review the disk usage summary and click Next.
    11. For the Server Configuration step, there are two tabs: Service Accounts and Collation. For Service Accounts, select NT Authority → System from the Account Name drop-down list. Accept the default setting for SQL Server Browser. For the Collation settings, accept the defaults. Click Next.
    12. For the Database Engine Configuration, Account Provisioning, select Mixed Mode, and enter a password for the built-in SQL Server administrator account (SA). Specify SQL Server administrators by clicking Add Current User. Accept the default settings for Data Directories, User Instances, and FILESTREAM, and click Next.
    13. For the Error And Usage Reporting step, accept the default settings and click Next.
    14. For the Installation Rules step, see if failures were identified. If failures were identified, correct the issues and rerun this process. If no problems were identified, click Next.
    15. Review the Ready To Install information and click Install. The installation process will begin.
    16. When the installation has completed successfully, click Next.
    17. Review the information on the completed page, and click Close.

    The installation steps for ServerB, the Database Server are now complete. The configuration steps for this server are provided in the upcoming section called ''Configuration of the MED-V Solution Server Components.''

ServerC — MED-V Management Server

The first step is to install Windows Server 2008 (32- or 64-bit) on this server. Installation instructions for Windows Server 2008 can be found on technet.microsoft.com.

The next step is to install the MED-V Management Server. The steps for installing the MED-V Management Server V1 are listed below.

  1. Run the appropriate MED-V Server Windows Installer package, MED-V_serverx_86_1.0.72.msi for x86 or MED-V_server_x64_1.0.72.msi for x64.
  2. Review the MED-V Server Installation Wizard Welcome screen, and click Next.
  3. Review the MED-V License Agreement. If you accept the licensing terms, click Next.
  4. Review the Install Destination Folder setting, and click Next.
  5. On the Ready To Install The Program screen, click Install.
  6. 1.
  7. On the MED-V Wizard Completed screen, deselect Launch MED-V Server Configuration Manager, and click Finish.
  8. 2.
  9. The next steps are to install the SQL Server Native Client and SQL Server Management Objects. The Microsoft SQL Server 2008 Feature Pack includes SQL Server Native Client and SQL Server Management Objects and can be downloaded at www.microsoft.com/downloads.
    1. Install SQL Server Native Client by running the file sqlcli.msi. Follow the Installation Wizard instructions, accepting all defaults.
    2. Install SQL Server Management Objects by running the file SharedManagementObjects.msi. Follow the Installation Wizard instructions, accepting all defaults.
About the authors
Tim Cerling is a senior technology specialist at Microsoft with more than 10 years experience and a focus on Hyper-V.

Jeff Buller is a virtualization specialist on Microsoft's virtualization solutions team.

The installation steps for ServerC, the MED-V Management Server, are now complete. The configuration steps for this server are provided in the upcoming section called ''Configuration of the MED-V Solution Server Components.''

Installation of the MED-V Solution Client Components

The client architecture used for this MED-V solution example includes three personal computers: PC1, PC2, and PC3. Each personal computer requires the installation of a supported Microsoft Windows Client operating system along with the MED-V Client software.

PC1 — Windows Vista MED-V Client and Management Console

The installation process for PC1 includes installing Windows Vista SP 2 and the MED-V Client and Management Console software. Follow the installation steps listed below.

  1. Install Windows Vista SP 2 (32-bit).
  2. Install Microsoft Virtual PC 2007 SP1 and KB 958162 Update. You can download these from www.microsoft.com/downloads.
  3. Install the MED-V Client and Management Console software.
    1. Run the MED-V Client Windows Installer package named MED-V_1.0.72.msi.
    2. Review the MED-V Client Installation Wizard Welcome screen, and click Next.
    3. Review the MED-V License Agreement. If you accept the licensing terms, click Next.
    4. Review the Install Destination Folder setting, and click Next.
    5. On the MED-V Settings screen, put checkmarks next to Install The MED-V Management Application, Load MED-V When Windows Starts, and Add A MED-V Shortcut To My Desktop. Enter the correct server address and port for your MED-V Server. Accept the default directory to store the MED-V virtual machines. Click Next.
    6. On the Ready To Install The Program screen, click Install. The MED-V Client and Management Console software will now be installed.
    7. On the MED-V Wizard Completed screen, deselect Launch MED-V Enterprise Desktop Virtualization, and click Finish.

PC2 — Windows Vista MED-V Client

The installation process for PC2 will include installing Windows Vista SP 2 and MED-V Client software. Follow the installation steps listed here:

  1. Install Windows Vista SP 2 (32-bit).
  2. Install Microsoft Virtual PC 2007 SP1and KB 958162 Update.
  3. Install the MED-V Client.
    1. Run the MED-V Client Windows Installer package named MED-V_1.0.72.msi.
    2. Review the MED-V Client Installation Wizard Welcome screen, and click Next.
    3. Review the MED-V License Agreement. If you accept the licensing terms, click Next.
    4. Review the Install Destination Folder setting, and click Next.
    5. On the MED-V Settings screen, put checkmarks next to Load MED-V When Windows Starts and Add A MED-V Shortcut To My Desktop. Enter the correct server address and port for your MED-V Server. Accept the default directory to store the MED-V virtual machines. Click Next.
    6. On the Ready To Install The Program screen, select Install. The MED-V Client software will now be installed.
    7. On the MED-V Wizard Completed screen, deselect Launch MED-V Enterprise Desktop Virtualization, and click Finish.

PC3 — Windows XP MED-V Client

The installation process for PC1 will include installing Windows XP SP3 and MED-V Client software. Follow the installation steps listed below.

  1. Install Windows XP SP 3 (32-bit).
  2. Install Microsoft Virtual PC 2007 SP1 and KB 958162 Update.
  3. Install the MED-V Client, and follow the instructions listed under PC2.

The installation steps for the personal computers are now complete. The configuration steps for the Windows personal computers are provided in the upcoming configuration section of this chapter.

Configuration of the MED-V Solution Server Components

After the MED-V solution server and client components have been installed, they need to be configured to work properly with each other. Instructions for configuring the server and client components are provided in the following sections.

ServerA — Image Repository Server

The configuration process for ServerA, the Image Repository Server, includes configuring the Web Server (IIS). The steps for configuring this server are listed below.

  1. Open Windows Server 2008 Server Manager on ServerA.
  2. Select the Web Server (IIS) role on the Server Manager hierarchy.
  3. Select Internet Information Services (IIS) Manager.
  4. In the Internet Information Services (IIS) Manager pane under Connections, select Default Web Site.
  5. Right-click the Default Web Site, and select Add Virtual Directory.
  6. In the Add Virtual Directory screen, enter MEDVImages in the Alias field and C:\MEDV Server Images in the Physical Path field, and click OK. Note that the MEDV Server Images directory was created during the installation of MED-V.
  7. Under Default Web Site, select the MEDVImages folder. In the MEDV Images Home pane, scroll down to the IIS section and select MIME Types → Open Feature from the Actions pane. The following steps will add the MED-V required filename extensions and MIME types:
    1. Select Add from the Actions pane. On the Add MIME Type window, enter .ckm in the File Name Extension field and application/octet-stream in the MIME Type field. Click OK.
    2. Select Add from the Actions pane. On the Add MIME Type window, enter .index in the File Name Extension field and application/octet-stream in the MIME Type field. Click OK.
  8. Under Default Web Site, select the MEDVImages folder. In the MEDV Images Home pane, scroll down to the Other section and select BITS Upload → Open Feature from the Actions pane. Select the check box Allow Clients To Upload Files. Select Apply from the Actions pane.
  9. Under Default Web Site, select the MEDVImages folder. In the Actions pane, select Edit Permissions. On the MED-V Server Images Properties screen, choose the Security tab. Select Edit, add the appropriate groups, and select Allow Read Permissions. In this instance we will use the group Everyone.

ServerB — Database Server

The configuration process for ServerB, the Database Server, was conducted during the time of the installation. Other database settings related to this server are located in the MED-V Server Configuration Manager.

ServerC — MED-V Management Server

The configuration process for ServerC, the MED-V Management Server, includes configuring Client Connections, Image Management, Management Permissions, and Database Settings. The steps for configuring this server are listed below. The MED-V Server Configuration Manager is shown in Figure 16.4.

Figure 16.4 MED-V Server Configuration Manager

  1. Open MED-V Server Configuration Manager from the Start menu on ServerC.
  2. The Connections Tab will be selected by default.
    1. Select the type of connection. MED-V Server provides two types of connections options: unencrypted connections using port 80 and encrypted connections using port 443. In this instance we will use the default setting, Enable Unencrypted Connections (http), Using Port 80.
  3. Select the Images tab.
    1. Enter the VMs Directory location. In this instance we will use the default directory loca-tion, C:\MED-V Server Images\. Earlier we configured the Web Server (IIS) to use the same directory.
    2. Enter the VMs URL In this instance the URL is http://ServerC/medvimages.
  4. Select the Permissions tab.
    1. Add the preferred domain users or groups who will need permissions to manage the MED-V Management Server. If the group Everyone has been added by default, remove it by selecting the group and clicking Remove.
  5. Select the Reports tab.
    1. Select the Enable Reports check box.
    2. Enter the appropriate value in the Database Server Connection String field. In this instance the connection string would be DataSource=ServerB\SQLEXPRESS;Initial Catalog=MEDV;UID=SA;PWD=P@ssword1. A complex password was used to meet the Windows Server password policy requirement.
    3. Click the Create Database button. Click the Test Connection button.
  6. Click the OK button. When prompted to restart the MED-V Management Server, click Yes.

Configuration of the MED-V Solution Client Components

After the MED-V Client components have been installed on personal computers 1, 2, and 3, they will need to be configured properly to work with the MED-V solution. The steps for configuring MED-V Client components are listed below. The MED-V Client Settings screen is shown in Figure 16.5.

PC1 — Windows Vista MED-V Client and Management Console

The process of configuring the Windows Vista MED-V Client and Management Console includes the following steps:

  1. Launch the MED-V Client software.
  2. Right-click the MED-V icon on the system tray and select Settings.
  3. Under Start Options, verify that the Load Med-V After Windows Logon check box and Start Workspace When Med-V Starts check box have been selected.
  4. Under Server Properties, enter the appropriate Server Address and Port data. In this instance, the server would be ServerC. Select Encrypt Connections (HTTPS) if applicable.
  5. Click OK.

Figure 16.5 MED-V Client settings

PC2 — Windows Vista MED-V Client

The steps for configuring the Windows Vista MED-V Client are the same as those performed on PC1. Please refer to the MED-V Client configuration instructions for PC1.

PC3 — Windows XP MED-V Client

The steps for configuring the Windows XP MED-V Client are the same as those performed on PC1. Please refer to the MED-V Client configuration instructions for PC1.


Deploying Microsoft Enterprise Desktop Virtualization
  MED-V deployment planning and requirements
  MED-V: Installing server and client components
  MED-V: Creating and deploying images, workspaces
  MED-V Workspace: Testing, deployment and management

Printed with permission from Wiley Publishing Inc. Copyright 2009. Mastering Microsoft Virtualization by Tim Cerling and Jeffrey Buller. For more information about this title and other similar books, please visit Wiley Publishing Inc.

This was first published in June 2010

Dig deeper on Virtualization Technology and Services

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

MicroscopeUK

SearchCloudProvider

SearchSecurity

SearchStorage

SearchNetworking

SearchCloudComputing

SearchConsumerization

SearchDataManagement

SearchBusinessAnalytics

Close