Chapter 9: Ready, Set, Install | Windows Server 2003 for Dummies

Installing Windows Server 2003 is relatively easy, but it can take more than an hour from start to logon. You can, however, reduce many of the delays with just a little planning. And by following our suggestions in this chapter, we hope that you can avoid some common installation problems, many of which relate to a lack of correct equipment. We also provide a troubleshooting section to smooth out any ruffles you encounter along the way.

Installation: Upgrade or New?

Whether you're installing Windows Server 2003 from scratch or upgrading from a previous version, planning can help ensure a smooth installation.

Upgrade, as the term implies, means that you currently have an operating system installed on your computer and you want to install Windows 2003 over the existing operating system while retaining as many settings as possible. Windows 2003 provides upgrade paths from Windows NT 4.0 with SP5 or greater and Windows 2000.

Tip

Note that there's also an upgrade path from beta versions of Windows 2003. If you select to perform an upgrade installation of Windows Server 2003 from a beta, we strongly recommend that you begin by backing up all the data on every machine that you plan to upgrade. (We cover backups in Chapter 17.) Although you can upgrade to Windows 2003 without losing current data, hardware and software sometimes have minds of their own and can mess things up. A smidgen of prevention can save you some real headaches !

Installing means you're adding Windows 2003 to a computer that may or may not have an existing operating system. On systems with existing operating systems, you can select to replace the current one or create a multiboot system. A multiboot system is a computer hosting two or more operating systems. You're given a choice on bootup as to which operating system will be loaded. In some multiboot configurations, data from one operating system will not be accessible from other operating systems (for example, NTFS partitions from Windows Server 2003 can't be accessed from Windows 95 or Windows 98).

If you're installing Windows Server 2003 for the first time, you need to make some decisions about how you're going to set up the server before you install the software. You can install Windows Server 2003 in the following three basic ways:

CD-ROM: This type of installation requires that you have a computer with a local CD-ROM drive installed. CD-ROM installations don't require a network interface card (NIC), but if you plan on connecting the system to a network, it's best to have the NIC in place during installation. We focus on this type of installation in this chapter.
Across the network: This type of installation requires network access and that the CD-ROM files be available on the network. Network access can be gained either from an existing operating system or a boot floppy.
Automated: This type of installation requires you to input installation information into a data file that you can then merge into a script file for execution.

You can launch the installation of Windows Server 2003 in several ways:

CD-ROM boot installation: If your computer allows the CD-ROM drive to participate in the boot sequence, you can boot the Windows 2003 installation program from the CD.
Floppy boot disks: If you don't have a bootable CD-ROM drive, don't fret; you can launch the installation from floppy disks. However, the setup boot floppy creation tool is no longer included on the CD; you'll have to download it from the Windows 2003 area of the Microsoft Web site. To locate the setup disk creation tool, go to http://www.microsoft.com/windowsserver2003/ and search for setup disks.
CD-ROM from operating system installation: If the existing operating system on your computer gives you access to the CD-ROM drive, you can launch the Windows 2003 setup without the boot floppies. (See the "Step-by-Step: Installing Windows 2003" section later in this chapter for details.)
Across the network installation: You can perform this if the Windows 2003 installation files are available on some other computer on the network. The files can be on a shared CD-ROM drive, or a copy of the contents of the distribution CD can be on a shared network drive. See the "Installing across a Network" section later in this chapter for details.
Remote installation: Microsoft has a remote OS installation procedure named Remote Installation Services (RIS) that enables network administrators to push a Windows 2003 installation out to network systems. (Pushing an installation means that an administrator can deploy Windows 2003 on a network without going to every client to launch the setup.)

Preparing for the battle

We offer the following pre-installation list to help you gather the information and equipment that you need for your setup. The Setup program in Windows 2003 doesn't require all the items that we list in the following sections, but we like to have everything handy when we perform an installation so that we don't need to run around looking for things during the process.

Manuals

The following is a list of books that you may want to have within arm's reach (this book, of course, is the most important):

Windows 2003 manuals: In some cases, the manuals you receive with Windows 2003 are in print form; in others, they're available only in electronic form from the distribution CD or online at the Microsoft Windows Web site at http://www.microsoft.com/windowsserver2003/.
Computer hardware manuals: These are the manuals for the base machine and all additional components or peripherals on which you plan to install Windows 2003. You especially want to have the manuals for your NIC(s) and video cards.
Modem manual (optional): Grab this manual only if you plan to install one or more modems on the server.

Software

If you don't want to hunt around halfway through the installation, make sure that you have the following software handy:

Windows Server 2003 CD-ROM: This disc is the CD-ROM that ships with Windows Server 2003. You also need the CD key from the sticker on the jewel case.
Windows Server 2003 Service Pack CD-ROM or downloaded file: Don't expect a service pack for Windows 2003 for at least three months after it's officially released. Until then, you can skip the "Windows 2003 Service Packs" section later in this chapter.
NIC driver: Windows 2003 Setup should find the NIC in the server, but keep a floppy with the necessary drivers handy in case it doesn't.
Small Computer System Interface (SCSI) drivers: Windows 2003 Setup should recognize all SCSI devices if they're listed in the Hardware Compatibility List (HCL) at http://www.microsoft.com/hwdq/hcl/.Again, keep the drivers handy just in case.

Hardware

Of course, setting up Windows Server 2003 also requires some hardware, particularly the following:

Computer: Make sure that the computer complies with the HCL. Remember that you'll need at least a 133-MH _z CPU, but we don't think you'll be satisfied with anything slower than 550 MH _z . You also want to have a mouse attached to the computer - it just makes life easier!
RAM: The more memory that you can afford, the better. You must have at least 128MB, but you'll get better results with 256MB or even 512MB.
CD-ROM drive: If you're installing Windows Server 2003 from a CD-ROM, you need a CD-ROM drive. Later model computers allow this drive to participate in the boot sequence, and this enables you to start your Windows 2003 installation directly from the CD.
Hard disk: You must have at least 1.5GB of free space, but we think you shouldn't even begin with less than 4GB of available disk storage space.
Modem: If the server connects to the Internet or provides access to remote users, a modem (either internal or external) is one way to provide this connection. We prefer at least a 56 Kbps modem.
Video: You need a Video Graphics Array (VGA) or higher resolution video adapter and monitor. We recommend Super Video Graphics Array (SVGA) as a minimum.
Cables: Depending on the components you install, you may need modem cables, telephone cables, power cords, monitor cables, and more.

Information

You need to make several choices as you go through the setup routine. You're better off if you already have an idea of what you're going to answer before you begin the installation. Consider the items in the following list:

SERVER1.TXT - SERVER4.TXT files: The Windows Server 2003 installation CD provides several files in the \docs subdirectory for some lastminute information and installation details gathered too late to include in the printed manuals. Check there for a lot of good information.
NTFS: NTFS is the Windows 2003 native file system and is much more secure than the File Allocation Table (FAT) file system. Unless you need backwards compatibility with older Microsoft operating systems on the same machine in a multiboot configuration, there's really no need to use FAT.
Licensing: You need to know how you purchased your Windows Server 2003 and client licenses because the Windows 2003 Setup program asks you whether you want per-seat or per-server licensing.
Computer name : Each computer needs a unique name that you can identify easily on the network.
Workgroup/domain name: If this is the first domain controller installed in a network, you must create a domain name. If this computer joins a current domain where a domain controller already exists, you're better off connecting this computer to a network with access to that domain. If you're installing Windows 2003 in a workgroup, you need the workgroup name. Remember it's an either-or setting, but you can always change your mind later.
Protocols: Determine which protocols the computer uses (or will use) to communicate. If you're planning to use the Transmission Control Protocol/Internet Protocol (TCP/IP), see Chapter 14 for more details. Decide whether you must configure TCP/IP manually or automatically through a Dynamic Host Configuration Protocol (DHCP) server. If this server connects to the Internet, make sure that you have a valid IP address.
Remote connectivity options: Determine whether the server connects (or will connect) to the Internet or will host a Web server. If so, you can install Internet Information Services (IIS) to provide Web services and Remote Access Services (RAS) for the connectivity. RAS can also enable your users or customers to dial into the network. You can always install RAS and IIS later. In either case, you need a working Internet connection.
Server roles: The game has changed in regard to the roles that servers can play when maintaining a domain. The function of your server may affect how you install Windows Server 2003, but it's no longer a lifethreatening decision because the server is not configured until after the initial installation is complete. See Chapters 11 and 12 for more details.