A third way that you can contribute to Microsoft Test Lab Guides (TLGs) is to publish a troubleshooting TLG in the TechNet Wiki. A troubleshooting TLG contains the following sections:
This sets the stage for using these tools later in the TLG and for identifying deltas between the display of these tools when everything works and when it doesn't.
These troubleshooting scenarios are a lot of fun because you can create a common issue and guide the reader through its resolution, in essence training them for the real thing in the wild. You can also get creative and break the functionality in ways that produce misleading error messages or conditions. Then take the reader through the troubleshooting methodology to expose the hidden culprit, giving them additional practice with the tools and troubleshooting methodology.
For example, the Test Lab Guide: Troubleshoot DirectAccess contains the following sections:
A quick listing of the UI and command line tools that are the most helpful in gathering information about DirectAccess configuration and behavior.
The results of the DirectAccess troubleshooting tools on the Corpnet, Internet, and Homenet subnets.
A set of five troubleshooting scenarios for common problems with DirectAccess functionality, including the following:
The process for publishing your own troubleshooting TLG is the following:
This should be the Base Configuration test lab or the test lab based on another modular TLG.
Use the Wiki: Troubleshooting Test Lab Guide Template in the TechNet Wiki as a starting point. If you use this template, your troubleshooting TLG will have the same structure and boilerplate text as other published troubleshooting TLGs, allowing readers to more easily learn the troubleshooting tools and techniques based on your instructions.
After documenting the tools and the troubleshooting scenarios (the steps and verifying that they work), publish the troubleshooting TLG as a single topic in the TechNet Wiki.
To make sure that others in the community know about your troubleshooting TLG, do the following:
Joe DaviesPrincipal WriterWindows Server Information Experience