The Contoso branch office test lab consists of six computers on three separate subnets:

• The Corpnet subnet contains the DC1, APP1, and RTR1 computers
• The Wannet subnet contains the RTR1 and RTR2 computers
• The Branchnet subnet contains the RTR2 and BOAPP1 computers

The CLIENT1 computer can connect to the Corpnet or Branchnet subnets.

This figure shows the computers and their connections to the subnets using a hub or switch. You can implement this configuration using physical computers and switches, virtual computers and switches, or a combination of physical and virtual components.

If you are using Windows Server 2012 and the Hyper-V server role for your virtualization solution, you can configure the Contoso branch office in Hyper-V on a single server as shown in the following figure (click on it for a larger version):

The key elements of this configuration are the following:

• All six computers (DC1, APP1, CLIENT1, RTR1, RTR2, and BOAPP1) are virtual machines running on the Hyper-V server.
• The Corpnet subnet is implemented as the Corpnet virtual switch.
  • DC1, APP1, and RTR1 are connected to the Corpnet virtual switch.
• The Wannet subnet is implemented as the Wannet virtual switch.
  • RTR1 and RTR2 are connected to the Wannet virtual switch.
• The Branchnet subnet is implemented as the Branchnet virtual switch.
  • RTR2 and BOAPP1 are connected to the Branchnet virtual switch.
• CLIENT1 can be connected to either the Corpnet or Branchnet virtual switches.
• The Hyper-V server has at least one physical network adapter that connects to your organization intranet and the Internet. You can use this connection to connect a branch office test lab computer to the real Internet, for example to install software or updates. For more information, see How do I get my base configuration computers on the Internet?

If you have not already done so, build out the Corpnet subnet in Windows Server 2012 Hyper-V with the following:

1. Create a private virtual switch named Corpnet. For the steps to do this, see Creating a new virtual switch.
2. Create a new virtual machine named DC1 with a single network adapter that is connected to the Corpnet virtual switch. For the steps to do this, see Creating a new virtual machine.
3. Create a new virtual machine named APP1 with a single network adapter that is connected to the Corpnet virtual switch.
4. Create a new virtual machine named CLIENT1 with a single network adapter that is connected to the Corpnet virtual switch.
5. Follow the instructions in the “Steps for Configuring the Corpnet Subnet” section of the Test Lab Guide: Windows Server 2012 Base Configuration. To install Windows Server 2012, Windows Server 2008 R2, Windows 8, or Windows 7 on a virtual machine, see Installing an operating system on a new virtual machine.

To build out the Wannet and Branchnet subnets in Windows Server 2012 Hyper-V, do the following:

1. Create a private virtual switch named Wannet.
2. Create a private virtual switch named Branchnet.
3. Create a new virtual machine named RTR1 that is connected to the Corpnet virtual switch.
4. Add a network adapter to RTR1 that is connected to the Wannet virtual switch. For the steps to do this, see Adding a network adapter to a new virtual machine.
5. Create a new virtual machine named RTR2 that is connected to the Wannet virtual switch.
6. Add a network adapter to RTR2 that is connected to the Branchnet virtual switch.
7. Create a new virtual machine named BOAPP1 that is connected to the Branchnet virtual switch.
8. Follow the instructions in the Test Lab Guide: Configure the Contoso Branch Office, starting with step 2.

• Step 2 installs and configures RTR1.
• Step 3 installs and configures RTR2.
• Step 4 installs and configures BOAPP1.
• Step 5 demonstrates connectivity from the branch office.

For additional information about configuring test labs with Windows Server 2012 Hyper-V, see Hosting Test Lab Guide environments in Windows Server 2012 Hyper-V.

For more information, see Test Lab Guides.

For the latest developments in the Test Lab Guides initiative, see the Microsoft Test Lab Guides blog.