Resouce Guides / Windows 2000 Server / Installation and Configuration / Installation

Seven steps to a successful Windows 2000 installation

There's more to Windows 2000 installation than just a waiting client or server and a Windows 2000 CD-ROM. Before installing Windows 2000, complete this quick checklist.

1. Ensure that the systems that will be running Windows 2000 meet Microsoft’s minimum hardware requirements. Microsoft recommends the following:

If you’re preparing to install Windows 2000 Professional, you'll need:

  • Processor: A Pentium 133 or better
  • Memory: 64 MB
  • Hard disk: A 2 GB disk with 650 MB of free space

If you’re preparing for Windows 2000 Server or Advanced Server, you’ll need:

  • Processor: A Pentium 133 or better
  • Memory: 128 MB
  • Hard disk: A 2 GB disk with 1 GB of free space

2. Verify that your hardware, including network adapters, monitors, CD-ROM drives, and other important peripherals, are supported by the Windows 2000 platform. Compatibility errors related to upgrading should be minimal, as Windows 2000 and the Windows Driver Model include support for more peripherals and devices than the Windows NT 4 platform. You can check compatibility using Microsoft’s Readiness Analyzer, or you can Search For Compatible Hardware Devices.

3. Choose an install method. In addition to the installation methods administrators will be familiar with from the NT 4.0 platform, IT pros will find new options. The installation methods supported by Windows 2000 include:

  • Traditional CD-ROM-based installation
  • Network-based installation
  • Disk Duplication-based installation
  • Automated installation using the Windows 2000 Setup Manager Wizard
  • Remote Installation Services

4. Know which file system you’re going to use. Many important Windows 2000 features, including Active Directory Services, rely upon NTFS. However, you’ll also find Windows 2000 supports FAT and FAT32.

5. Select a licensing method. Per seat licensing requires that each client have a Client Access License (CAL). Per server licensing dictates the number of client connections a server can support. As a result, per server mode requires that each server connection a client establishes possess a CAL. Organizations operating multiple Windows 2000 servers will probably find per seat the most efficient licensing model.

6. Have your namespace planned properly. The time to design your domain structure isn’t when Windows 2000 prompts you for a domain or workgroup name - it’s before. Remember, too, that domain names in Windows 2000 take the fully qualified domain name structure,

7. Create a computer account. If you’re adding systems to a Windows 2000 domain, computer accounts must exist. Without a pre-configured computer account, the installer will require Administrator-level permissions. Appropriate passwords will also be required.

Contact Us | Authors | Subject Index | RSS Feeds

Copyright ©2007