Test Lab Guide: Virtual Desktop Infrastructure Standard Deployment
Applies To: Windows Server 2012 R2, Windows Server 2012
A Virtual Desktop Infrastructure (VDI) standard deployment enables you to install the appropriate role services on separate computers. Unlike the VDI Quick Start deployment, a standard deployment provides more precise control of virtual desktops and virtual desktop collections by not creating them automatically.
In this guide
This guide contains instructions for setting up a test lab which deploys VDI by using four servers. For detailed information about how the lab is set up, see Test Lab Guide: Base Configuration. The resulting test lab demonstrates how to successfully install and configure a VDI standard deployment.
Important
The following instructions explain how to configure a VDI standard deployment test lab that uses a minimum number of computers. Individual computers are needed to separate the services that are provided on the network and to clearly show the desired functionality. This configuration is neither designed to reflect best practices nor does it reflect a desired or recommended configuration for a production network. The configuration, including IP addresses and all other configuration parameters, is designed only to work on a separate test lab network.
Test lab overview
In this test lab, the VDI standard deployment is deployed with:
One computer running Windows Server 2012 named DC1 that is configured as an intranet domain controller, Domain Name System (DNS) server, Dynamic Host Configuration Protocol (DHCP) server, and an enterprise root certification authority (CA).
One intranet member server running Windows Server 2012 named RDVH1 that is configured as the Remote Desktop Virtualization Host (RD Virtualization Host) server.
One intranet member server running Windows Server 2012 named RDWA1 that is configured as the Remote Desktop Web Access (RD Web Access) server.
One intranet member server running Windows Server 2012 named RDCB1 that is configured as the Remote Desktop Connection Broker (RD Connection Broker) server.
The VDI standard deployment test lab consists of one subnet (10.0.0.0/24) that simulates an intranet named Corpnet.
Computers are connected to each other by using a Hyper-V virtual switch as shown the following figure.
.jpeg)
Hardware and software requirements
The following are required components of the test lab:
You must have a network shared folder that is configured to store user profile disks. All RD Virtualization Host computer accounts must have the ability to read and write to this location.
The product disc or files for Windows Server 2012.
The product disc or files for Windows 8.
A physical computer that meets the minimum hardware requirements for Windows Server 2012.
Note
If you choose the VDI scenario-based installation, a virtual switch named RDS Virtual is automatically created.
Steps for configuring the test lab
There are seven steps to follow when you set up the VDI standard deployment test lab based on the Test Lab Guide: Base Configuration
Step 1: Complete the Base Configuration Test Lab The VDI standard deployment test lab requires the Base Configuration test lab as its starting point.
Step 2: Install and configure RDVH1 RDVH1 is a computer running Windows Server 2012 that is used as the RD Virtualization Host computer.
Step 3: Install and configure RDWA1 RDWA1 is a computer running Windows Server 2012 that is used as the RD Web Access computer.
Step 4: Install and configure RDCB1 RDCB1 is a computer running Windows Server 2012 that is used as the RD Connection Broker computer.
Step 5: Deploy the Virtual Desktop Infrastructure standard deployment The Virtual Desktop Infrastructure standard deployment is deployed by using Server Manager.
Step 6: Test Remote Desktop Services connectivity RDCB1 is used to test that the VDI standard deployment completed successfully.
Step 7: Take a snapshot of the configuration At the completion of the lab, take a snapshot of the configuration so that you can later return to a working VDI standard deployment test lab.
Note
You must be logged on as a member of the Domain Admins group or a member of the Administrators group on each computer to complete the tasks described in this guide. If you cannot complete a task while you are logged on with an account that is a member of the Administrators group, try performing the task while you are logged on with an account that is a member of the Domain Admins group.
Step 1: Complete the base configuration test lab
This test lab guide uses the base configuration test lab as a starting place. Before you proceed with the remainder of the steps in this guide, complete the steps in the Test Lab Guide: Base Configuration. If you have already completed the steps in the Test Lab Guide: Base Configuration and saved a disk image or a virtual machine snapshot of the base configuration, you can restore the base configuration and proceed to the next step.
Step 2: Install and Configure RDVH1
Installing and configuring the server used for the RD Session Host consists of the following procedures:
Install the operating system.
Configure TCP/IP properties.
Join RDVH1 to the CORP domain.
The following sections explain these procedures in detail.
Install the operating system on RDVH1
First, install Windows Server 2012.
To install the operating system on RDVH1
Start the installation of Windows Server 2012.
Follow the instructions to complete the installation, specifying a strong password for the local Administrator account. Log on using the local Administrator account.
Connect RDVH1 to a network that has Internet access and run Windows Update to install the latest updates for Windows Server 2012.
Configure TCP/IP properties
Next, configure TCP/IP.
To configure TCP/IP properties
In Server Manager, click Local Server in the console tree. Click the link next to Wired Ethernet Connection in the Properties tile.
In Network Connections, right-click Wired Ethernet Connection, and then click Properties. Note that the "Wired Ethernet Connection" interface name may be different on your computer.
Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
Select Use the following IP address. In IP address, type 10.0.0.3. In Subnet mask, type 255.255.255.0.
Select Use the following DNS server addresses. In Preferred DNS server, type 10.0.0.1.
Click OK, and then click Close. Close the Network Connections window.
From the Start screen, type command, and then click Command Prompt.
To check name resolution and network communication between RDVH1 and DC1, type ping dc1.corp.contoso.com in the command prompt window and hit ENTER.
Verify that there are four replies from 10.0.0.1.
Close the Command Prompt window.
.jpeg)
Windows PowerShell equivalent commands
The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.. Use the ipconfig /all command to list all the interfaces.
New-NetIPAddress -InterfaceAlias "Wired Ethernet Connection" -IPv4Address 10.0.0.3 -PrefixLength 24
Set-DnsClientServerAddress -InterfaceAlias "Wired Ethernet Connection" -ServerAddresses 10.0.0.1
Join RDVH1 to the CORP domain
To join RDVH1 to the CORP domain
Log on to the computer with the local Administrator user account.
Server Manager will start automatically. If it does not start automatically, click Start, type servermanager.exe, and then click Server Manager.
Click Local Server.
Click the name of the computer next to Computer name, and then click Change.
In the Computer name box, type RDVH1. In the Member of box, click the Domain option, type corp.contoso.com and then click OK.
When you are prompted for a user name and password, provide the CORP\Administrator credentials, and then click OK.
When you see a dialog box welcoming you to the corp.contoso.com domain, click OK.
When you are prompted that you must restart the computer, click OK.
On the System Properties dialog box, click Close, and then click Restart Now.
Windows PowerShell equivalent commands
The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.. Note that you must supply domain credentials after entering the Add-Computer command below.
Rename-Computer -NewName RDVH1
Restart-Computer
Add-Computer -DomainName corp.contoso.com
Restart-Computer
Step 3: Install and Configure RDWA1
Installing and configuring the server used for RD Web Access in the Session Virtualization standard deployment test lab consists of the following procedures:
Install the operating system.
Configure TCP/IP properties.
Join RDWA1 to the CORP domain.
The following sections explain these procedures in detail.
Install the operating system on RDWA1
First, install Windows Server 2012.
To install the operating system on RDWA1
Start the installation of Windows Server 2012.
Follow the instructions to complete the installation, specifying a strong password for the local Administrator account. Log on using the local Administrator account.
Connect RDWA1 to a network that has Internet access and run Windows Update to install the latest updates for Windows Server 2012.
Configure TCP/IP properties
Next, configure TCP/IP.
To configure TCP/IP properties
In Server Manager, click Local Server in the console tree. Click the link next to Wired Ethernet Connection in the Properties tile.
In Network Connections, right-click Wired Ethernet Connection, and then click Properties. Note that the "Wired Ethernet Connection" interface name may be different on your computer.
Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
Select Use the following IP address. In IP address, type 10.0.0.4. In Subnet mask, type 255.255.255.0.
Select Use the following DNS server addresses. In Preferred DNS server, type 10.0.0.1.
Click OK, and then click Close. Close the Network Connections window.
From the Start screen, type command, and then click Command Prompt.
To check name resolution and network communication between RDWA1 and DC1, type ping dc1.corp.contoso.com in the command prompt window and hit ENTER.
Verify that there are four replies from 10.0.0.1.
Close the Command Prompt window.
Windows PowerShell equivalent commands
The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.. Use the ipconfig /all command to list all the interfaces.
New-NetIPAddress -InterfaceAlias "Wired Ethernet Connection" -IPv4Address 10.0.0.4 -PrefixLength 24
Set-DnsClientServerAddress -InterfaceAlias "Wired Ethernet Connection" -ServerAddresses 10.0.0.1
Join RDWA1 to the CORP domain
To join RDWA1 to the CORP domain
Log on to the computer with the local Administrator user account.
Server Manager will start automatically. If it does not start automatically, click Start, type servermanager.exe, and then click Server Manager.
Click Local Server.
Click the name of the computer next to Computer name, and then click Change.
In the Computer name box, type RDWA1. In the Member of box, click the Domain option, type corp.contoso.com and then click OK.
When you are prompted for a user name and password, provide the CORP\Administrator credentials, and then click OK.
When you see a dialog box welcoming you to the corp.contoso.com domain, click OK.
When you are prompted that you must restart the computer, click OK.
On the System Properties dialog box, click Close, and then click Restart Now.
Windows PowerShell equivalent commands
The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.. Note that you must supply domain credentials after entering the Add-Computer command below.
Rename-Computer -NewName RDWA1
Restart-Computer
Add-Computer -DomainName corp.contoso.com
Restart-Computer
Step 4: Install and Configure RDCB1
Installing and configuring the server used for the RD Connection Broker consists of the following procedures:
Install the operating system.
Configure TCP/IP properties.
Join RDCB1 to the CORP domain.
The following sections explain these procedures in detail.
Install the operating system on RDCB1
First, install Windows Server 2012.
To install the operating system on RDCB1
Start the installation of Windows Server 2012.
Follow the instructions to complete the installation, specifying a strong password for the local Administrator account. Log on using the local Administrator account.
Connect RDCB1 to a network that has Internet access and run Windows Update to install the latest updates for Windows Server 2012.
Configure TCP/IP properties
Next, configure TCP/IP.
To configure TCP/IP properties
In Server Manager, click Local Server in the console tree. Click the link next to Wired Ethernet Connection in the Properties tile.
In Network Connections, right-click Wired Ethernet Connection, and then click Properties. Note that the "Wired Ethernet Connection" interface name may be different on your computer.
Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
Select Use the following IP address. In IP address, type 10.0.0.5. In Subnet mask, type 255.255.255.0.
Select Use the following DNS server addresses. In Preferred DNS server, type 10.0.0.1.
Click OK, and then click Close. Close the Network Connections window.
From the Start screen, type command, and then click Command Prompt.
To check name resolution and network communication between RDCB1 and DC1, type ping dc1.corp.contoso.com in the command prompt window and hit ENTER.
Verify that there are four replies from 10.0.0.1.
Close the Command Prompt window.
Windows PowerShell equivalent commands
The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.. Use the ipconfig /all command to list all the interfaces.
New-NetIPAddress -InterfaceAlias "Wired Ethernet Connection" -IPv4Address 10.0.0.5 -PrefixLength 24
Set-DnsClientServerAddress -InterfaceAlias "Wired Ethernet Connection" -ServerAddresses 10.0.0.1
Join RDCB1 to the CORP domain
To join RDCB1 to the CORP domain
Log on to the computer with the local Administrator user account.
Server Manager will start automatically. If it does not start automatically, click Start, type servermanager.exe, and then click Server Manager.
Click Local Server.
Click the name of the computer next to Computer name, and then click Change.
In the Computer name box, type RDCB1. In the Member of box, click the Domain option, type corp.contoso.com and then click OK.
When you are prompted for a user name and password, provide the CORP\Administrator credentials, and then click OK.
When you see a dialog box welcoming you to the corp.contoso.com domain, click OK.
When you are prompted that you must restart the computer, click OK.
On the System Properties dialog box, click Close, and then click Restart Now.
Windows PowerShell equivalent commands
The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.. Note that you must supply domain credentials after entering the Add-Computer command below.
Rename-Computer -NewName RDCB1
Restart-Computer
Add-Computer -DomainName corp.contoso.com
Restart-Computer
Step 5: Deploy the Virtual Desktop Infrastructure standard deployment
Deploying the required role services for the VDI standard deployment consists of the following procedures:
Add RDVH1, RDWA1, and RDCB1 to the server pool
Deploy the VDI standard deployment
To add RDVH1, RDWA1, and RDCB1 to the server pool
Log on to the RDCB1 server by using the CORP\User1 user account.
Server Manager will start automatically. If it does not automatically start, click Start, type servermanager.exe, and then click Server Manager.
In the QUICK START section, click Add other servers to manage.
In the Name (CN): box, type RDWA1, and then click Find Now.
Click RDWA1, and then click the right arrow.
Repeat steps 4- 5 for the RDVH1 server.
Click OK.
To deploy the VDI standard deployment
Log on to the RDCB1 server by using the CORP\User1 user account.
Server Manager will start automatically. If it does not automatically start, click Start, type servermanager.exe, and then click Server Manager.
In the QUICK START section, click Add roles and features.
On the Before You Begin page of the Add Roles and Features Wizard, click Next.
On the Select Installation Type page, click Remote Desktop Services installation, and then click Next.
On the Select deployment type page, click Standard deployment, and then click Next.
On the Select deployment scenario page, click Virtual machine-based desktop deployment, and then click Next.
On the Review role services page, click Next.
On the Specify RD Connection Broker server page, click RDCB1.corp.contoso.com, click the right arrow, and then click Next.
On the Specify RD Web Access server page, click RDWA1.corp.contoso.com, click the right arrow, and then click Next.
On the Specify RD Virtualization Host server page, click RDVH1.corp.contoso.com, click the right arrow, and then click Next.
On the Confirm selections page, select the Restart the destination server automatically if required check box, and then click Deploy.
After the installation is complete, click Close.
Step 6: Test the VDI standard deployment connectivity
You can ensure that VDI standard deployment deployed successfully by using Server Manager to check the Remote Desktop Services deployment overview.
Use the following procedure to connect to the VDI standard deployment.
To check the deployment overview
Log on to the RDCB1 server by using the CORP\User1 user account.
Server Manager will start automatically. If it does not automatically start, click Start, type servermanager.exe, and then click Server Manager.
Click Remote Desktop Services, and then click Overview.
In the DEPLOYMENT OVERVIEW section, ensure that the RD Web Access, RD Connection Broker, and RD Virtualization Host role services are installed. If there is an icon and not a green plus sign (+) next to the role service name, the role service is installed and part of the deployment.
Step 7: Take a snapshot of the configuration
This completes the VDI standard deployment. To save this configuration so that you can quickly return to a working VDI standard deployment configuration from which you can test other Remote Desktop Services modular test lab guides (TLGs), TLG extensions, or for your own experimentation and learning, do the following:
On all physical computers or virtual machines in the test lab, close all windows and then turn them off.
If your lab is based on virtual machines, save a snapshot of each virtual machine and name the snapshots. If your lab uses physical computers, create disk images to save the VDI standard deployment test lab configuration.
Additional Resources
What's New in Remote Desktop Services in Windows Server 2012 [redirected]
You Are Here -> Test Lab Guide: Virtual Desktop Infrastructure Standard Deployment
Test Lab Guide: Unmanaged Pooled Virtual Desktop Collections
Test Lab Guide: Remote Desktop Services Session Virtualization Quick Start
Test Lab Guide: Remote Desktop Services Session Virtualization Standard Deployment