Deploying Remote Desktop IP Virtualization Step-by-Step Guide

Applies To: Windows 7, Windows Server 2008 R2

About this guide

This step-by-step guide walks you through the process of setting up a working Remote Desktop IP Virtualization infrastructure in a test environment. During this process, you will create a test deployment that includes the following components:

  • A Remote Desktop Connection Broker (RD Connection Broker) server

  • A Remote Desktop Web Access (RD Web Access) server

  • A DHCP server

This guide assumes that you previously completed the Installing Remote Desktop Session Host Step-by-Step Guide (, and that you have already deployed the following components (if you have previously configured the computers in the Installing Remote Desktop Session Host Step-by-Step Guide, you should repeat the steps in that guide with new installations):

  • A Remote Desktop Session Host (RD Session Host) server

  • A Remote Desktop Connection client computer

  • An Active Directory domain controller

This guide includes the following topics:

In Windows Server® 2008 R2, RD Session Host supports per program and per session Remote Desktop IP Virtualization for Winsock applications. When using per program Remote Desktop IP Virtualization, you choose which programs to use with Remote Desktop IP Virtualization. When using per session Remote Desktop IP Virtualization, all Winsock applications are virtualized with Remote Desktop IP Virtualization. Remote Desktop IP Virtualization allows you to assign a unique IP address to a user session, which helps to avoid application compatibility issues by simulating a local desktop.

What this guide does not provide

This guide does not provide the following:

  • An overview of Remote Desktop Services.

  • Guidance for setting up and configuring a Remote Desktop IP Virtualization server in a production environment.

  • Scalability or performance information concerning RD Session Host in a production environment.

  • Complete technical reference for Remote Desktop Services.

Scenario: Deploying Remote Desktop IP Virtualization in a test environment

We recommend that you first use the steps provided in this guide in a test lab environment. Step-by-step guides are not necessarily meant to be used to deploy Windows Server features without additional deployment documentation and should be used with discretion as a stand-alone document.

Upon completion of this step-by-step guide, you will have a working Remote Desktop Services infrastructure by using Remote Desktop IP Virtualization. You can then test and verify Remote Desktop Services functionality as follows:

  • Have a user connect to an RD Session Host server by using Remote Desktop Connection and verify that the session is assigned a unique IP address.

The test environment described in this guide includes six computers connected to a private network using the following operating systems, applications, and services.

Computer name Operating system Applications and services


Windows Server 2008 R2

Active Directory Domain Services, Domain Name System (DNS)


Windows Server 2008 R2

RD Session Host


Windows® 7

Remote Desktop Connection


Windows Server 2008 R2

RD Connection Broker


Windows Server 2008 R2

RD Web Access


Windows Server 2008 R2

Dynamic Host Configuration Protocol (DHCP)

The computers form a private network and are connected through a common hub or Layer 2 switch. This configuration can be emulated in a virtual server environment if desired. This step-by-step exercise uses private addresses throughout the test lab configuration. The private network ID is used for the network. The domain controller is named CONTOSO-DC for the domain named The following figure shows the configuration of the test environment.