Upgrading a Single Member Server

The direct upgrade approach from Windows 2000 to Windows Server 2003 is the most straightforward approach to migration. An upgrade simply takes any and all settings on a single server and upgrades them to Windows Server 2003. If a Windows 2000 server handles WINS, DNS, and DHCP, the upgrade process will upgrade all WINS, DNS, and DHCP components, as well as the base operating system. This makes this type of migration very tempting, and it can be extremely effective, as long as all prerequisites described in the following sections are satisfied.

Often, upgrading a single server can be a project in itself. The standalone member servers in an environment are often the workhorses of the network, loaded with a myriad of different applications and critical tools. Performing an upgrade on these servers would be simple if they were used only for file or print duties and if their hardware systems were all up to date. Because this is not always the case, it is important to detail the specifics of each server that is marked for migration.

Verifying Hardware Compatibility

It is critical to test the hardware compatibility of any server that will be directly upgraded to Windows Server 2003. In the middle of the installation process is not the most ideal time to be notified of problems with compatibility between older system components and the drivers required for Windows Server 2003. Subsequently, the hardware in a server should be verified for Windows Server 2003 on the manufacturer's Web site or on Microsoft's Hardware Compatibility List (HCL), currently located at http://www.microsoft.com/whdc/hcl.

Microsoft suggests minimum hardware levels on which Windows Server 2003 will run, but it is highly recommended that you install the OS on systems of a much higher caliber because these recommendations do not take into account any application loads, domain controller duties, and so on. The following is a list of Microsoft's recommended hardware levels for Windows Server 2003:

• Intel Pentium III 550MHz CPU or equivalent

• 256MB RAM

• 1.5GB free disk space

That said, it cannot be stressed enough that it is almost always recommended that you exceed these levels to provide for a robust computing environment.

Note

One of the most important features that mission-critical servers can have is redundancy. Putting the operating system on a mirrored array of disks, for example, is a simple yet effective way of increasing redundancy in an environment.

Verifying Application Readiness

Nothing ruins a migration process like discovering a mission-critical application will not work in the new environment. Subsequently, it is very important to list all applications on a server that will be required in the new environment. Applications that will not be used or whose functionality is replaced in Windows Server 2003 can be retired and removed from consideration. Likewise, applications that have been verified for Windows Server 2003 can be designated as safe for upgrade. For any other applications that may not be compatible but are necessary, you either need to delegate them to another Windows 2000 server or delay the upgrade of that specific server.

In addition to the applications, the version of the operating system that will be upgraded is an important consideration in the process. A Windows 2000 server install can be upgraded to either Windows Server 2003 Standard Server or Windows Server 2003 Enterprise Server. A Windows 2000 Advanced Server install can be upgraded only to Windows Server 2003 Enterprise Server, however. Finally, only Windows 2000 Datacenter Server edition can be upgraded to Windows Server 2003 Datacenter Server.

Backing Up and Creating a Recovery Process

It is critical that a migration does not cause more harm than good to an environment. Subsequently, we cannot stress enough that a good backup system is essential for quick recovery in the event of upgrade failure. Often, especially with the inplace upgrade scenario, a full system backup is the only way to recover; consequently, it is very important to detail fallback steps in the event of problems.

Upgrading a Standalone Server

After all various considerations regarding applications and hardware compatibility have been thoroughly validated, a standalone server can be upgraded. Follow these steps to upgrade:

1.	Insert the Windows Server 2003 CD into the CD-ROM drive of the server to be upgraded.
2.	The Welcome page should appear automatically. If not, choose Start, Run and then type d:\Setup, where d: is the drive letter for the CD-ROM drive.
3.	Click Install Windows Server 2003 (Enterprise Edition).
4.	Select Upgrade from the drop-down box, as indicated in Figure 17.1, and click Next to continue. Figure 17.1. Starting the Windows Server 2003 upgrade.
5.	Select I Accept This Agreement at the License screen and click Next to continue.
6.	The following screen prompts you to enter the 25-character product key. You can find this number on the CD case or in the license documentation from Microsoft. Enter the product key and click Next to continue.
7.	The next screen allows for the download of updated Windows Server 2003 files. They may be downloaded as part of the upgrade or installed later. For this example, select No, Skip This Step and Continue Installing Windows. Then click Next to continue.
8.	The next prompt is crucial. It indicates which system components are not compatible with Windows Server 2003. It also indicates, for example, that IIS will be disabled as part of the install, as you can see in Figure 17.2. IIS can be re-enabled in the new OS but is turned off for security reasons. Click Next after reviewing these factors. Figure 17.2. Checking the System Compatibility report.
9.	The system then copies files and reboots, continuing the upgrade process. After all files are copied, the system is then upgraded to a fully functional install of Windows Server 2003. If upgrading to Windows Server 2003 R2, setup will then invoke the R2 upgrade process by asking to insert the second CD containing R2 information. Once inserted, the final R2 upgrade process can take place.

Note

Many previously enabled components such as IIS are turned off by default in Windows Server 2003. Ensure that one of the post-upgrade tasks performed is an audit of all services so that those disabled components can be re-enabled.