Chapter 2, Installing and Configuring Microsoft Windows 2000 Server

Chapter 2, Lesson 1

Preparing to Install Windows 2000 Server

|1| 1. Preparing for Installation

A. Reviewing the list of tasks

Note Refer to the table on pages 39–40 for details about the following tasks. These tasks are discussed in more detail in the following sections.

1. Minimum hardware requirements

2. Hardware compatibility

3. Disk partitions

4. File systems

5. Licensing

6. Workgroups and domains

7. Upgrade or new installation

8. Installation methods

9. Choosing which components to install

B. Working with DNS

C. Recording information

D. Backing up files

E. Uncompressing the drive

F. Disabling disk mirroring

G. Disconnecting UPS devices

H. Reviewing applications

I. Checking the boot sector for viruses

J. Gathering materials

|2| 2. Minimum Hardware Requirements

Note Refer to the table on pages 42–43 when reviewing the following minimum hardware requirements necessary to install Windows 2000 Server.

A. Processor

B. Free hard disk space

C. Memory

D. Display

E. CD-ROM drive

F. Additional drives

G. Optional components

|3| 3. Hardware Compatibility

A. Hardware and software automatically checked for compatibility

B. Compatible hardware and devices on Hardware Compatibility List (HCL)

C. Support only for devices on HCL

Note Microsoft releases an updated HCL on a regular basis at the Microsoft Web site.

|4| 4. Disk Partitions

A. Windows 2000 can be installed on a new partition or on an existing partition.

B. Windows 2000 Server is installed on the boot partition, which must be at least 671 MB.

C. The operating system starts from the system partition.

D. To install Windows 2000, mirroring must be disabled on the partitions and the disks must be uncompressed.

|5| 5. File Systems

|6| A. NTFS

1. Contains the basic capabilities of FAT plus advanced features

2. Requires Microsoft Windows NT or Windows 2000

3. Used when a Windows 2000 partition requires specific features

a. File-level and directory-level security

b. Disk compression

c. Disk quotas

d. Encryption

|7| B. FAT16 and FAT32 file systems

1. Allow access by and are compatible with more than one operating system

Note Windows 2000 supports FAT32 volumes of any size created by Microsoft Windows 95 OSR2 or Microsoft Windows 98. However, Windows 2000 formats FAT32 volumes up to only 32 GB. This limitation stems from memory constraints in recovery utilities such as Autochk.

2. Do not offer many of the features supported by NTFS

3. Often used to support a dual-boot environment

|8| C. File system considerations

1. You can use an existing partition that is already formatted.

2. You can convert an existing partition to NTFS to make use of Windows 2000 security and other file system enhancements.

3. You can reformat an existing partition either to NTFS or to the FAT file system.

4. You should choose the FAT option if your boot partition is smaller than 2 GB and you want to gain access to that partition when running MS‑DOS.

5. You should choose the FAT option if you are dual-booting with Windows 95 OSR2.

Note Use the table on page 49 to compare the different features of the three file systems.

|9| 6. Licensing

A. Per Server licensing

1. Client access licenses (CALs) assigned to a particular server

2. Allows one connection per client computer to the server for basic network services

3. Preferred by small companies with only one computer running Windows 2000 Server

4. Allows you to specify a maximum number of concurrent server connections and reject any additional logon attempts

B. Per Seat licensing

1. Requires separate CAL for each client computer

2. More often economical for large networks

3. Usually used with Terminal Services except with the Terminal Services Internet Connector license

Note If you are unsure of which licensing mode to use, choose Per Server because you can change, only once, from Per Server to Per Seat licensing at no additional cost. This is a one-way conversion; you cannot convert from Per Seat to Per Server.

C. Client access license (CAL)

1. Provides the right to client computers to connect to a Windows 2000 Server computer

2. Not required for anonymous or authenticated access to Windows 2000 Server with IIS or a Web-server application that provides HTTP sharing of HTML files

3. Not required for Telnet and FTP connections

Note A Windows 2000 license does not cover Microsoft BackOffice products.

7. Workgroups and Domains

A. Joining a workgroup

1. A workgroup name must be assigned to the computer.

2. When a name is assigned, the computer appears as a member of that workgroup when other computer users in the network browse for network resources.

3. Although a domain and a workgroup can share the same name, workgroup computers are not members of the domain but appear with the domain computers in Windows Explorer.

B. Joining a domain

1. A computer account must exist for that computer when joined to a domain.

2. The user must have a user account that has authority to add computer accounts to the domain.

3. At least one domain controller and one DNS server must be online when installing a computer in a domain.

|10| 8. Upgrade or New Installation

A. Upgrading is the process of installing Windows 2000 Server in a directory that currently contains Windows NT Server 3.51, Windows NT Server 4.0, or Windows NT 4.0 Terminal Server.

B. Installing is the process of placing the operating system in a new directory, wiping out the previous operating system at setup, or installing Windows 2000 Server on a disk or partition with no previous operating system.

|11| 9. Installation Methods

|12| A. Setup boot disk

