Table of Contents Test lab overviewHardware and software requirementsSteps for Configuring the Branch Office Test LabStep 1: Set up the Base Configuration test labStep 2: Set up RTR1 and the Wannet subnet Install the operating systemConfigure Network Connections propertiesConfigure IPv4 routing Step 3: Set up RTR2 and the Branchnet subnet Install the operating systemConfigure Network Connections propertiesConfigure IPv4 routing Step 4: Install and configure BOAPP1 Install the operating systemConfigure TCP/IP propertiesJoin BOAPP1 to the CORP domainInstall the Web Server (IIS) roleConfigure the HTTPS security bindingCreate a shared folderInstall and configure the DHCP Server service Step 5: Demonstrate connectivity from the branch officeStep 6: Install and configure WAN link emulation (optional)Snapshot the ConfigurationAdditional Resources
This Test Lab Guide (TLG) contains instructions for setting up a branch office test lab using three server computers, two computers acting as IPv4 routers, and one client computer. The resulting branch office test lab provides an environment for configuring
and testing branch office deployment scenarios.
Important The following instructions are for configuring a branch office 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.
Attempting to adapt this test lab configuration to a pilot or production deployment can result in configuration or functionality issues.
In this test lab, the Contoso branch office is deployed with:
This TLG only requires the Corpnet subnet from the Base Configuration test lab as its starting point. See the following figure for the branch office test lab configuration (click on it for a larger
Note that this branch office test lab configuration is emulating a private WAN link (the Wannet subnet) between a main office (the Corpnet subnet) and a branch office (the Branchnet subnet). This
branch office test lab configuration does not create a site-to-site VPN connection between computers over the Internet subnet.
In this Test Lab Guide, you install a set of router computers to forward traffic between the Corpnet and Branchnet subnets via the Wannet subnet and then add an application server to the Branchnet
For a short overview of how to build out the Contoso branch office test lab, see the following:
Note For a variation on this branch office configuration that replaces RTR1, RTR2, and the Wannet subnet with an Apposite Technologies Linktropy WAN emulator, see
Test Lab Guide: Configure
the Contoso Branch Office using an Apposite Technologies WAN Emulator.
For instructions on configuring this lab using Hyper-V in Windows Server 2012, see
Hosting the Contoso branch office test lab with Windows Server 2012 Hyper-V.
The following are required components of this test lab:
There are six major steps to follow when setting up a branch office test lab.
The following sections provide the details about how to perform these steps.
The branch office test lab requires the Corpnet subnet of the Base Configuration test lab. If needed, create the Corpnet subnet of the base configuration test lab as described in the
Test Lab Guide: Base Configuration.
RTR1 acts as an IPv4 router between the Corpnet and Wannet subnets. RTR1 configuration consists of the following:
You will need an additional switch, either physical or virtual, for the Wannet subnet.
Note RTR1 must have two network adapters installed.
First, install Windows 7 on RTR1.
To install Windows 7 on RTR1
Next, configure the names of the adapters in the Network Connections folder for the subnets to which they are connected and their IPv4 addresses.
To configure Network Connections properties
Next, configure RTR1 to perform IPv4 forwarding and for the set of routes for all three subnets and the Corpnet subnet computers to use RTR1 as its default gateway.
To configure IPv4 routing
netsh interface ipv4 set interface Corpnet forwarding=enabled
netsh interface ipv4 set interface Wannet forwarding=enabled
netsh interface ipv4 add route 10.2.0.0/24 interface=Wannet nexthop=192.168.1.2
netsh advfirewall firewall set rule "File and Printer Sharing (Echo Request - ICMPv4-In)" new enable=yes
If you have additional computers on the Corpnet subnet, perform the following steps on each of them to ensure that they will be able to send traffic to the branch office subnet:
RTR2 acts as an IPv4 router between the Wannet and Branchnet subnets. RTR2 configuration consists of the following:
You will need an additional switch, either physical or virtual, for the Branchnet subnet.
Note RTR2 must have two network adapters installed.
First, install Windows 7 on RTR2.
To install Windows 7 on RTR2
Note that the Branchnet subnet is using the IPv4 addressing guidelines described in
to the Demonstrate IPv6 TLG and addressing guidelines for the Contoso Corporation.
Next, configure RTR2 to perform IPv4 forwarding and for the set of routes for all three subnets.
To configure RTR2 for IPv4 routing
netsh interface ipv4 set interface Branchnet forwarding=enabled
netsh interface ipv4 add route 10.0.0.0/24 interface=Wannet nexthop=192.168.1.1
BOAPP1 provides DHCP, web, and file sharing services in the branch office. BOAPP1 configuration consists of the following:
First, install Windows Server 2008 R2 Enterprise Edition on BOAPP1.
To install the operating system
Next, configure TCP/IP.
To configure TCP/IP properties
Next, join BOAPP1 to the corp.contoso.com domain.
To join BOAPP1 to the CORP domain
Next, install the Web Server (IIS) role to make BOAPP1 a web server.
To install the Web Server (IIS) role
Next, configure the HTTPS security binding so that BOAPP1 can host HTTPS-based URLs.
To configure the HTTPS security binding
Next, create a shared folder and a text file within the folder on BOAPP1.
To create a shared folder
Next, install the DHCP Server service on BOAPP1 and configure it for the Branchnet subnet.
To install and configure the DHCP server role
Verify that intranet web and file share resources on BOAPP1 can be accessed by CLIENT1.
To test access to intranet resources
For scenarios that rely on reduced bandwidth across a WAN link, you can install and configure WAN link emulation on RTR1 and RTR2 to simulate a low bandwidth connection between the Corpnet and
Windows Server 2008 R2 and Windows 7 does not include WAN simulation capabilities for Ethernet network adapters. You can use the Network Emulation in Visual Studio 2010 (see
Introducing True Network Emulation in Visual
Studio 2010 and How to: Configure Network Emulation
Using Test Settings in Visual Studio). Alternately, you can use a third-party network emulation or LAN simulation product.
This completes the branch office test lab. The result is a test lab environment that contains two subnets of the Contoso intranet separated by a simulated WAN link. You can now begin building
out and experimenting with branch office scenarios and solutions.
To save this configuration so that you can quickly return to a working branch office configuration, do the following:
For additional test lab guide resources, see
Test Lab Guides.