Some people find templates helpful when creating Wiki articles. This one is intended to help those writing modular test lab guides (TLGs), based on either the Base Configuration test lab or a test lab based on another modular TLG.

A modular TLG describes how to set up and demonstrate a technology, product, or multi-product or technology solution. For more information, see Test Lab Guides.

This template is a work in progress, please add to it.

Feel free to copy/paste the template below into your modular TLG Wiki article to help get you started. It is a best practice to leave an area that you cannot currently fill in blank. This way others can fill it in if they have the information. This is called "stubbing" on the wiki.

Modular Test Lab Guide Template

This topic contains instructions for setting up a test lab based on the <Base Configuration or other modular test lab guide> and deploying <product/technology> using <number> server computers and <number> client computers. The resulting <product/technology> test lab demonstrates <functionality>.

Important  The following instructions are for configuring a <product/technology> 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 <product/technology> test lab configuration to a pilot or production deployment can result in configuration or functionality issues. To ensure proper configuration and operation for your pilot or production <product/technology> deployment, use the information in the <link to product/technology Design Guide> for planning and design decisions and the <link to product/technology Deployment Guide> for the steps to properly configure the <product/technology> and supporting infrastructure servers.

Test lab overview

In this test lab, <product/technology> is deployed with:

  • One computer running Windows Server 2008 R2 Enterprise Edition 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 2008 R2 Enterprise Edition named EDGE1 that is configured as <additional functionality as needed>.
  • One intranet member server running Windows Server 2008 R2 Enterprise Edition named APP1 that is configured as a general application server and <additional functionality as needed>.
  • One standalone server running Windows Server 2008 R2 Enterprise Edition named INET1 that is configured as an Internet DHCP server, DNS server, Web server, and <additional functionality as needed>.
  • One roaming member client computer running Windows 7 Enterprise or Ultimate Edition named CLIENT1 that is configured as a <additional functionality as needed>.
  • <additional computers as needed>

The <product/technology> test lab consists of <number> subnets that simulate the following:

  • The Internet (131.107.0.0/24).
  • An intranet named Corpnet (10.0.0.0/24) separated from the Internet by EDGE1.
  • <additional subnets as needed>

Computers on each subnet connect using a hub or switch. See the following figure.

< figure of resulting test lab>

<summary of the functionality that the test lab instructions demonstrate>

Hardware and software requirements

The following are required components of the test lab:

  • The product disc or files for Windows Server 2008 R2 Enterprise.
  • The product disc or files for Windows 7 Enterprise or Ultimate.
  • <number> computers that meet the minimum hardware requirements for Windows Server 2008 R2 Enterprise Edition. One of these computers has two network adapters installed.
  • <number> computers that meet the minimum hardware requirements for Windows 7 Enterprise or Ultimate Edition.

Steps for Configuring the <product/technology> Test Lab

There are <number> steps to follow when setting up a <product/technology> test lab based on the <link to test lab guide on which this test lab operates>.

  1. Set up the <Base Configuration or other modular TLG> test lab. The <product/technology> test lab requires the <Base Configuration or other required> test lab as its starting point.
  2. Configure <existing computer>. <existing computer> is already configured as <roles>. For the <product/technology> test lab, <existing computer> must be configured with <additional functionality>.
  3. Configure <new computer>. <new computer> must be configured as <roles>.
  4. Configure <product/technology>.
  5. Demonstrate/verify <product/technology functionality>.

This topic provides steps for configuring the computers of the <product/technology> test lab, configuring <product/technology>, and demonstrating <functionality>. The following sections provide details about how to perform these tasks.

Step 1: Set up the <Base Configuration or other> Test Lab

<Set up the Base Configuration test lab for both the Corpnet and Internet subnets using the procedures in the “Steps for Configuring the Corpnet Subnet” and “Steps for Configuring the Internet Subnet” sections of the Test Lab Guide: Base Configuration.>

<Set up the <other> test lab using the procedures in the <link to test lab guide on which this test lab operates>.>

Step 2: Configure <existing computer>

Additional <existing computer> configuration for the <product/technology> test lab consists of the following procedures:

  • <procedure section title>

The following sections explain these procedures in detail.

<procedure section title>

<summary of procedure>

To <procedure>

  1.   
  2.  
  3.  
  4.  
  5.   

Step x: Add and configure <computer name>

<computer name> configuration for the <product/technology> test lab consists of the following procedures:

  • <procedure section title>

The following sections explain these procedures in detail.

<procedure section title>

<summary of procedure>

To <procedure>

  1.   
  2.  
  3.  
  4.  
  5.   

Step y: Configure <technology/product>

Use the following procedures to configure < technology/product>:

  • <procedure section title>

The following sections explain these procedures in detail.

<procedure section title>

<summary of procedure>

To <procedure>

  1.   
  2.  
  3.  
  4.  
  5.   

Step z: Test/verify <technology/product functionality>

Use the following procedures to show <functionality>:

  • <procedure section title>

The following sections explain these procedures in detail.

<procedure section title>

<summary of procedure>

To <procedure>

  1.   
  2.  
  3.  
  4.  
  5.   

Snapshot the Configuration

This completes the <technology/product> test lab. To save this configuration so that you can quickly return to a working <technology/product> configuration from which you can test other <technology/product> modular TLGs, TLG extensions, or for your own experimentation and learning, do the following:

  1. On all physical computers or virtual machines in the test lab, close all windows and then perform a graceful shutdown.
  2. If your lab is based on virtual machines, save a snapshot of each virtual machine and name the snapshots <technology/product>. If your lab uses physical computers, create disk images to save the <technology/product> test lab configuration.

 Additional Resources

For additional information about <technology/product> see <link to resources>.

For additional test lab guide resources, see
Test Lab Guides.