1. Required if installing Windows 2000 Server on a computer that is not running MS‑DOS or a Windows operating system and does not support the bootable CD‑ROM format

2. Allows you to start Windows 2000 to initiate an emergency repair

3. Can be created by using Makeboot.exe or Makebt32.exe

Note If you are installing Windows 2000 Server on a computer with no previous operating system and you are using an MS‑DOS boot floppy disk, you have to format the drive first. However, if you use the Windows 2000 Setup disks to start Setup, you can format the drive during Setup.

|13| B. CD-ROM

1. Computer’s BIOS must support the Bootable CD‑ROM (no-emulation mode) format.

2. BIOS might need to be modified.

|14| C. Over-the-network

1. Upgrading or installing on a Windows 95, Windows 98, or Windows NT computer

2. Installing on a computer that is not running Windows 95, Windows 98, or Windows NT

|15| 10. Choosing Which Components to Install

Note Refer to the tables on pages 57–60 when discussing which components to install during the Windows 2000 Server setup process.

Chapter 2, Lesson 2

Installing Windows 2000 Server

|16| 1. Windows 2000 Setup Programs

|17| A. Setup.exe

1. Allows you to launch Winnt.exe or Winnt32.exe

2. Located in the root directory of the Windows 2000 Server installation CD‑ROM

3. Allows you to install Windows 2000 Server, install add-on components, browse the CD‑ROM, or exit the Setup program

4. Prompts you to install or upgrade to Windows 2000 if Windows NT Server 3.51, Windows NT Server 4.0, or an earlier version of Windows 2000 Server is running on computer

|18| B. Winnt.exe

1. Used for a clean installation on a computer running MS‑DOS or Windows 3.x

2. Commonly used for over-the-network installations that use an MS‑DOS client

3. Can be executed from an MS‑DOS or a Windows 16-bit operating system command prompt

4. Includes a number of switches that allow you to modify the behavior of the program

Note Refer to the table on pages 62–63 for a description of each of the switches available to the Winnt.exe Setup program.

|19| C. Winnt32.exe

1. Used for a clean installation on a computer running Windows 95, Windows 98, or Windows NT Workstation

2. Used for a clean installation or upgrade on a computer running Windows NT Server 3.51, Windows NT Server 4.0, or an earlier version of Windows 2000 Server

3. Can be executed from the Windows 2000 Server installation CD‑ROM or from a network share

4. Includes a number of switches that allow you to modify the behavior of the program

Note Refer to the table on pages 64–66 for a description of each of the switches available to the Winnt32.exe Setup program.

|20| 2. The Installation Process

|21| A. Pre-Copy phase

1. Installation files copied to temporary folders on local hard drive

2. Allows you to choose not to create the boot floppy disks

3. Windows 95, Windows 98, and Windows NT running during this phase

|22| B. Text Mode phase

1. Prompted for information needed to complete the installation

2. Prompted to accept the Windows 2000 Server licensing agreement

3. Existing Windows 2000 installations detected

4. Existing partitions and free space detected, and partitions can be created

5. File system is selected

a. Can keep current file system intact

b. Can convert to NTFS

|23| C. GUI Mode phase

1. Gathering information about your computer

a. Regional settings

b. Personalizing software

c. Computer name

d. Administrator password

e. Optional components

f. Date and time

2. Installing Windows 2000 Server networking

a. Clients

b. Services

c. Protocols

3. Completing Setup

Note Refer to the table on page 70 for details about each of the following tasks.

a. Copying files

b. Configuring the computer

c. Saving the configuration

d. Removing temporary files

Chapter 2, Lesson 3

Upgrading to Windows 2000 Server

1. Upgrading to Windows 2000 Server

|24| A. Introduction to a Windows 2000 Server upgrade

1. One basic process for upgrading a member server

2. Guided through installation by the Setup wizard

3. Reasons to upgrade

a. Configuration is simpler.

b. Existing users, settings, groups, rights, and permissions are retained.

c. Files and applications do not need to be recopied to the disk after installation.

4. Using same applications after upgrade

a. Review the Windows 2000 Compatibility Guide at the Microsoft Web site.

b. Install the Windows 2000 Support Tools, which include the Windows 2000 Server Resource Kit Deployment Guide.

|25| B. Upgrading servers

1. Can upgrade from Windows NT Server 3.51, Windows NT Server 4.0, and earlier versions of Windows 2000 Server

2. Should upgrade to Windows NT Server 4.0 first if computer is running a pre-3.51 version of Windows NT Server

Note Windows 2000 supports all service packs for Windows NT 3.51 and Windows NT 4.0. The upgrade of installed applications varies with the system.

3. Upgrade methods

a. Inserting Windows 2000 Server installation CD‑ROM

b. Running Winnt32 from the Windows 2000 Server installation CD‑ROM

c. Running Winnt32 over the network

Note Setup cannot upgrade the operating system from the boot floppies or from booting off the CD‑ROM. Winnt32 or Autorun must be used to upgrade Windows NT Server.

4. Finding Windows NT installation to upgrade

a. Examining the Boot.ini file

b. Examining the registry

2. Upgrading a Windows NT Domain

