Previous Table of Contents Next


Chapter 2
Installing Windows NT Server

  Windows NT Server Installation Requirements
  Installing Windows NT Server Using Floppy Disks And/Or CD-ROM
  Installing Windows NT Server From MS-DOS Or Windows 3.x
  Installing Windows NT Server On A RISC Computer
  Upgrading A Windows NT Server Installation
  Initial Configuration Tips For Windows NT Server
  Troubleshooting A Failed Installation Of Windows NT Server
  Migrating A Lan Manager Or Novell Netware Server

This chapter is designed to familiarize you with the installation options for Windows NT Server, so there will be no surprises when you finally install it. This chapter is basically broken down into four sections. The first is our discussion of the actual methods of installation and a walk-through of the CD-ROM installation method. The next section deals with your initial configuration of Windows NT Server after you have installed the product. And should you have any problems with the installation, the following section deals with troubleshooting. Finally, we will look at the tools that are available for migrating your Microsoft Lan Manager (1.x) and Novell NetWare servers to Windows NT Server.

Installation

There are several methods that you can use to install Windows NT Server to a new computer. For an Intel-based computer, you can install Windows NT Server using floppy disks, three boot floppies and CD-ROM, or from a network share using MS-DOS and the WINNT.EXE installation program. All of these methods eventually execute the same installation program. They differ only in their initial methodology of getting the source files copied to the computer. There is also a slight difference in installation for RISC-based computers, as these computers are limited to installation from the CD-ROM only. You can upgrade a Windows NT Server installation by using any of the preceding methodologies or running a Windows NT version of WINNT.EXE called WINNT32.EXE.

In this section, we will look at each methodology to help you choose the best method to get Windows NT Server up and running. But, before we start our discussion of the actual installation process, there are a few things you should consider first. There are certain requirements for a successful Windows NT installation. After we look at these requirements, we can move on to our installation discussion. We will start by discussing an installation on the Intel processor platform. After that, we will look at the differences in the installation process for the various RISC platforms. Finally, we’ll review the upgrade process.

Before You Begin The Installation

Generally speaking, the installation process is pretty straightforward. It is rare, but not unheard of, to encounter a problem with the installation. You can avoid severe problems and surprises by adhering to the following basic rules:

  Check the Hardware Compatibility List (HCL)This booklet is included with your source media package and provides a listing of every hardware platform that Microsoft has tested to ensure compatibility with Windows NT Server. In this document, you may find specific BIOS requirements for your particular hardware platform, or even specific BIOS requirements for peripherals (such as video or SCSI adapters). If your hardware platform is not listed by name, don’t despair. It only means that the platform has not been tested for complete compatibility. In this case, look through the list of peripherals to see if you can identify any problem areas you should consider before installation (such as an unsupported network adapter). If your system, or peripherals are not listed, you may want to spend the time to download the latest version of the HCL from the Microsoft Web site at http://www.microsoft.com/kb/articles/q131/3/03.htm.


TIP:  If you plan on installing Windows NT Server from your CD-ROM, check to see if it is listed in the HCL. If it is a SCSI CD-ROM, check to see if your SCSI controller is listed. If it is an IDE CD-ROM, Windows NT Server supports the ATAPI interface and proprietary CD-ROM controllers from Sony, Panasonic, and Mitsumi. If the installation process does not autodetect your CD-ROM controllers, try and manually install these one at a time. If they all fail, you will be required to install using the MS-DOS method (WINNT.EXE), which we will discuss later in this chapter.
  Read SETUP.TXT and README.WRI—These files contain specific information not often mentioned in the HCL about various hardware platforms and peripherals. SETUP.TXT can be found in the root directory of the CD-ROM drive. README.WRI is a compressed file and is located in your installation subdirectory (I386 for Intel processors), and it will need to be manually expanded prior to being read.


You can manually expand the README.WRI file by locating the file README.WR_ (on your CD-ROM or installation disks) and running the MS-DOS expand program (located in your MS-DOS or Windows 3.x installation directory). For example:
     expand E:\I386\README.WRI C:\TEMP\README.WRI

Where E: is the letter of your CD-ROM drive.


  Check your free space—Windows NT Server requires about 130MB for a complete installation (this includes the minimum paging file requirement). If this amount of free space cannot be located on a single disk drive, the installation program will require that you reformat your disk drive in order to continue the installation. Of course, you can always exit the installation by pressing the F3 key, delete some files, then restart the installation process. But, it is better to have sufficient free space before you start.
  Check your hardware settings—Unlike MS-DOS, Windows NT does not support the sharing of interrupts on the ISA expansion bus. Only EISA, MCA, and PCI adapters can share interrupts. Make sure you have no I/O, DMA, or upper-memory conflicts, as well, before you start the installation process.


If a network card cannot be found during the installation process, you may be unable to install Windows NT Server. A resource conflict, such as using IRQ 3 for your network adapter when you also have your second communication port (COM2) using IRQ 3, may cause the installation to fail. You can avoid this by selecting a different IRQ for your network card before you begin the installation. There are other options, as well, which we will look at as part of the installation process a little later on.
  Obtain your OEM (Original Equipment Manufacturer) drivers—If you have proprietary or unsupported hardware, such as a network or SCSI adapter, you should assemble your driver disks before you begin your installation. During the installation, you will be given a chance to install these OEM drivers.


You can find many OEM drivers for Windows NT Server in the DRIVLIB subdirectory on the CD-ROM (including disk controller drivers, video drivers, printer drivers, and so forth). Even if you have an OEM disk, you should look in the subdirectory to see if a newer version is available. Don’t despair if you cannot find a driver there, because Microsoft also maintains online areas that contain drivers. These areas are located on the Internet at www.microsoft.com/msdownload, on Microsoft’s FTP site at ftp.microsoft.com, and in the Windows Driver Library (GO WDL) on CompuServe.
  Select a file system—Determine what file system you want to use before you install Windows NT Server. Currently, you can install Windows NT Server to a partition formatted as FAT, HPFS, or NTFS. Generally speaking, HPFS is only used for Lan Manager to Windows NT Server upgrades, but you could keep that file system if desired.


I recommend that you always use the FAT file system for the initial system partition. This partition can always be converted to NTFS later by using the CONVERT.EXE program. Installing Windows NT to the FAT file system guarantees that you will be able to access the NT system files from an MS-DOS boot disk should you have any unforeseen problems.
  Select an operating mode—Before you install Windows NT Server, make your determination as to what mode of operation you want the installation to operate in. Will it be a controller (either primary or backup), or will it be an application server operating in server mode? You must make this determination at install time, and once selected, the only way to change this mode is by reinstalling Windows NT Server.


Previous Table of Contents Next