Publishes a session-based desktop for each RD Session Host server in the collection.

Publishes applications as RemoteApp programs.

A Remote Desktop Services Session Virtualization standard deployment allows you to install the appropriate role services on separate computers. Unlike the Session Virtualization Quick Start deployment, a standard deployment provides more precise control of session-based desktops and session virtualization collections by not creating them automatically.

This topic contains instructions for setting up a test lab based on the Test Lab Guide: Base Configuration and deploying Session Virtualization using three server computers and one client computer. The resulting Session Virtualization standard deployment test lab demonstrates how to successfully install and configure a Session Virtualization standard deployment.

Important

The following instructions describe how to configure a Session Virtualization standard deployment test lab using the minimum number of computers. Individual computers are needed to separate the services 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.

Step 6: Create Session Collection – A Session Collection is created by using Server Manager.

Step 7: Test Remote Desktop Services Connectivity -- CLIENT1 is a Windows 8 computer that is used to test that you can successfully connect to the Session Virtualization standard deployment.

Step 8: Snapshot the configuration -- At the completion of the lab, snapshot the configuration so that you can later return to a working Session Virtualization 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.

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.

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.6. 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 RDSH1 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.

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 RDSH1. 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.

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.

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.

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.

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.

To test that the Session Virtualization standard deployment deployed and the session collection was created successfully, you log on to the RD Web Access server on the RDWA1 computer and connect to a session in the SessionCollection session collection.

This completes the Session Virtualization standard deployment test lab. To save this configuration so that you can quickly return to a working VDI Quick Start 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 perform a graceful shutdown.

If your lab is based on virtual machines, save a snapshot of each virtual machine and name the snapshots Session Virtualization standard deployment. If your lab uses physical computers, create disk images to save the Session Virtualization standard deployment test lab configuration.