Sample Planning Worksheets

Building a Windows 2000 Test Lab

The chapter "Building a Windows 2000 Test Lab" in this book stresses the importance of thorough Windows 2000 testing based on realistic scenarios. It also provides many guidelines that you can use to set up your organization's lab and to run a thorough test program.

To start, you need to:

Create a test plan that describes your scope, objectives, and methodology.
Design test cases that describe the test scenarios and issues that you need to address.
Conduct tests and evaluate results.
Document test results.
Escalate problems to the proper people for resolution.

To the extent possible, your lab needs to simulate your actual working environment. The following are essential components that should be documented in your test plan:

The current network design (logical and physical).
The proposed Windows 2000 design.
A list of features to evaluate and explore.
An inventory of existing hardware (servers, client computers, and portable computers).
A list of hardware proposed for Windows 2000.
This list might evolve during testing, but you need an initial list to equip the lab.
A list of administrative tools (Windows 2000, third party, and custom built).
A list of the upgrades, such as service packs, drivers, and basic input/output system (BIOS), that you need to install to be ready for Windows 2000.

Also include the following types of information in your lab description:

Domain structure, including:
- Forest and tree hierarchy.
- Group Policy objects (settings and where they apply).
- Purpose for each domain.
- Method for populating user account data.
- Trust relationships (transitive and explicit).
Domain controllers, including:
- Primary Domain Controllers (PDCs) and Backup Domain Controllers (BDCs), if migrating from Microsoft® Windows NT® version 4.0.
- Servers you will promote to domain controllers, if migrating from any other operating system.
Member servers, including the services that will run on them.
Client computers, including:
- Computer make and model.
- Amount of memory.
- Processor type and speed.
- Hard disk capacity.
- Graphics cards (type, resolution, and color depth).
Use of lab design for specific tests, including:
- Mixed-mode and native-mode testing.
- Dial-up and other remote testing.
- Interoperability testing (UNIX, mainframes, and other systems).
- Replication and Active Directory site testing.
- WAN link testing.

Use Table A.10 to document the scope and objectives of each test. Complete a new sheet for each test.

Table A.10 Document the Scope and Objectives of Each Test

Test Identifier:	Test Date:
	Test Scope and Objectives:
Purpose of the test
Special hardware requirements
Special software requirements
Special configuration requirements
Test procedure to be used
Expected results or success criteria

Table A.11 illustrates the type of tracking sheet you might use to monitor the progress of your tests and to ensure that all follow-up issues are resolved.

Table A.11 Track Your Test Results

Test Identifier	Date of Test	Results	Action Items