Some people find templates helpful when creating Wiki articles. This one is intended to help those writing troubleshooting test lab guides (TLGs), which step readers through troubleshooting tools and some common troubleshooting scenarios in test lab based on a modular TLG. A modular TLG describes how to set up and demonstrate a technology, product, or multi-product or technology solution. For an example of a troubleshooting TLG, see Test Lab Guide: Troubleshoot DirectAccess.

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

Troubleshooting Test Lab Guide Template

<a brief overview (1-2 paragraphs) of the technology or product>

In this guide

The <technology/product> test lab, as described in the <link to modular test lab guide on which this troubleshooting test lab guide is based>, contains <number> server computers running Windows Server 2008 R2 Enterprise Edition and <number> client computers running Windows 7 Enterprise or Ultimate Edition. The lab simulates an <environment and technology/product functionality>.

The <technology/product> test lab consists of:

• 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 <technology/product> 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, switch, or virtual switch. See the following figure.

<insert figure of technology/product test lab>

<summary of the technology/product test lab configuration and demonstration of functionality>

This guide uses the working <technology/product> test lab as a basis for describing <technology/product> troubleshooting tools and their results when <situation/configuration to demonstrate troubleshooting tools>. This guide then takes you through various troubleshooting scenarios using topics in the <link to technology/product Troubleshooting Guide> and the troubleshooting tools to discover the root cause of the problem.

Important  This topic does not describe how to troubleshoot a non-functioning <technology/product> test lab. For general troubleshooting information, see the <link to technology/product Troubleshooting Guide>.

<technology/product> Troubleshooting Tools

<product/OS> provides many tools for gathering information for <technology/product>problem determination and resolution. The following table lists the tools and describes their use and purpose for <technology/product>. For additional information, see <link to TechNet topic that describes the tools in detail>.

<technology/product> Troubleshooting Tools in the Test Lab

This section describes the display of key troubleshooting tools when <situation/configuration to demonstrate troubleshooting tools>.

<tool>

The following is the display of the <tool> on <computer> when it is <situation/configuration>:

<command line output or screen shot>

Notice the <information relevant for technology/product troubleshooting>.

Troubleshooting <technology/product or problem domain> Problems

The following sections contain troubleshooting scenarios in which you deliberately configure the <technology/product> test lab to impair <technology/product functionality>. You will then use the troubleshooting techniques described in the <link to technology/product Troubleshooting Guide> and the troubleshooting tools described in this topic to determine the root cause of the problem and correct it.

<troubleshooting problem x>

<discussion of technology/product requirement or process that provides context for the troubleshooting scenario and the following subsections>

In this troubleshooting scenario, you will configure <root cause that breaks the test lab> and then troubleshoot the results.

Break the configuration procedure

Follow these steps to configure the <technology/product> test lab for this troubleshooting scenario.

To <break procedure title>

1.  <steps to break the test lab and demonstrate its broken state>

Step-by-step troubleshooting
From the previous procedure, it appears that <problem statement>. The following procedure uses the appropriate steps in <links to appropriate topics in technology/product Troubleshooting Guide> to determine the root cause of the problem.

To troubleshoot this scenario

1. <steps to perform root cause troubleshooting of the problem, the last step clearly demonstrates or determines the root cause>

 This is the root cause of the problem. <discussion of why the root cause impairs the demonstrated functionality>

Correct the configuration procedure

Follow these steps to correct the configuration of the <product/technology> test lab for this troubleshooting scenario.

To configure <correction procedure title>