1. Chapter 5: Server Installation

2. Learning 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

3. Learning 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

4. Learning Objectives (continued)
Install a service pack
Troubleshoot installation problems and uninstall Windows 2000 Server

5. Installation 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

6. Example Hardware Components Information Form

7. Example Hardware Components Information Form (continued)

8. Note Specifics of Driver
Screenshot
of hardware device
(Ctrl-Alt-PrtScrn)

9. Troubleshooting Tip
Record the BIOS setup information and save it for later troubleshooting in the event that the computer’s battery is defective or in case you need it to restore one or more BIOS settings
Try f1 on gateway during gateway screen on boot
A lot of systems tell how to get into setup at the beginning of the boot, e.g. “Hit DEL to enter setup

10. Sample BIOS Setup Screen
Note Boot Order
Figure 5-1 BIOS setup screen

11. Troubleshooting 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
Check device site for latest drivers
I suggest you let Win2K install its default, then a later time install newer drivers

12. Make 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 (Domain Controller)

13. Decide Whether to Set Up a 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
If you decide this, you are limited to a FAT partition

14. Partitioning
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)
You cannot see NTFS systems from a FAT booted system

15. Boot.ini File
The Boot.ini file on the system partition contains information about the location of both operating systems in a dual boot configuration

16. 2 sections: boot and Operating systems that can be started
Sample Boot.ini File
Figure 5-2 Boot.ini file
2 sections: boot and Operating systems that can be started

17. Advanced RISC Computing (ARC) pathname
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
Operating system is is a folder \WINNT
multi(0) on a non-scsi disk installed (always has the value 0)
disk(0) (always 0 for non-scsi)
rdisk(0) on first disk on the channel path. 1 for second disk 2 for third disk, 3 for forth disk
partition(1) in partition 1
multi(0)disk(0)rdisk(1)partition(2) \WINNT="Microsoft Windows 2000 Professional" /fastdetect
rdisk(1) on second disk on the channel path.
partition(2) in partition 2
scsi(1)disk(2)rdisk(0)partition(1) \WINNT="Microsoft Windows 2000 Professional" /fastdetect
scsi(0) scsi id = 1
disk(2) third disk in the scsi chain
rdisk(0)

18. FAT Partitions
Windows 2000 will format a 2 GB or smaller partition as FAT16 and a partition larger than 2 GB as FAT32

19. Server Naming Use a name that is easy to type
No to NJrt1242
Make the name descriptive of the server’s function or of the organization
NCOMPRIME
Select a name that is easy to remember and use
Make sure the name is not already used on the network

20. Administrator 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 m!cha3l
Includes at least one symbol in characters two through six

21. Protocol Selection
Consider using the default TCP/IP setup as a starting point and add other protocols later as needed

22. Licensing 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

23. Initial 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)

24. Installation Options CD-ROM only Floppy disk and CD-ROM
Network installation
Installation from an existing operating system
Unattended installation

25. Installation 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)

26. Command-line Switches for Winnt

27. Command-line Switches for Winnt (continued)

28. Command-line Switches for Winnt32

29. Command-line Switches for Winnt32 (continued)
Debug Log

30. Command-line Switches for Winnt32 (continued)

31. Command-line Switches for Winnt32 (continued)

32. CD-ROM Installation Set the computer’s 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

33. Floppy 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

34. Making 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

35. Network Installation
Copy the installation files from the Windows 2000 Server CD-ROM which are in the folder \I386
Share the host’s folder and set appropriate permissions
Map the host’s shared folder from the target server computer
Run Winnt.exe or Winnt32.exe from the shared folder
Follow the on-screen instructions

36. Installation 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
D:\ENGLISH\WIN2000\SERVER\I386>
Follow the on-screen instructions

37. Installation 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

38. Unattended Installation Over 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 /unattend:unattend.txt
Use a uniqueness database and the /UDF switch to further customize the unattended installation

39. Unattended 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

40. Creating 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

41. Installation Troubleshooting Tip
If Setup starts, but does not find mass storage, restart the installation, press F6 as soon as possible and load the manufacturer’s 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 manufacturer’s Hal.dll

