Simulating the Proposed Server Environment

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

This section lists some components you might need to include in your lab to fully test Windows Server 2003. The recommendations presented here might not apply to all Windows Server 2003 implementations. Focus on the considerations that apply to your design.

Server hardware and drivers

Use the same type of hardware components and drivers that you use, or plan to use, on servers in the production environment. Be sure to obtain an updated BIOS that is compatible with Windows Server 2003.

Services and configurations

Use the same services and configurations that you will use in the actual deployment. For example, duplicate the Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), and Windows Internet Names Service (WINS) configurations.

User accounts

If you are migrating from Windows NT Server 4.0, set up your domain controllers as replicas of your production domain controllers, using copies of the production user accounts. You can use the Clone Principal tool (Clonepr.dll) to copy production users to your test domain. For more information about the Clone Principal tool, see the Microsoft TechNet link on the Web Resources page at https://www.microsoft.com/windows/reskits/webresources, and then search for Tools. Coordinate with your IT security division whenever you copy production data to test lab databases. For more information about security, see "Planning a Secure Environment" in Designing and Deploying Directory and Security Services of this kit.

Domain structure

If you are implementing Active Directory, simulate the domain hierarchy; for example, include a forest with multiple trees, a tree with parent and child domains, and transitive and one-way trust relationships, as appropriate. Reflect your IT administration structure (either centralized or decentralized). Include Active Directory sites as appropriate. For more information, see "Designing Domains for Testing" later in this chapter.

Group Policy settings

Duplicate the Group Policy settings from your production environment in the test lab. Properly testing Group Policy settings in the lab helps you identify whether implementing new features or technologies will require that you make changes to your Group Policy settings.

Server strategy

Include domain controllers, file and print servers, application servers, Web servers, database servers, and other utility servers that are, or will be, included in your production environment. If you plan to use SMS to deploy Windows Server 2003, include it in the test lab.

Mixed environments

To accommodate both the mixed environment that exists during a phased rollout and the Windows Server 2003 environment that will exist after the completion of the rollout, plan to include some native-mode and mixed-mode domains.

By simulating the interim state, you can identify functional problems that might occur during the phased implementation. The servers running operating systems other than Windows Server 2003 should mirror the services they perform in the current production environment. For more information, see "Designing Domains for Testing" later in this chapter.

Client computer configuration

Client computers in the test lab should conform to the standard configuration that your organization has established. They should have the same components and peripherals found in your production environment.

Use the same mix of client computers that is present in your production environment. If you plan to deploy Windows Server 2003 first and Windows XP Professional later, include in your test lab the client computer operating system that you will be using until Windows XP Professional is deployed.

If you plan to deploy Windows XP Professional first, test to see how the extended server functionality will be introduced into your environment as the infrastructure is deployed.

If you plan to have a phased rollout, include the same mix of client computers in your test lab that will be present in your production environment. For example, have client computers with Windows NT Workstation 4.0 and client computers with Windows XP Professional.

Network topology and protocols

Mirror the network topology and protocols that you use in your production environment as closely as possible. For example, if your production network uses both Ethernet and Token Ring, the test lab should include both.

WAN connections

If you have a WAN, the test lab should include routers for testing network latency or for testing domain controller and global catalog replication across the WAN link. If you have the facilities and budget, you might want to set up a secondary test lab at a remote location to test network latency across the WAN link. If you have a multinational organization, place the secondary test lab in a different region to test actual latency problems.

If you do not have a secondary test lab located where you can test the WAN link, you can connect two routers in the same lab with a cable and use a link simulator to test the link.

Remote connectivity

In the test lab, provide the same types of remote connectivity — such as Routing and Remote Access service and VPN — that will be included in your production environment so that you can test the Point-to-Point Tunneling Protocol (PPTP), Internet Protocol security (IPSec), Layer 2 Tunneling Protocol (L2TP), and Demand Dial Routing.

Peripherals

Include a representative sample of the types of peripherals used in your production environment. For example, include the same types of printers and scanners, along with their associated drivers.

Interoperability

If you plan to implement Windows Server 2003 so that it operates with networks or computers using another operating system, mimic the interoperability infrastructure. For example, include connections to mainframe hosts, UNIX systems, or other network operating systems. To keep your test lab configuration manageable, decide which interoperability scenarios are most important to your organization and focus on those.

Administrative tools

Include the tools (Windows Server 2003, third-party, or custom built) that you currently use or plan to use for server-based administrative tasks. Test the tools for compatibility and effectiveness in the new environment.

Fault tolerance techniques

Test any fault tolerance techniques you plan to use in your production environment. For example, if you plan to use clustering, include a server cluster in the test lab.

Terminal Services

If you plan to implement Terminal Services, install the appropriate mix of applications on the server so that you can assess the effect of running applications in a multiuser environment. You might need to modify the default operating environment for some applications to obtain the desired functionality. For more information about hosting applications using Terminal Services, see "Hosting Applications with Terminal Server" in Planning Server Deployments of this kit.

Protecting the production network

Be sure you isolate the test lab from your corporate network. If you need to provide a connection from the test lab to the corporate network, plan how to regulate and control the connection and be sure to devise a way to quickly terminate the connection.

You can design router configurations to protect the production network. For example, consider using a multihomed router with two network adapters to connect the test lab to the production network for specific, controlled uses. Configure the router so that the production network can access the test lab network, but the test lab network cannot access the production network. This approach protects the production environment from events that might occur in the test lab, but allows a user in production to access test lab resources. For example, you could use this approach to test logon scripts on a test lab server with a limited number of users before moving the scripts to a pilot in the production environment.