Export (0) Print
Expand All

Building a Lab Environment

Published: October 22, 2009

Updated: October 22, 2009

Applies To: Windows 7, Windows Server 2008 R2

noteNote
This content applies to Windows 7. For Windows 8 content, see Windows Deployment with the Windows ADK.

If you do not already have a lab, we recommend that you create a lab environment dedicated to developing and testing Windows® deployment.

The lab must mirror the production environment as closely as possible to ensure that all aspects of this environment can be accounted for in the development process. The following are two example deployment environments: a simple network and a server-based network.

Simple Network Environment

Diagram of a simple network environment

A simple network is ideal for low-volume deployments. The lab must include:

  • A technician computer to host the Windows OPK tools or Windows AIK tools. It can be a workstation, server, or even a laptop, and can be used as a network share. It can run Windows Vista®, Windows® 7, Windows Server® 2003 or Windows Server® 2008 R2.

  • Client workstations. Any unique type of workstation configuration found in production must be duplicated in the lab. This enables you to test each hardware configuration.

  • Network hubs and cabling. A router with Dynamic Host Configuration Protocol (DHCP) support is recommended. DHCP services provide IP addresses to client computers.

  • Internet access. The lab (or a portion of the lab) must have access to the Internet for downloading software updates.

  • CD or DVD burner. A computer must be available in the lab for creating CD-ROMs or DVD-ROMs.

For more information on deploying an image from a network, see Walkthrough: Deploy an Image from a Network Share.

Server-Based Network Environment

Diagram of example server-deployment environment

A server-based network is recommended for high-volume deployments. The lab must include the previous minimum requirements, in addition to the following:

  • A Windows domain for the computers to join and to host user accounts. This can be a Windows Server 2003 or Windows Server 2008 R2 domain.

  • A build server in the domain to host the build files and images. This can be a workstation or server class computer installed with Windows 2000 Professional or a later version of Windows. A Windows Deployment Server or a Preboot Execution Environment (PXE) Server is highly recommended for this role.

  • Network switches and cabling. For high-volume deployments, 100 megabits/sec (Mb/s) or faster is recommended to accommodate high volumes of data.

  • DHCP services. DHCP services provide IP addresses to client computers.

  • Domain Name System (DNS) services. DNS services provide TCP/IP host name resolution to client and server computers.

  • Windows Internet Name Service (WINS) services. WINS services provide NetBIOS name resolution to client and server computers.

  • Keyboard/video/mouse (KVM) switches. It can be helpful to connect the client workstations to a KVM switch to minimize the floor space required to host the workstations.

For more information on deploying an image from a server, see Deploy Windows Using Windows Deployment Services.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft