Before you install a network operating system, you should gather up everything you need so that you don't have to look for something in the middle of the setup. The following sections describe the items you're most likely to need.
Obviously, you have to have a server computer on which to install the NOS. Each NOS has a list of the minimum hardware requirements supported by the operating system. Table 7-2 lists two kinds of minimum requirements for Windows Server 2003:
Microsoft's extremely inadequate published requirements
Your author's realistic recommendations for acceptable performance
Hardware | Microsoft's Published Minimum | Doug's Realistic Minimum |
---|---|---|
CPU | 133 MHz Pentium | 1 GHz Pentium |
RAM | 128MB | 2GB |
Free disk space | 1.5GB | 20GB |
Warning | Computer components are inexpensive enough that you shouldn't scrimp on hardware costs. |
You should also check your server hardware against the list of compatible hardware published by the maker of your NOS. For example, Microsoft publishes a list of hardware that it has tested and certified as compatible with Windows servers. This list is the Hardware Compatibility List, or HCL for short. You can check the HCL for your specific server by going to the Microsoft Web site at http://www.microsoft.com/whdc/hcl/default.mspx. You can also test your computer's compatibility by running the Check System Compatibility option from the Windows distribution disc.
You also need a server operating system to install. You need either the distribution discs or access to a copy of them over the network. In addition to the discs, you should have these items:
The product key: The installation program asks you to enter the product key during the installation to prove that you have a legal copy of the software.
Tip | If you have the actual CD-ROM discs, the product key should be on a sticker attached to the case. |
Manuals: If the operating system came with printed manuals, keep them handy.
A startup diskette: If you're installing on a brand-new server, you need some way to boot the computer. Depending on the NOS version you're installing and the capabilities of the server computer, you may be able to boot the computer directly from the distribution disc. If not, you need a floppy disk from which to boot the server.
Your license type: You can purchase Microsoft operating systems on a per-server or per-user basis. You need to know which plan you have when you install the NOS.
Tip | Check the CD-ROM distribution disc for product documentation and additional last-minute information. For example, Windows servers have a \docs folder that contains several files that have useful setup information. |
In most cases, the installation program should be able to automatically configure your server's hardware devices and install appropriate drivers. Just in case, though, you should dig out the driver discs that came with your devices, such as network interface cards, SCSI devices, CD-ROM drives, printers, and scanners.
This item isn't an absolute requirement, but the installation goes much more smoothly if you have a working Internet connection before you start. The installation process may use this Internet connection for several tasks:
Downloading late-breaking updates or fixes to the operating system: This can eliminate the need to install a service pack after you finish installing the NOS.
Locating drivers for nonstandard devices: This one can be a big plus if you can't find the driver disk for your obscure SCSI card.
Activating the product after you complete the installation (for Microsoft operating systems): For more information, see the section "Activating Windows," later in this chapter.
You spend lots of time watching progress bars during installation, so you may as well have something to do while you wait.