|26| A. Introduction to a domain upgrade

1. Three server roles in relation to domains

a. Domain controllers, which contain matching copies of the user accounts and other Active Directory data in a given domain

b. Member servers, which belong to the domain but do not contain a copy of Active Directory data

c. Stand-alone servers, which belong to a workgroup instead of a domain

2. At least one domain controller in a domain

3. Several considerations in upgrading a domain

a. You must use NTFS on domain controllers

b. Any servers that have any partition formatted with FAT will lack local security.

c. When upgrading the domain controllers in a Windows NT domain to a Windows 2000 domain, you must upgrade the PDC first.

4. Roles of servers in Windows NT domains and Windows 2000 domains

Note See the table on page 84 for details about the roles of servers in Windows NT domains and Windows 2000 domains.

B. Stages in upgrading a domain

|27| 1. Planning for a Windows NT domain upgrade

a. Develop DNS structure for the root domain of the enterprise tree or multiple trees in a forest of disjointed DNS domain names.

b. Determine how to use OUs to structure the people and project resources.

c. Rebalance administration and control of centrally managed and distributed network services by merging resource domains into fewer Windows 2000 domains.

d. Determine the location of computer accounts in Windows 2000 OUs.

e. Deploy new advanced technologies such as PKI security for smart card logon and remote access authentication or IP security for secure data transfer via private intranet and public Internet communications.

Note For more information about domain upgrades, see the Windows 2000 Support Tools Deployment and Planning Guide. The installation program for this guide and other support tools is located in the Support\Tools folder on the Windows 2000 Server installation CD‑ROM.

|28| 2. Preparing for a Windows NT domain upgrade

a. Back up the hard disks before upgrading any of the servers.

b. Disconnect the network cable of a BDC in the Windows NT domain.

c. Ensure that there is plenty of disk space on any computer that will be made a domain controller in the Windows 2000 domain.

|29| 3. Preparing to upgrade the domain controller

a. Disable WINS and DHCP.

b. Set up a test environment.

Note Refer to the table on page 86 for details about items you might want to include in a test environment. It is always a good idea to test any upgrade in a lab environment before implementing it in a production environment.

|30| 4. Upgrading the primary domain controller

a. Upgrade the PDC first.

b. You can choose whether to create a new domain or a child domain and whether to create a new forest or a domain tree in an existing forest.

c. You can choose the location of three important files.

(1) Database containing Active Directory data

(2) System volume

(3) Log

d. After the server is upgraded, it is fully backward compatible.

|31| 5. Upgrading the backup domain controllers

a. After the PDC is upgraded and functioning properly, upgrade the BDCs one at a time.

b. After you have upgraded all servers to Windows 2000 domain controllers, you can change the domain mode from mixed mode to native mode.

(1) Mixed mode refers to a domain that contains both Windows 2000 and Windows NT domain controllers. The PDC appears as a Windows 2000 domain controller to other Windows 2000 computers and as a Windows NT domain controller to computers that are not yet upgraded. In mixed mode, the domain is limited by the functionality of the Windows NT domain controllers.

(2) In native mode, all clients make use of Windows 2000 transitive trust, which means that a user can connect to any resource in the enterprise. Native mode also allows group nesting.

Note A move to native mode is a one-way move. Once a domain is in native mode, you cannot move it back to mixed mode.

|32| 6. Upgrading member servers

a. Upgrade the member servers.

b. Member servers in the domain can be upgraded in any order.

|33| 3. Domain Consolidation

A. Two methods for consolidating domains

1. Move user accounts from one domain to another to form a single larger domain.

2. Move server computers from one resource domain into the OU of another domain.

B. Advantages of domain consolidation

1. The number of master account domains can be reduced because each domain can be scaled to handle a much larger number of user, group, and computer accounts.

2. The number of resource domains can be reduced by moving servers from many small domains into a combined resource domain.

C. Features that enable domain reconfiguration

1. Users and groups can be moved across domain boundaries and still preserve security identity.

2. Domain controllers can be demoted to member servers and moved to another domain.

3. Security policies can be defined centrally and applied to many systems.

4. Computers can be moved to different domains by using remote administration tools.

5. Access rights can be updated to reflect changes in organization or philosophy.

Chapter 2, Lesson 4

|34| Troubleshooting a Windows 2000 Server Installation

Note Refer to the table on pages 92–93 for more details about troubleshooting a Windows 2000 Server installation.

1. Media Errors

A. Use a different CD‑ROM drive.

B. Request replacement CD‑ROM.

2. Unsupported CD‑ROM Drive

A. Replace the CD‑ROM drive.

B. Try another method of installation.

3. Insufficient Disk Space

A. Use Setup to create a partition that uses existing free space on hard disk.

B. Delete and create partitions as needed.

C. Reformat an existing partition to create more space.

4. Failure of Dependency Service to Start

A. Verify that you installed the correct protocol and network adapter.

B. Verify that the network adapter has the proper configuration settings.

5. Inability to Connect to the Domain Controller

A. Verify that the domain name is correct.

B. Verify that the server running the DNS service and the domain controller are both running and online.