Simulating the Proposed Client Computer Environment

  • Article

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 XP Professional. The recommendations presented here might not apply to all Windows XP Professional implementations. Focus on the considerations that apply to your lab design.

Client computer hardware

Include at least one client computer from each vendor and one of each model that will run Windows XP Professional in your production environment. If your organization uses laptops, docking stations, or port replicators, be sure to include components that fully represent the vendors and models. Be sure to obtain a BIOS update that is compatible with Windows XP Professional.

Develop a standard hardware configuration for Windows XP Professional as part of your deployment project. Lab testing can help you define and refine a standard configuration that is compatible with Windows XP Professional. Some of the components that need to be tested for compatibility include:

  • Universal serial bus (USB) adapters.

  • Compact disc (CD) and digital video disc (DVD) drives.

  • Sound cards.

  • Network adapters.

  • Video adapters.

  • Small computer system interface (SCSI) adapters.

  • Mass storage controllers.

  • Removable storage devices.

  • Pointing devices (mouse or trackball).

  • Keyboards.

To determine whether a device is compatible with Windows XP Professional, see the Windows Catalog link on the Web Resources page at https://www.microsoft.com/windows/reskits/webresources, and then look up the component. If a device is not included in the Windows Catalog list, contact the device vendor to find out if a driver is available.

Alternatively, you can use the Windows XP Professional CD to check hardware and software incompatibility. To obtain a report that indicates hardware and software incompatibilities and identifies device drivers that need to be updated, insert the Windows XP Professional CD in your drive and select Check System Compatibility. If updated drivers for your devices are not included with Windows XP Professional, contact the device vendors to obtain them.

On computers running Microsoft® Windows® 95 or Microsoft® Windows® 98 operating systems, you can check hardware and software incompatibility by using the log file called Upgrade.txt. Upgrade.txt is located in the Windows Installation folder. On systems running Windows NT Server, you can check hardware and software incompatibility by using the log file Winnt32.log. Winnt32.log also is located in the Windows Installation folder.

Note

  • Windows XP Professional does not support 16-bit drivers. If your components use 16-bit drivers, you need to obtain 32-bit drivers for those components.

Network connectivity

Provide connectivity to the same types of networks that you use in the production environment, such as a LAN, a WAN, or the Internet.

If you plan to use Routing and Remote Access or a proxy network service in the production environment, include these types of connections in the test lab.

Server-based services

Configure servers for the services used in the production environment. For example, include services such as:

  • DNS, WINS, and DHCP.

  • Directory services, such as X.500 and Novell NetWare.

  • File sharing.

  • Network printing.

  • Server-based line-of-business applications, both centralized and decentralized.

  • IntelliMirror® management technologies.

Remember to account for administrative services or tools, such as:

  • Remote operating system installation.

  • Server-based application deployment.

  • Tools for managing client computers (SMS, for example).

Domain authentication

If your organization uses, or plans to use, domain authentication, simulate your authentication configuration in the test lab. If you are migrating from Windows NT Server 4.0 to Windows Server 2003, plan for authentication in the mixed environment that will occur during the phase-in period.

Network management services

Include network services used in your environment, such as Simple Network Management Protocol (SNMP).

Network protocols

Use the protocols you plan to use in the production environment. Verify that the protocols you use on client computers work properly before connecting the client computers to the production network.

Applications

You need licenses for, and access to, the software for all applications, stand-alone or server-based, that is to be supported on Windows XP Professional client computers.

Peripherals

Include a representative sample of the types of peripherals, such as printers and scanners, used in the business environment.

Server platform interoperability

Simulate the server platforms to be accessed by Windows XP Professional client computers. You might need to establish connections with the following systems:

  • Windows Server 2003

  • Windows 2000 Server

  • Windows NT Server 4.0

  • Mainframes supporting 3270 emulation

  • UNIX or Linux

  • Other server operating systems

If you have a separate server test lab, consider connecting the client computer test lab to it, instead of installing servers in the client computer lab.

If you plan to deploy Windows XP Professional at the same time as Windows Server 2003, include every type of server that a client computer will be able to access during the deployment period.

Desktop configurations

As part of your Windows XP Professional deployment, your organization might decide to evaluate Standard Client configurations and Group Policy objects for managing them. Lab tests can provide information that will help you recommend specific configurations and Group Policy objects to management. If you decide to perform this type of evaluative testing, include side-by-side comparisons of different configurations and Group Policy object settings.

Plan to have enough computers of the same make and model to allow for the side-by-side evaluations. Evaluate client configurations based on performance, ease of use, stability, hardware and software compatibility, functionality, and security model. Evaluate Group Policy objects by verifying that they produce the desired result, particularly when more than one object applies to a configuration, and that the resulting logon time is acceptable.

Performance

Use the test lab to start evaluating the effect on your network traffic by testing for changes in baseline traffic patterns when there is limited user activity, for example, when conducting your pilot.

Production network connectivity

If you have separate test labs for clients and servers, you need to isolate them both from the corporate network. If you need to provide a connection from the test lab to the corporate network, plan how you will use routers to separate the two networks.