Sams Teach Yourself MCSE Windows NT Server in 14 Days: MCSE Exam Preparation Guide

Sams Teach Yourself MCSE Windows NT Server in 14 Days: MCSE Exam Preparation Guide

by David G. Schaer, Walter J. Glenn, Marcus W. Barton, Theresa Hadden

Bullets: { Approved and certified from Microsoft { Prepares you to pass Exams 70-067 and 70-068 { Offers practice questions in the book and at the E-zone site that will test your knowledge and help you become comfortable with the actual exam { Covers all comprehensive exam objectives in concise format { Makes it easy to access and retain the information you need…  See more details below


Bullets: { Approved and certified from Microsoft { Prepares you to pass Exams 70-067 and 70-068 { Offers practice questions in the book and at the E-zone site that will test your knowledge and help you become comfortable with the actual exam { Covers all comprehensive exam objectives in concise format { Makes it easy to access and retain the information you need to pass the exam COPY: Practice for the NT Server and NT Enterprise MCSE exams with Teach Yourself Windows NT Server4: MCSE Exam Preparation Guide. This Microsoft-approved, comprehensive training guide features test questions, tables, figures, and review sections to completely prepare you for Exams 70-067 and 70-068. Avoid enrolling in a class and save yourself thousands of dollars. Teach Yourself Windows NT Server 4: MCSE Exam Preparation Guide thoroughly trains you better for less. Visit the E-zone to have your additional review questions answered by mentors within 24 hours. Teach Yourself Windows NT Server 4: MCSE Exam Preparation Guide is sure to help you pass your exams.

  • Written for Microsoft exams 70-67 and 70-68.
  • Written by a Microsoft Certified Trainer.
  • Includes Internet Resource sections for the readers to obtain the most up-to-date information about a particular subject.

Read More

Editorial Reviews

A Microsoft approved training guide to passing the MCSE exams #70-67 and #70-86 for Windows NT Server 4. Features sample test questions, tables, figures, and review questions. Annotation c. by Book News, Inc., Portland, Or.

Product Details

Publication date:
Edition description:
1 ED
Product dimensions:
7.36(w) x 9.14(h) x 1.30(d)

Read an Excerpt

Teach Yourself MCSE Windows NT Server 4.0 in 14 Days -- Ch 3 -- Installing NT Server 4.0

[Figures are not included in this sample chapter]

Teach Yourself MCSE Windows NT Server 4.0 in 14 Days

- 3 -

Installing NT Server 4.0

by David Schaer and Theresa Hadden

3.1. Overview

Questions about installing NT Server can be as basic as reviewing your knowledge
of hardware requirements to as complex as questions on automated setup options. This
chapter guides you through each step of the installation and upgrade process of NT
Server 4.0. The questions that follow act as a review on areas of installation, upgrades,
and operating system coexistence.

This chapter leads you through the multiple phases of an NT installation. The
exam tests your ability to select equipment that is capable of running NT Server
4.0, install it both locally and from across the network, upgrade it from previous
operating systems, and troubleshoot common installation problems.

3.1.1. Objectives

The information in this chapter provides a basis for properly understanding how
to install Windows NT. The following Microsoft objectives as stated in the Preparation
Guide are addressed in this chapter:

  • Choose a protocol for various situations.

  • Install, configure, and troubleshoot various protocols including TCP/IP, NWLink,
    and NetBEUI.

  • Install Windows NT Server on Intel-based platforms.

  • Install Windows NT to perform various server roles including primary domain controller,
    backup domain controller, member server, and stand-alone server.

  • Install Windows NT using various methods including CD-ROM and over the network,
    and by using Network Client Administrator.

  • Configure protocols and protocol bindings.

  • Configure network adapters.

  • Choose the appropriate course of action to take to resolve installation failures.

3.1.2. Fast Facts

The following list of facts is a concise picture of the information presented
in this chapter. It acts as both an overview for the chapter and as a study aid to
help you do any last-minute cramming.

  • Minimum requirement for NT Server 4.0 is 486DX/33, 12MB RAM (16MB RAM is recommended),
    and 125MB free disk space on an Intel-based computer.

  • Minimum requirement for NT Server 4.0 on a RISC-based computer is 16MB RAM and
    160MB free disk space.

  • RISC-based machines can be installed only from a SCSI CD-ROM.

  • Multiple copies of NT can be installed on the same partition provided they are
    in separate directories.

  • There is no automatic upgrade option from Windows 95 to NT 4.0; you must reinstall
    all common applications.

  • The BOOT.INI file is a text file that contains the operating system
    boot choices.

  • The BOOTSECT.DOS file contains the original boot sector code before
    NT is installed.

  • The logic might sound backward, but you boot from the system partition and system
    files are held on the boot partition.

  • The boot and system partitions can be the same.

  • WINNT32.EXE is used to upgrade when NT is already installed on the computer.

  • You can set up Intel-based computers using either a local CD-ROM or from over
    the network. Floppy disks are not an option in NT 4.0.

  • The minimum video configuration is VGA.

  • Passwords are case sensitive, user names are not.

  • You can create an NTHQ diagnostic disk by running MAKEDISK.BAT to test
    the system for compatibility.

  • RDISK is the repair disk utility. It is used to both create and update emergency
    repair disks.

  • The emergency repair disk is not bootable.

  • The NT Setup Manager is used to create hands-free installation scripts.

  • You use hands-free scripts with over-the-network setup by specifying the /b,
    /u, /udf, and /s switches.

  • The /udf switch is used with a file containing overrides to the unattended
    script file called with the /u switch.

  • The SYSDIFF.EXE utility is helpful for installing large numbers of systems
    with preinstalled software requirements.

  • TCP/IP and NWLink IPX/SPX-compatible transport are both routable protocols.

  • TCP/IP is the default protocol.

  • Automatic detection of network adapter cards locates only the first network card.
    Select the Find Next button to detect additional network cards. Only one card at
    a time is detected.

  • Computer names can be up to 15 characters and must be unique across the network.

  • NetBEUI is non-routable; it requires bridging.

3.2. Choosing the Right Equipment

As operating systems become more complex, the level of equipment required increases
dramatically. You can personally cut corners to try to squeeze out a little more
power for your money when purchasing your personal system. However, for purposes
of the test, money is not the object; when choosing equipment, compatibility is the
major criterion.

3.2.1. The Hardware Compatibility List (HCL)

The equipment that you use must be supported on the HCL. The latest copy of the
HCL, shown in Figure 3.1, can be found at
or downloaded from

Figure 3.1. Microsoft's Web site provides the latest HCL information.

When troubleshooting a new system, one of the first things to confirm is that
all of the equipment being used is supported on the HCL. The HCL contains listings
of supported systems and accessories such as mice, SCSI cards, modems, network adapters,
tape drives, and video cards.

TIP: NTHQ is an NT diagnostic tool that can help detect hardware conflicts.
You create the bootable NTHQ disk by running makedisk.bat from the NT Server
CD's /support/hqtool directory. The NTHQ diagnostics are run automatically
when you boot from the disk. Booting from the disk enables the utility to interact
more closely with the hardware than diagnostics run from within NT.

A specific piece of hardware may be found compatible, but not necessarily across
all hardware platforms. For example, the same network card that might be approved
for use on an Intel x86-based system might not be approved on a DEC Alpha, MIPS,
or PowerPC.

3.2.2. Hardware Requirements

The hardware requirements for NT will vary based on what the system will be used
for. A system running Microsoft SQL and servicing 500 users has greater hardware
requirements than a system that is being used solely to provide file and print services
to a few dozen people. Because hardware requirements can vary so drastically based
on function, the tests are forced to focus on minimum requirements.

Intel x86 Installation Requirements

The Intel x86-based systems (80486, Pentium) are the most common systems used
to run NT Server 4.0. Because of this it is reasonable to expect the exam to place
more attention on this platform than on the RISC.

TIP: Be sure to know the minimum installation requirements for an x86 system.
They are

  • A 486DX/33 or above

  • 16MB of RAM

  • 130MB of free disk space

  • VGA or better video capabilities

  • CD-ROM or access to files via a network

  • A FAT or NTFS partition for installation

Processor Requirements T requires a 486DX/33 or above. NT also supports
systems with multiple processors. NT Workstation supports two, and NT Server supports
four. Various OEM versions of NT running on specialized hardware have been designed
to support up to 32 processors.

Memory Requirements The minimum amount of memory you can have is 16MB.
The terms random access memory (RAM) and physical memory will be used interchangeably.
RAM is the focus of many performance issues in Chapter 11, "Configuring and
Optimizing NT 4.0 Services." A system with a slower processor yet a large amount
of RAM can often outperform systems with faster processors and less memory.

Hard Disk Space Requirements The minimum hard disk space requirement, 130MB,
is listed for a system with 16MB of physical memory. Certain configurations of NT
require additional hard disk space. Configuring a large paging file for emulating
physical memory on a hard disk requires a hard disk of greater capacity. The default
pagefile size is the amount of RAM plus 12MB--the minimum pagefile size is 2MB. Configuring
the recovery option of writing system memory to a dump file (%SystemRoot%\MEMORY.DMP)
when a system failure occurs requires a pagefile on the system partition at least
equal to the amount of RAM in the computer.

Video Requirements The system must support VGA or greater resolution. You
will be asked to test the video driver and resolution during the installation.

TIP: It is better to install the standard VGA driver during installation.
After you have finished the installation, then you can install the specific drivers
for your video adapter card.

You must use the video drivers for NT 4.0. Video is handled differently in NT
4.0 than in previous versions of NT, and video drivers from NT 3.x are not
compatible. This is true also of Windows 95 drivers; they cannot be used as the drivers
for NT 4.0 systems.

Installation Media Requirements There are only two installation methods
for NT 4.0, CD-ROM or via a network. The CD-ROM drive may use either a SCSI or supported
IDE controller. In certain systems that support booting from the CD-ROM you might
not need to boot from a floppy disk to begin the installation. Because a majority
of systems do not support this feature, NT Server comes with three floppy disks that
are used to initialize the CD-ROM under a limited character-based version of NT.

Installation from a shared network device is supported for systems that do not
have a local CD-ROM drive. Performing multiple installations or upgrades is often
easier using the across-the-network method.

TIP: The fastest method for installing NT is via a network share. In fact,
you can point to multiple shares to speed the installation even more.

Primary File System Requirements On an Intel x86-based machine the system
partition can be either FAT or NTFS. Either file system is supported because the
NTLDR file initializes the mini-file system drivers to provide support for both on

RISC-Specific Issues

The same hardware requirements as for x86-based computers must be met when installing
NT Server 4.0 on a RISC-based computer with the addition of a SCSI CD-ROM and a 2MB
FAT partition.

Because RISC-based computers do not include the NTLDR file found on x86-based
NT installations, the mini-file system drivers required for NTFS access are not initialized
at boot time.

TIP: A RISC-based computer requires the following additional items:


  • A minimum of a 2MB FAT partition

Installation Media Requirements You have only one option here, a SCSI CD-ROM.
Because RISC machines boot off of firmware, only devices initialized by the system
directly will be available to perform the installation.

Primary File System Requirements FAT is the only file system initialized
by a RISC system's firmware. The FAT partition must be at least 2MB in size. This
gives the partition room to hold the OSLOADER.EXE, HAL.DLL,
and any *.PAL (DEC Alpha-specific) files to continue initializing
NT. RISC-based systems use the Arcinst.exe utility to create and format
partitions which may be NTFS. On RISC-based machines the system administrator can
secure the FAT partition through the Secure System Partition command on the Partition
menu of Disk Administrator. This security feature is unique to the RISC platform
and should not mislead you into thinking that FAT offers any file-level security.

3.3. Planning for Multiple Operating Systems

You might need or want to boot into a different operating system to perform certain
functions. The operating systems that you want available to boot into in addition
to NT will normally be installed before installing NT. Usually you will want to install
the operating systems in the order of DOS, Windows 95, then NT.

TIP: You can install your operating systems in any order. Just repair the
NT installation to return to a multiboot environment.

Don't confuse the concept of multiple operating systems with environment subsystems.
Environment subsystems let NT emulate an operating system so that applications written
for those systems can run unchanged under NT. Because not all applications will run
properly under the operating system emulators, NT provides the capability of booting
into other operating systems. Only one operating system can be active at a time.

You can select the default operating system to start at boot time through the
Startup/Shutdown tab in the System Properties dialog box under Control Panel, as
shown in Figure 3.2.

Figure 3.2. Setting the default operating system.

You also can adjust the time allowed to select an operating system boot choice
before the default is loaded. The default loads immediately if the time-out value
is set to 0.

Because FAT is the only file system supported by DOS, Windows 95, OS/2, and NT,
FAT must be the file system on the system partition on dual-boot systems. Other partitions
that contain file systems or configurations unique to a particular operating system
are available only when the supported operating system is active.

3.3.1. Coexistence with DOS

When DOS is installed on a computer, the boot sector is modified to call the DOS
initialization files. When NT is installed to the same partition, the NT installation
program copies the boot sector information to a file called BOOTSECT.DOS.
The information is saved before NT overwrites the boot sector so that it is available
to be called later.

The operating system that is selected and booted is the actual operating system.
It is in no way different in function because the boot process began with the NT
loader. The installation and configuration of common devices must be performed under
each operating system.

If the BOOTSECT.DOS file ever is deleted or corrupted or the NT boot
sector is accidentally overwritten, the NT boot sector can be replaced. To do this,
you must inspect the NT boot sector through the emergency repair options. Boot from
NT Server Setup Disk 1--the emergency repair disk is not bootable--and select the
option to repair. Under the repair options, clear all options except to inspect the
boot sector. Simply insert other required disks as prompted. This process repairs
both the boot sector and creates the BOOTSECT.DOS file if required.

3.3.2. Coexistence with Windows 95

Dual booting between Windows 95 and Windows NT is supported in the same way as
dual booting NT and DOS. If dual booting is already configured for DOS, boot into
DOS and run the Windows 95 setup. You must take care to ensure that you do not accidentally
install Windows 95 in the same directory as Windows NT; this would overwrite the
NT system files.

You must configure devices and software once under each operating system. Be especially
careful when changing network settings; changing the IP address under NT will have
no effect on the IP address under Windows 95. The same is true of physical hardware
configuration settings; if a network card is moved to a different IRQ the change
must be adjusted under both operating systems.

The only file system fully supported between NT and Windows 95 is FAT. However,
not all FAT is created equal. Systems installed with OEM versions of Windows 95 might
come installed with partitions formatted with an incompatible version of FAT called
FAT32. FAT32 partitions would be accessible only under Windows 95.

Windows 95 cannot understand partitions formatted with NTFS. Partitions created
as volume or stripe sets under NT are not accessible under Windows 95 even if formatted
as FAT. Disks that were mirrored under NT do not appear or function as mirrored sets
under Windows 95.

3.3.3. Coexistence with OS/2

Coexistence with OS/2 would be desirable for people who have an installed base
of Microsoft LAN Manager or IBM LAN Server, both of which were designed to run on

OS/2 1.x

Integrating OS/2 1.x is fairly simple. Before you load NT, simply install
and configure OS/2 1.x to allow for dual booting of OS/2 and DOS. To boot
between OS/2 1.x and DOS, select DOS from the options offered during the NT
boot. When the system loads to the command prompt you can type boot /os2
or boot /dos to enable the proper operating system.

OS/2 2.x

Like NT, OS/2 supports booting into multiple operating systems. If you plan to
support additional operating systems besides NT, you should first configure NT to
boot as described previously.

After installing NT, you can install OS/2 on the same system. A different partition
must be used for the OS/2 boot partition. The OS/2 BOOTLOADER can be used to select
the operating system boot choice of OS/2 or NT. If NT is selected, the system will
call the NTLDR that in turn reads the BOOT.INI to present the user a choice
of operating systems to boot into.

3.4. Upgrading Existing Operating Systems

The issues with upgrading are slightly different than issues with coexistence.
When upgrading it is important to confirm that NT will support all hardware required.

A system might have run without problems on Windows 95 or even NT 3.x but
might not work with NT 4.0. You should check the hardware against the HCL before
beginning the upgrade, and confirm the availability of drivers. Back up all data
before you begin the upgrade process.

3.4.1. Upgrading from OS/2 to NT 4.0

Although NT can be installed on a machine running OS/2 it does not upgrade the
operating system. NT will be installed as a separate operating system on the machine.
In previous versions of NT the High Performance File System (HPFS) was supported.
In NT 4.0 the OS/2 subsystem no longer supports HPFS.

3.4.2. Upgrading from Windows 95 to NT 4.0

This is a manual upgrade process. Although both NT and Windows 95 use a registry
to store configuration information, the two registries are incompatible.

CAUTION: Do not install Windows NT into the same directory as Windows 95.
You would be unable to boot either operating system due to registry incompatibilities.

You do the upgrade as a new installation of NT. You can perform the installation
from the local CD-ROM or from across the network. When you use the across the network
installation method you must execute WINNT.EXE. Even though Windows 95 supports
32-bit applications you cannot use the WINNT32.EXE utility to perform your
upgrade because it requires NT-specific support files.

TIP: You can install Windows NT from the RUN prompt under Windows
95 by using WINNT.EXE with the /w switch. This also requires that
you manually perform the first reboot.

It is necessary to reinstall all applications under NT. Install each application
into the same directory to save disk space. If you are installing a member server,
it will only contain default users, groups, and policies. A BDC will receive a copy
of the domain SAM database.

TIP: It is possible to get around reinstalling certain programs by using the
System applet on the Control Panel to add the location of the needed DLLs to the
Windows NT path.

3.4.3. Upgrading from NT 3.x to 4.0

The preferred method of upgrading a system that already has a version of NT loaded
is to use the WINNT32.EXE executable. This method can also be used to install
additional copies of NT on the same machine.

3.4.4. Updates and Service Packs

Periodically, Microsoft releases service packs to correct bugs or enhance the
released product. To install a service pack, run the UPDATE.EXE utility
from the source directory. Check with the hardware vendor before applying service
packs to machines with proprietary hardware. When applying service packs to machines
with multiple processors, special instructions are required.

3.5. Initiating NT Server 4.0 Setup

There are two basic setup methods: installation from a local CD-ROM and installation
from a source on the network.

3.5.1. Initiating NT Server 4.0 Setup from a Local Source

When you set up a single system, using a local CD-ROM as the setup source is usually
simplest. Having the source files held locally, on the CD-ROM, or even copied to
a directory on the hard disk can aid in later repairing the system files if necessary.
However, don't assume that all systems will have a CD-ROM drive or the extra hard
disk capacity to hold a copy of the source files.

You normally begin local installation by booting from the NT Server Setup Disk
1. This initializes a basic version of NT, which loads the drivers necessary to access
hardware including the CD-ROM drive. Figure 3.3 shows the installation at the point
of initializing SCSI and IDE controllers.

If NT does not support the local CD-ROM drive it can still be used as a local
source for the NT server installation files. An unsupported CD-ROM that is accessible
under DOS can be treated as a network device for installation purposes. The installer
would activate the CD-ROM under DOS and follow the directions for an over-the-network

TIP: When dealing with a non-supported CD-ROM, you can copy the installation
files to the hard drive and install from there.

Local installation is the only option for RISC machines. You must install them
by using a supported SCSI CD-ROM. RISC machines boot from firmware and do not require
the NT Server Setup disks.

Figure 3.3. Local setup initializing SCSI and IDE controllers.

3.5.2. Initiating NT Server 4.0 Setup from a Network Share Point

Over-the-network setup from a share point on the server allows the system administrator
to centrally control the installation files. The SA can either share the appropriate
directory (such as I386) on the NT CD-ROM or copy the source files to a shared directory
on the server.

The target machine must be connected to the file server via the network. If the
operating system on the target machine is DOS-based, the executable will be WINNT.EXE.
If the target machine is installed with an existing copy of NT, then WINNT32.EXE
can be utilized.


You can use both WINNT.EXE and WINNT32.EXE to perform either
local or over-the-network installations.

After executing the file appropriate to the client's operating system, the installation
copies source files to a partition on the target computer. The basic installation
creates a temporary directory called $WIN_NT$.~LS to hold the source files.
If the /b option is used with WINNT.EXE or WINNT32 an
additional directory, $WIN_NT$.~BT also is created. This directory provides
temporary storage for the information normally held on the three setup floppies.
Because the /b option alleviates the need for the floppy disks, it is a
common option to choose.

Other common switches to use with WINNT.EXE and WINNT32.EXE
are as follows:

/s This switch enables you to specify the source directory that contains the installation
/o or /ox Use these switches when you must rebuild the three NT setup floppies for use with
the CD-ROM.
/u This switch activates unattended setup mode. You must specify the name of the unattended
script file created using the Setup Manager from the NT 4.0 Resource Kit. The Setup
Manager is shown in Figure 3.4. Unattended mode also requires using the /s
switch to provide the source path.
/udf This switch loads a file that supersedes section values in the unattended script
file. Common override values can be assigned, or sections can be applied only to
individual machines based on their ID.

Figure 3.4. The entry screen for the Setup Manager.

The unattended script file is a text file that provides the answers to the common
setup questions. The system administrator controls the degree of user interaction.

After executing WINNT.EXE or WINNT32.EXE the initial files are
copied to the temporary directories as described earlier. As the final step of phase
one the system is rebooted.

Phase Two of NT Server 4.0 Setup

The installation setup screen is shown in Figure 3.5.

Figure 3.5. The installation welcome screen.

Using the unattended script files as described previously would alleviate you
from needing to respond to some or all of the screens that follow.

As seen in Figure 3.6, you have the option of specifying SCSI or IDE devices that
are not detected automatically.

Figure 3.6. You can select additional SCSI or IDE devices.

The license agreement is then displayed. You must agree to the license agreement
to continue installation.

A screen appears, as shown in Figure 3.7, showing the hardware believed to be
present in the system. You can override the hardware detected by the installation
program. You must confirm the hardware before continuing.

Figure 3.7. You are required to confirm detected hardware.

You must then choose a partition on which to place the installation, as seen in
Figure 3.8. Many installations of NT can reside on the same partition as long as
they are installed in separate directories. If extended DOS partitions exist, there
will be a separate listing for each logical drive.

Figure 3.8. Choose the installation partition.

You can create and delete partitions at this point of the installation. You next
determine whether the partition should be formatted or converted. If you format the
partition, all data on that partition will be lost.

In the example in Figure 3.9 the C drive will be converted to NTFS. This will
render all operating systems but NT from accessing the drive. The data will still
remain on the drive, but it will not be accessible to any operating system but NT.
If you planned on dual-booting the system the file system must be left intact as

Figure 3.9. Choosing to convert the C drive.

The default installation directory as shown in Figure 3.10 can be overridden.
Notice that the drive is not specified, only the directory; this is because the partition
has already been selected.

The system offers to perform a check of the hard disk for bad blocks, as shown
in Figure 3.11. If the hard disk is old or suspect in any way it is especially important
to allow the secondary test to be performed.

Figure 3.10. WINNT is the default installation directory.

Figure 3.11. The system can perform a check for bad blocks on the hard

Following the hard disk check, the setup program states it is copying files, as
shown in Figure 3.12. In the over-the-network setup the files are really being expanded
from the temporary directory to the selected installation directory. The network
is not accessible at this point of the installation.

Figure 3.12. When the copying is complete you are prompted to reboot
the system.

Figure 3.13 shows that the second phase of installation is complete.

Figure 3.13. The second phase of installation completes.

Phase Three of the NT Server 4.0 Setup

The NT Setup Wizard prompts you through the remainder of the installation referred
to as the GUI portion. Figure 3.14 shows the first screen of the third installation

Figure 3.14. The third phase of installation begins.

The registered user information is requested in Figure 3.15. This information
is for registration purposes only and will not affect the user, computer, workgroup,
or domain names.

Figure 3.15. Registration information is requested.

The license information must be completed before continuing. Figure 3.16 shows
the two licensing options.

Licensing requirements can vary significantly. In general, if you have only one
server, choose server-based licensing; if you have more than one server, it would
be better to select the Per Seat option.

The computer name, or NetBIOS name, of up to fifteen characters is requested in
Figure 3.17.

Figure 3.16. NT licensing options.

Figure 3.17. The computer name is requested.

Two systems on the same network cannot have the same computer name. If two computers
are installed with the same computer name on separate unconnected network segments
they will function properly until the segments are connected. The first system to
register the NetBIOS name with the network will be the system that functions. The
second receives a failure when attempting to register the NetBIOS name, and its network
capabilities are rendered inoperative.

You must select the server type. The three server type options are displayed in
Figure 3.18.

Figure 3.18. The three NT server types.

If you fail to select the function of the system properly you might need to reinstall.
NT does not provide a method of changing a stand-alone server into a domain controller
(PDC or BDC) or in the other direction.

The administrator password is case sensitive, as are other user passwords in NT.
Enter and confirm the administrator password as in Figure 3.19.

Figure 3.19. The administrator password is case sensitive.

Creating an emergency repair disk is optional, as seen in Figure 3.20. The repair
disk holds copies of the configuration information that might be required to troubleshoot
the system. You can create or update the emergency repair disk by using the Repair
Disk Utility, RDISK.EXE, at any time. Updating the repair disk whenever
significant changes to hardware, software, or users have been performed is good practice.

Figure 3.20. The emergency repair disk is optional.

Each of the optional components to install can be specified. Not all components
of each category must be selected, as shown in Figure 3.21.

The network portion of the installation commences. The system may communicate
with the network by using a standard network adapter card or may attach by using
remote access services. If neither of the selections, as shown in Figure 3.22, are
selected the system will not be able to run any of the network services.

Figure 3.21. Not all components must be selected.

Figure 3.22. Specify the type of network connection.

The Internet Information Server, commonly known as a Web server, can be installed
now or added later. Figure 3.23 shows the IIS Server installation option.

Figure 3.23. IIS can be added now or later.

The network adapter card can be detected automatically, as in Figure 3.24. If
multiple adapter cards are present, only the first one is detected. If the system
is configured to serve as a BDC it is important to confirm the card is attached to
a segment that allows connectivity to the PDC.

Figure 3.24. Installation of the network adapter cards.

If the network adapter card being used is not located automatically or is improperly
identified, you can select it manually from the list. If the card is not listed,
the driver might be available from the manufacturer, and you can add it as an unlisted

You can select one or multiple protocols at this time. Figure 3.25 shows the protocol
selection screen.

Figure 3.25. Initial protocol selection is made.

Select TCP/IP when there is a need for connection to the Internet or when systems
must communicate over an IP-routed network. NWLINK, or NetWare Link, is compatible
with Novell's IPX/SPX protocol. It can be used on a routed network whether or not
a NetWare server is present. NetBEUI (Network Basic Enhanced User Interface) is a
very fast protocol for use on single segments of a network. NetBEUI is not a routable
protocol; it can, like all other protocols, be bridged. If the computer being installed
is a BDC you must select at least one protocol that is also in use on the PDC.

In addition to the basic network services shown in Figure 3.26, you can also select
to install advanced services at this time. Advanced services include DHCP Server,
Remote Access Server, DNS server, and others, which are discussed in Chapter 11.

Figure 3.26. Selecting the basic network services.

After you select the services you must configure protocol settings for TCP/IP
or IPX/SPX, if either were selected. If you have selected to install the DHCP Server
service on the system you must configure TCP/IP manually; a DHCP server cannot be
a DHCP client. NetBEUI is self-configuring.

The protocol bindings are displayed in Figure 3.27. You can change the binding
order and thus the priority of the protocols relative to specific services.

Figure 3.27. The protocol binding order.

The system now initializes the network.

When installing a PDC the name of the domain being created is required. Figure
3.28 shows NTMASTER being installed as the PDC for the KNOWLEDGE domain.

Figure 3.28. NTMASTER is configured as the PDC for KNOWLEDGE.

Enter the appropriate time zone. Figure 3.29 shows the system configured for GMT+01:00.

Figure 3.29. Enter the time zone information.

The system displays the video information and requires that you test the video
configuration before continuing. In Figure 3.30 the video configuration is displayed.

Figure 3.30. Configuring the system video.If the video does not appear
properly during the test mode simply wait until the test completes and try a different

The final step is to create the emergency repair disk if the option was selected.
The emergency repair disk only reflects the system configuration at the time of installation
unless it is periodically updated using the Repair Disk utility, RDISK.EXE.
The emergency repair disk should be updated following any major system change including
hardware, software, and user configuration.

The BOOT.INI is updated to reflect the new installation of NT as the
default boot selection.

The installation is now complete.

3.6. Hands-Free Installations

Several methods are available to perform hands-free installations. The most common
method is by utilizing the NT Setup Manager to create text-based answer files. The
answer files are called during over-the-network installation when the /u
and /s switches are employed.

The NT installation can also be activated through Microsoft Systems Management
Server or by something as simple as a batch file called in a logon script.

Microsoft System Management Server can be used to force or push the installation
of various software packages to the target system. For example, a package containing
Microsoft Office 97 could be distributed and installed on the client machine. Not
all software packages provide a script that lets SMS perform an automated installation.

The sysdiff.exe utility allows an installation of NT to be enhanced by
including additional software. The software installed using sysdiff.exe
does not have to support scripting. In essence, the sysdiff.exe utility
creates a file containing system differences between a clean target machine and the
same machine after desired software has been installed. The difference file can be
applied to other target machines to lay down the software and update the registry.
Hardware and software resellers use the sysdiff.exe utility most commonly.

3.7. Uninstalling Windows NT

If you loaded NT for trial purposes, or if you want to turn a stand-alone or member
server into a controller, removing it at some point might be necessary. Uninstalling
NT, without losing other applications or data, requires only a few simple steps.

If NT was installed on a FAT partition, simply boot into DOS or Windows 95 either
from a system disk or by selecting the other operating system on multiboot machines.
A system disk is a better choice because it is often necessary to SYS the drive.

Next, delete the entire Windows NT directory structure from the %SYSTEM_ROOT%

Finally, delete the file pagefile.sys and all system files in the root
of the system partition, including NTLDR, NTDETECT.COM, BOOTSECT.DOS,
BOOT.INI, and--if it exists--NTBOOTDD.SYS.

If NT is installed on an NTFS partition and another copy of NT is installed in
another directory, delete the unwanted NT installation manually. The BOOT.INI
file must be manually updated to note the removal.

If NT is installed as the only operating system on an NTFS partition, remove it
by deleting the partition (the setup disks can be used for this).

3.8. Selecting Network Protocols

The exams will test your knowledge of four basic network protocols: TCP/IP, NWLink
(IPX/SPX), NetBEUI, and DLC. Remember to focus on what each protocol has in common
and at the same time what features make each protocol unique.

3.8.1. TCP/IP

TCP/IP has been popularized within NT and Microsoft exams. TCP/IP has gained so
much popularity over the years for several reasons:

  • TCP/IP is a routable protocol.

  • TCP/IP is the protocol the Internet uses.

  • TCP/IP is a common protocol implemented by all major network manufacturers.

3.8.2. NWLink (IPX/SPX)

NWLink is Microsoft's implementation that is compatible with Novell's implementation
of IPX/SPX. Although the name implies that the sole purpose of NWLink is to connect
to NetWare servers, that is not the case. In fact, NWLink may be the protocol running
on a pure NT network. Also, NWLink without either Client Services for NetWare (CSNW)
or Gateway Services for NetWare (GSNW) loaded would allow access to a NetWare application
server (such as Oracle or Sybase running as an NLM).

NWLink has several powerful features:

  • NWLink is a routable protocol.

  • NWLink alone can allow NetWare clients access to an NT application server.

  • NWLink alone can allow NT clients access to a NetWare application server.

3.8.3. NetBEUI

NetBEUI lacks the routing capability of TCP/IP and NWLink. The disadvantages of
NetBEUI on a WAN are often never seen by the small network administrator. In fact,
there are several times when NetBEUI may be the protocol of choice:

  • NetBEUI is completely self-tuning.

  • NetBEUI is the fastest protocol to use across RAS.

  • NetBEUI is the only RAS dial-in protocol to support the NetBIOS gateway feature.

3.8.4. Data Link Control (DLC)

The Data Link Control (DLC) is a nonroutable protocol used in NT for some specific
purposes, such as the following:

  • DLC is commonly used with a 3270 or 5250 emulator to talk directly to IBM mainframes
    and IBM AS/400 computers.

  • DLC is used with Hewlett-Packard print devices that connect to the network via
    JetDirect cards.

TIP: You should know that DLC cannot be used by clients to attach to a Microsoft
NT network.

3.9. Lab

This lab aids in your learning by testing you on the information presented in
this chapter, as well as by giving you exercises to hone your skills. Answers to
the review questions can be found in Appendix B, "Answers to Review Questions."

3.9.1. Review Questions

Question 1

The system administrator for Corporation B recently received a new RISC-based
machine. He is planning to install NT Server on the machine. Which of the following
installation methods are available to him?

A. Floppy disk



D. Shared network directory

Question 2

Corporation B has received 50 new Pentium computers capable of running Windows
NT. You want to install Windows NT on each of the systems with as little human intervention
as possible. You know that the installed video cards provide at least VGA resolution
but are of different brands on several machines. Which of the following steps must
you perform to automate the installations?

A. Create a differences file using sysdiff.exe

B. Create an unattended installation answer file

C. Use the over-the-network installation method

D. Install Microsoft System Management Server

Question 3

The system administrator of Corporation B is evaluating an x86-based Pentium clone
for use as the company's Web server. Which of the following are bootable disks that
will allow the system administrator to confirm NT Server compatibility?

A. The emergency repair disk

B. The NTHQ diagnostic disk

C. The Windows NT Server Setup Disk #1

D. A Windows 95 Start disk

Question 4

The primary domain controller for Corporation B is configured with TCP/IP, NetBEUI,
and DLC. A BDC is planned to be installed on the other side of a router. The router
is configured to allow NetBIOS broadcasts to pass on UDP Port 137. Which of the following
could be used as the sole protocol on the BDC during installation?





Question 5

The administrator of Corporation B created an emergency repair disk when he installed
NTSRVX. After the installation the administrator created a volume set on the computer.
Which of the following steps must the administrator perform to ensure that the emergency
repair disk reflects the new configuration?

A. Create a new emergency repair disk

B. Run the NT Server Setup Manager

C. Update the emergency repair disk

D. Run the repair disk utility

Question 6

A computer consultant wants the ability to demonstrate both NT Workstation, NT
Server, and Windows 95 on the same computer. What is the minimum number of hard disks
that will be required to load all of the desired operating systems and also allow
the consultant to demonstrate NTFS-specific features?

A. One

B. Two

C. Three

D. The three operating systems cannot coexist

Question 7

Which of the following installations will fail if a PDC is not accessible during

A. Stand-alone server

B. Backup domain controller

C. Primary domain controller

D. All of the above

Question 8

Which of the following parameters are the minimum required when configuring TCP/IP
on an NT Server?

A. IP address

B. Subnet mask

C. Default gateway

D. Bridge address

Question 9

Which of the following protocols are required to use a Hewlett-Packard JetDirect
print device?


B. NWLink



Question 10

Which of the following are routable protocols?


B. NWLink



Question 11

Which of the following protocols can be bridged?


B. NWLink



Question 12

Which of the following protocols can be used with RAS to act across the NetBIOS





Question 13

To allow NetWare clients to access a Microsoft SQL server, which protocol(s) must
be loaded on the NT Server?



C. NWLink


Question 14

Which of the following must be loaded on an NT server to allow access to files
on a NetWare file server?


B. NWLink



3.9.2 Exercise

Your company has acquired 50 new desktop computers and 20 laptops; you must install
Windows NT on each of them. How are you going to do the installations? How would
you create an unattended answer file?

© Copyright, Macmillan Computer Publishing. All rights reserved.

Read More

Customer Reviews

Average Review:

Write a Review

and post it to your social network


Most Helpful Customer Reviews

See all customer reviews >