42. Installation 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

43. Installation Part 1 (continued)
Figure 5-3 Beginning setup options

44. Installation Part 1 (continued)
Read the licensing agreement and press F8
Select the partitioned or unpartitioned disk space on which to install Windows 2000

45. Installation Part 1 (continued)
Figure 5-4
Detecting
partitions

46. Installation 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

47. Quick Quiz
You have a 1 GB partition that you want to format for FAT. What version of FAT will Windows 2000 use to format this partition?
Answer: FAT16
The ___________________ file contains information about the location of both operating systems in a dual-boot system.
Answer: Boot.ini
When the ARC path starts with multi(), this means that
Answer: the operating system is located on a non-SCSI or on a SCSI disk with the BIOS enabled
.  The password auto!2#rank is an example of a _____________________ password.
Answer: strong 
 Which Winnt32.exe command enables you to create a log from which to analyze installation problems?
Answer: /debug level:file

48. Installation 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

49. Installation 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

50. Installation Part 2 (continued)
Figure 5-5 Name and organization information

51. Installation Part 2 (continued)
Select the licensing mode
Enter the name of the server and the Administrator account’s password
Select the Windows 2000 components to install

52. Installation Part 2 (continued)
Figure 5-6 Windows 2000 components

53. Installation 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)

54. Installation Part 2 (continued)
Wait for Setup to install components and files and then click Finish

55. Installation Part 2 (continued)
Figure 5-7 Installing components

56. Log On and Test the Server
Press Ctrl+Alt+Del, 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

57. Configure Your Server Tool
Figure 5-8 Configuration dialog box

58. Testing the Desktop Icons
Test the desktop icons and other preliminary functions of the server

59. Figure 5-9 Windows 2000 Desktop

60. Upgrading 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

61. Upgrading 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

62. Upgrading a Windows NT 4.0 Server and Domain (continued)
Figure Selecting the upgrade option

63. Upgrading 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

64. Troubleshooting 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

65. Troubleshooting 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 computer’s diagnostics before starting
Run a comprehensive test of the hard disk before starting

66. Troubleshooting a Windows 2000 Server Setup

67. Troubleshooting a Windows 2000 Server Setup (continued)

68. Troubleshooting a Windows 2000 Server Setup (continued)

69. Service Packs
Check Microsoft’s 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

70. Windows Service Pack Update Switches

71. Uninstalling 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

72. Chapter Summary
Before you install Windows 2000 Server, make sure the computer’s 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

73. Chapter 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

74. KeyTerms
answer file – A text file that contains a complete set of instructions for installing Windows 2000 in the unattended mode.
basic input/output system (BIOS) – A program on a read-only or flash memory chip that establishes basic communications with components such as the monitor and disk drives. The advantage of a flash chip is that you can update the BIOS.
client access license (CAL) – A license to enable a workstation to connect to Windows 2000 Server as a client.
dual-boot system – A computer set up to boot from two or more different operating systems, such as Windows 2000 Server and MS-DOS.
emergency repair disk (ERD) – A disk that contains repair, diagnostic, and backup information for use in case there is a problem with Windows 2000.
format – An operation that divides a disk into small sections called tracks and sectors for storage of files.

75. KeyTerms
Hardware Abstraction Layer (HAL) – A set of program routines that enable an operating system to control a hardware component, such as the processor, from within the operating system kernel.
member server – A server that is a member of an existing Windows 2000 domain, but that does not function as a domain controller.
partition – A process in which a hard disk section or a complete hard disk is set up for use by an operating system. A disk can be formatted after it is partitioned.
per seat licensing – A server software license that requires that there be enough licenses for all network client workstations.
per server licensing – A server software license based on the maximum number of clients that log onto the server at one time.
slip streaming – Installing only a specific portion of a service pack instead of the entire update.
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.
uniqueness database file (UDF) – A text file that contains an answer set of unique instructions for installing Windows 2000 in the unattended mode and that is used with an answer file.