Microsoft KB Archive/242859

= Preparing Your x86-Based Member Servers for Upgrade to Windows 2000 =

Article ID: 242859

Article Last Modified on 8/6/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition

-



This article was previously published under Q242859



SUMMARY
This article describes how to prepare your x86-based member servers for upgrading to Windows 2000.



Read the Preinstallation Documents
The network administrator should read the following three important documents for x86-based systems before attempting an upgrade:
 * The Hardware Compatibility List (HCL), which is located in the Support folder on the Windows 2000 Server Installation CD-ROM
 * The Read1st.txt file, which is stored in the root folder of the CD-ROM
 * The Relnotes.doc file, which is stored in the root folder of the CD-ROM

The Hardware Compatibility List
The list is comprehensive, but be aware that Microsoft updates the information on a continuing basis. You can find the updated list by visiting the following Microsoft Web site:

http://www.microsoft.com/whdc/hcl/default.mspx/

The Read1st.txt File
The Read1st.txt file provides late-breaking, critical, or other preinstallation or upgrade information that supplements the Windows 2000 documentation.

The Relnotes.txt File
This file contains a detailed, technical description of additions and should be used to assist in making informed decisions concerning deploying member servers in your network.

Record System Information
Make sure that you record all system information pertinent to each server before beginning an upgrade. This allows administrators to refer to important information to assist in getting a member server back to its original condition if a problem occurs while upgrading.

You can view server system information in Windows NT 4.0. On the Administrative Tools menu, click Windows NT Diagnostics. To print the information, click Print Report on the File menu in Windows NT Diagnostics Manager.

Back Up Important Files
Make sure to back up all of your important files to a backup tape or a share on your network.

Back Up Hard Disk Configurations
You can save hard disk configuration information to a floppy disk in Disk Administrator by pointing to Configuration on the Partition menu, and then clicking Save.

If a drive uses the NTFS file system, you can leave it as it is. Windows 2000 Setup converts it to the version of NTFS included with Windows 2000. Also, disable any disk mirroring.

Determine Software Compliance
Software designed for Windows 2000 takes advantage of Windows 2000 features such as Active Directory. However, any software written for Windows 2000, Microsoft Windows NT, Microsoft Windows 95, or Microsoft Windows 98 should run properly in Windows 2000. Software that was written for 16-bit versions of Windows (Microsoft Windows 3.x) or MS-DOS should work in a Windows 2000 environment, but is subject to the following considerations:
 * The software might require special configuration files, such as the Autoexec.nt and Config.nt files.
 * The 16-bit software might have or require special device drivers that are no longer available or are incompatible with Windows 2000.

Make sure to test the software thoroughly in a lab environment before risking down time and data loss in a production environment.

Determine System Requirements
The first step in installing or migrating servers is to take a hardware inventory and compare it to the Windows 2000 HCL to verify that the servers are compatible with the operating system.

Requirements for x86-Based Systems
Each server in the network infrastructure must meet minimum requirements for Windows 2000 Server to operate efficiently. In addition, an upgrade could require much more disk space than a new installation. As you add Active Directory functionality, the existing user accounts database can expand by up to a factor of ten during the upgrade process.

Upgrade or Perform a New Installation on x86-Based Systems
When there are member servers on the network that already have operating systems installed, the upgrade to Windows 2000 is primarily automated. During the upgrade process, Windows 2000 migrates the current settings for the operating system, and no administrator input is required.

Pre-Upgrade Checklist
Upgrading member servers to Windows 2000 requires that computers be compatible with the new operating system. Before starting Setup for Windows 2000 Server, use the following checklist:  Check event logs for errors. In Windows NT Server 4.0, check the System, Application, and Security event logs in Event Viewer to verify that no errors are currently logged. If errors exist, you should correct them before upgrading to Windows 2000 Server. Back up system and important files. Perform a full backup of all drives in the system. If you are using the Windows NT Backup program, confirm that there are no errors after the backup process is complete by checking the Winnt\Backup.log file.

You can also back up the registry on member server by using the Regback.exe utility in the Windows NT 4.0 Server Resource Kit. This tool backs up registry hives to files without the use of tape. You can restore the registry by using Regrest.exe, which is also included with the Windows NT 4.0 Server Resource Kit. Remove software and utilities. Remove any virus scanners, third-party network services, or client software. Read the Release Notes file (Relnotes.htm on the Windows 2000 Server CD-ROM) for information about any known problems with specific programs. Remove uninterruptible power supply (UPS) devices. Disconnect the serial cable that connects any UPS devices. Windows 2000 Server attempts to automatically detect devices connected to serial ports, which can cause problems with the detection process. IRQ reservations and the Emergency Repair Disk (ERD). If your system contains non-Plug and Play Industry Standard Architecture (ISA) devices, set your computer's BIOS to reserve all IRQs currently in use by non-Plug and Play ISA devices. Not doing so could result in the following error message:

INACCESSESSIBLE_BOOT_DEVICE

In some cases, the non-Plug and Play ISA devices might not function. You should also update your ERD.

Inventory of Existing Hardware
Before starting the Windows 2000 upgrade process, document the following information for each member server:
 * The manufacturer, make, and model of the computer being upgraded.
 * The amount of physical memory installed.
 * The type of network adapter installed.
 * Any non-Plug and Play devices.
 * The UPS connected to the server.
 * The type of external hard disks connected to the system.
 * The hard disk partitioning and free disk space available.
 * Any hardware or software RAID in use.
 * Which file systems (FAT16 or NTFS) are in use.
 * Type of CD-ROM drive installed.
 * The operating system and any service packs currently in use.

Ensure Software Reliability and Compatibility
To ensure software reliability and compatibility, check the following items for the software you intend to run:
 * For which operating system was a program written (Windows NT, Windows 98, Windows 95, Windows 3.x, or MS - DOS?
 * Was the program written to operate in a specific network environment? For which version of that network?
 * Are program and program configuration files stored on a server or on the client computers?
 * Are data files stored on a server or on client computers?

Keywords: kbenv kbinfo kbsetup KB242859

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.