Title: Chapter 5: Server Installation
1Chapter 5Server Installation
2Learning Objectives
- Make installation, hardware, and site-specific
preparations to install Windows 2000 Server - Install Windows 2000 Server using different
methods, including from a CD-ROM, from the
installation disks, over a network, unattended,
and from another operating system
3Learning Objectives (continued)
- Go through a Windows 2000 Server installation
step by step, and test the installation - Upgrade a Windows NT server and domain
- Create an emergency repair disk
4Learning Objectives (continued)
- Install a service pack
- Troubleshoot installation problems and uninstall
Windows 2000 Server
5Installation Preparations
- Preliminary steps
- Information about what hardware components are
installed - Determination of which file system to use
- Creation of an Administrator account
- Name of the server
- An installed NIC
- Determine which protocols to install
6Example Hardware Components Information Form
7Example Hardware Components Information Form
(continued)
8Troubleshooting Tip
- Record the BIOS setup information and save it for
later troubleshooting in the event that the
computers battery is defective or in case you
need it to restore one or more BIOS settings
9Sample BIOS Setup Screen
Figure 5-1 BIOS setup screen
10Troubleshooting Tip
- Obtain the latest device drivers before you start
the installation, such as those for the NIC,
HAL.dll (for SMP computers), SCSI adapters,
CD-ROM drives, RAID arrays
11Make Important Decisions in Advance
- How to partition the disk or disks
- What file system(s) to use
- What to name the server
- What password to use for the Administrator
account - What protocols to use
- What licensing method to use
- Whether to make the server a DC
12Decide Whether to Set Upa Dual Boot System
- Other systems that can reside on the same server
as Windows 2000 Server include MS-DOS, Windows
3.x, Windows 95, and Windows 98
13Partitioning
- If you create FAT and NTFS partitions, create the
FAT partition before you start (or leave an
existing FAT partition if you create a dual boot
system)
14Boot.ini File
- The Boot.ini file on the system partition
contains information about the location of both
operating systems in a dual boot configuration
15Sample Boot.ini File
Figure 5-2 Boot.ini file
16 FAT Partitions
- Windows 2000 will format a 2 GB or smaller
partition as FAT16 and a partition larger than 2
GB as FAT32
17Server Naming
- Use a name that is easy to type
- Make the name descriptive of the servers
function or of the organization - Select a name that is easy to remember and use
- Make sure the name is not already used on the
network
18Administrator Password
- Use a strong or difficult-to-guess password for
the critical Administrator account - Characteristics of a strong password
- Over seven characters long
- Has a combination of letters, numbers, and
symbols - Includes at least one symbol in characters two
through six
19Protocol Selection
- Consider using the default TCP/IP setup as a
starting point and add other protocols later as
needed
20Licensing Methods
- Per server licensing A server software license
based on the maximum number of clients that log
on to the server at one time - Per seat licensing A server software license
that requires that there be enough licenses for
all network client workstations
21Initial Server Installation
- Standalone server A server that is not a member
of a domain, but that is a member of an existing
workgroup or that establishes its own workgroup,
such as in peer-to-peer networking - Member server A server that is a member of an
existing Windows 2000 domain, but that does not
function as a domain controller - (Either type of server can be later set up as a
domain controller)
22Installation Options
- CD-ROM only
- Floppy disk and CD-ROM
- Network installation
- Installation from an existing operating system
- Unattended installation
23Installation Programs
- Use Winnt.exe from scratch (installation disks or
CD-ROM) and from computers already booted from
MS-DOS or Windows 3.x - Use Winnt32.exe from computers already booted
from Windows 95/98, Windows NT, or Windows 2000
(for an upgrade)
24Command-line Switches for Winnt
25Command-line Switches for Winnt (continued)
26Command-line Switches for Winnt32
27Command-line Switches for Winnt32 (continued)
28Command-line Switches for Winnt32 (continued)
29Command-line Switches for Winnt32 (continued)
30CD-ROM Installation
- Set the computers BIOS to boot first from CD-ROM
- Insert the Windows 2000 Server CD-ROM
- Turn the computer off and then back on (you may
need to press Enter to boot from CD-ROM) - After Winnt.exe starts, follow the instructions
on the screen
31Floppy Disk and CD-ROM Installation
- Set the BIOS to boot first from drive A
- Power off the computer
- Insert Setup Disk 1 and the CD-ROM
- Turn on the computer, booting from the Setup Disk
1 - After Winnt.exe starts, insert Setup Disk 2 and
follow the on-screen instructions
32Making Copies of the Setup Disk
- Format 4 floppy disks
- Insert the Windows 2000 Server CD-ROM
- Click Start and then click Run
- Enter the drive letter of the CD-ROM and the path
\bootdisk\makebt32.exe - Click OK
- Follow the on-screen instructions
33Network Installation
- Copy the installation files from the Windows 2000
Server CD-ROM which are in the folder \I386 - Share the hosts folder and set appropriate
permissions - Map the hosts shared folder from the target
server computer - Run Winnt.exe or Winnt32.exe from the shared
folder - Follow the on-screen instructions
34Installation from an Existing Operating System
- Boot the computer to use its existing operating
system - Insert the Windows 2000 Server CD-ROM
- Click Start, click Run, enter the drive letter of
the CD-ROM and the path to the Winnt.exe or
Winnt32.exe file, such as \I386\winnt32 plus any
switches - Follow the on-screen instructions
35Installation Tip
- If you install Windows 2000 from MS-DOS, you can
reduce the installation time from several hours
to under an hour if you start the SMARTDRIVE
utility before running Winnt.exe
36Unattended InstallationOver the Network
- Create an answer file using Setup Manager or
Notepad - Use the /s and /u (or /unattend) switches to
specify the location of the installation files
and of the answer file such as - Winnt32 /s\\mainserver\I386 /unattendunattend.tx
t - Use a uniqueness database and the /UDF switch to
further customize the unattended installation
37Unattended Installation via CD-ROM
- An alternative to a unattended network
installation is to create an answer file to use
along with booting via the CD-ROM, but name the
file, Winnt.sif
38Creating Duplicate Unattended Installations
- Use Sysprep.exe to clone computers that have the
same hardware configuration - Use Syspart.exe to clone computers that have
different hardware configurations
39Installation Troubleshooting Tip
- If Setup starts, but does not find mass storage,
restart the installation, press F6 as soon as
possible and load the manufacturers driver (such
as for a SCSI adapter) - If Setup does not start because you are using an
SMP computer, restart the installation, press F5,
and provide the computer manufacturers Hal.dll
40Installation Part 1
- When the Windows Setup starts, it inspects the
computer hardware and loads drivers and then
presents a screen on which to press Enter to
start the installation
41Installation Part 1(continued)
Figure 5-3 Beginning setup options
42Installation Part 1(continued)
- Read the licensing agreement and press F8
- Select the partitioned or unpartitioned disk
space on which to install Windows 2000
43Installation Part 1(continued)
Figure 5-4 Detecting partitions
44Installation Part 1(continued)
- Select the file system to use, FAT or NTFS
- Setup automatically checks the disks, copies
files, and reboots into the graphical mode
45Installation Part 2
- Setup gathers and verifies information about the
computer, such as the keyboard and pointing
device - Setup next enables you to configure regional and
keyboard settings, such as the language that you
use
46Installation Part 2(continued)
- Enter your name and the name of your organization
- Enter the product key which is obtained from the
back of the Windows 2000 Server CD-ROM jewel case
47Installation Part 2(continued)
Figure 5-5 Name and organization information
48Installation Part 2(continued)
- Select the licensing mode
- Enter the name of the server and the
Administrator accounts password - Select the Windows 2000 components to install
49Installation Part 2(continued)
Figure 5-6 Windows 2000 components
50Installation Part 2(continued)
- If there is an installed modem, provide the Modem
Dialing information - Verify the date and time
- Select the network configuration option, such as
Typical settings in order to install TCP/IP - Specify whether the computer will start off in a
workgroup or domain (if in a domain, provide the
account and password)
51Installation Part 2(continued)
- Wait for Setup to install components and files
and then click Finish
52Installation Part 2(continued)
Figure 5-7 Installing components
53Log On and Test the Server
- Press CtrlAltDel, enter Administrator as the
account name, and enter the Administrator
password you specified during the installation - Look for the Windows 2000 Configure Your Server
dialog box, which provides one method for
continuing to configure the server
54Configure Your Server Tool
Figure 5-8 Configuration dialog box
55Testing the Desktop Icons
- Test the desktop icons and other preliminary
functions of the server
56Desktop
Figure 5-9 Windows 2000 Desktop
57Upgrading a Windows NT 4.0 Server and Domain
- Coordinate a time for the upgrade
- Backup each server that will be upgraded
- Upgrade the PDC first
- Upgrade the BDCs one at a time
- Upgrade using Winnt32
58Upgrading a Windows NT 4.0 Server and Domain
(continued)
- Select the Upgrade to Windows 2000 (recommend)
option - Follow the directions in the Windows 2000 Setup
59Upgrading a Windows NT 4.0 Server and Domain
(continued)
Figure 5-10 Selecting the upgrade option
60Upgrading a Windows NT 4.0 Server and Domain
(continued)
- When the Active Directory Wizard starts, specify
if you want to join an existing domain tree or
forest, or start a new one - Establish the appropriate default domain and
other group policies - Convert the domain to native mode after the last
BDC is upgraded and there are no more Windows NT
servers
61Troubleshooting Tip
- Create an emergency repair disk for each newly
installed or upgraded server - Update the emergency repair disk every time you
implement an important change on a server, such
as after installing new hardware, drivers, and
software
62Troubleshooting Installation Problems
- The first step is to avoid problems through your
advanced preparations - Purchase components listed on the HCL
- Test all hardware before you start the
installation - Run the computers diagnostics before starting
- Run a comprehensive test of the hard disk before
starting
63Troubleshooting a Windows 2000 Server Setup
64Troubleshooting a Windows 2000 Server Setup
(continued)
65Troubleshooting a Windows 2000 Server Setup
(continued)
66Service Packs
- Check Microsofts Web site for the latest
information about service packs and the option to
download them - For more control, install service packs using the
Update command
67Windows Service Pack Update Switches
68Uninstalling Windows 2000 Server
- Backup the server files
- Use the disk management utilities in the new
operating system to delete the Windows 2000
partition, re-partition the drive, and format it
(or start a Windows 2000 installation and delete
the partition via Windows 2000 Setup) - Install the new operating system
69Chapter Summary
- Before you install Windows 2000 Server, make sure
the computers components are on the HCL - Make decisions in advance about how to complete
the installation options, such as how to
partition the disk and what file system to use
70Chapter Summary
- Use the appropriate installation option, such as
installing from CD-ROM, from the installation
diskettes, over the network, from another
operating system, or unattended - Make an emergency repair disk after you finish
the installation