Chapter 18. Compatibility Testing for Windows Server 2003

In This Chapter

• The Importance of Compatibility Testing

• Preparing for Compatibility Testing

• Researching Products and Applications

• Verifying Compatibility with Vendors

• Lab-Testing Existing Applications

• Documenting the Results of the Compatibility Testing

• Determining Whether a Prototype Phase Is Required

At this point in the book, the new features of Windows Server 2003 have been presented and discussed in depth, as have the essential design considerations and migration processes. The goal of this chapter is to examine the process of testing the actual applications that rely on the Windows Server infrastructure.

This chapter provides insight into the steps necessary to gather information before the testing process begins, how to actually test the applications and document the results, and how to determine whether a more extensive prototype testing process is needed. Going through this process is vital to ensure the success of the project and avoid a displeased user community. The application testing process is intended as a quick way to validate the compatibility and functionality of the proposed end-state for the upgrade.

Currently many companies are seeking to "right-size" their network environment, and might be using the upgrade as a chance to actually reduce the number of servers that handle file and print processes on the network. At the end of the process, fewer servers will handle the same tasks as before, and new functionality might have been added, making the configurations of the individual servers that much more complex, and making it even more important to thoroughly test the mission-critical networking applications on the server. For example, Windows Server 2003 manages user connections and application server functions as well as providing enhanced fault tolerance capabilities, prompting some organizations to replace existing Windows NT4 or Windows 2000 servers with Windows Server 2003.

Thus it's even more important to test this configuration to ensure that the performance meets user expectations and that the everyday features used by the employees to share knowledge and collaborate are in place.

The results of the application compatibility testing process will validate the goals of the project or reveal goals that need to be modified because of application incompatibility or instability. If one key application simply won't work reliably on Windows Server 2003, a Windows NT4 Server or Windows 2000 Server might need to be kept as part of the networking environment, which changes the overall design. As discussed in Part II of this book, "Windows Server 2003 Active Directory," a variety of different combinations of Windows server configurations can be combined in the end configuration, so the chances that there will be a way to keep the troublesome applications working in the new environment are good.