CHAPTER 2
INSTALLING AND CONFIGURING MICROSOFT
WINDOWS 2000 SERVER
Lesson 1: Preparing to Install Windows 2000
Server
During the installation, the Windows 2000 Setup program asks you to provide information about
how to install and configure Windows 2000. Review the Task list before you begin. See the
Task List.
There are additional tasks you should perform so you can eliminate potential problems, and they are:
Working with Domain Name System (DNS)
When you create a Windows 2000 domain, the DNS service must be running and configured. If you
are joining a domain you must know the DNS name of the domain that your computer is joining. If
DMS is not running, it is installed automatically when you create a domain controller or when you
promote a
server to a domain controller.
Recording Information
Keep track and document this information: Previous operating system (if any), name of the computer
(if on a network), name of the workgroup or domain (if on a network), and the IP address (if there is
no Dynamic Host configuration Protocol (DHCP) server or an existing DHCP server will not be used
for dynamic IP addressing).
Backing Up Files
Before you install Windows 2000, you should backup files that you want to preserve.
Uncompressing the Drive
Uncompress any Drive Space you DoubleSpace volume before installing Windows 2000. You should
not install Windows 2000 on a compressed drive unless the drive was compressed with the NTFS
compression utility.
======================================================================
winser2.html PAGE
2
2002/01/12
Disable Disk Mirroring
If you are installing a clean copy of Windows 2000 and you have Windows NT disk mirroring
installed on your target computer, disable it before running Setup. You can re-enable disk-mirroring
after the installation is complete. But, if you are upgrading to Windows 2000, you can leave
Windows NT mirroring enabled during Setup.
NOTE: Disabling hardware level disk mirroring to complete a new installation of Windows 2000 is
not necessary since the operating system is unaware of redundant array of inexpensive (RAID)
implemented in hardware.
Disconnecting UPS Devices
If you have UPS equipment connected to your target computer, disconnect the connecting serial
cable before running Setup. Windows 2000 Setup attempts to automatically detect devices
connected to serial ports, and UPS equipment can cause problems with the detection process.
Reviewing Applications
Before starting the Windows 2000 Server Setup program, be sure to read Readme.doc. You
may need to remove virus-scanning software, third-party network services, or client software
before running the Windows 2000 Server installation.
Checking the Boot Sector for Viruses
A boot sector virus will cause the installation for Windows 2000 to fail. To verify there are no
viruses, run the Makedisk.bat file in the \Valueadd\3rdpart\CA_antiv directory on the Windows
2000 Server installation CD-ROM.
Gathering Materials:
Gather the following materials to prepare for the Windows
2000 installation:
the *.doc files on the Server Installation CD-ROM.
hardware, including any third-party device driver disks and documentation.
======================================================================
winser2.html PAGE
3
2002/01/12
2000 Server files available.Format four 3.5” 1.44 MB floppy disks (if creating optional Setup
Startup Disks).
Minimum Hardware Requirements:
======================================================================
Component Minimum Requirement
======================================================================
Processor 32-bit Pentium 133 MHz.
Free hard disk One or more hard disks where %systemroot%
Space 1GB, but 2 GB recommended
Memory 128MB RAM recommended (64MB RAM minimum)
Display VGZ monitor capable of 640X480
(1024 X 768 recommended).
CD-ROM drive 12x or faster, not required for network installations.
Additional Drives High-density 3.5”disk drive, unless your CD-ROM
Is bootable and supports starting the Setup program
From a CD-ROM.
Optional Mouse or other pointing device.
components
=======================================================================
Hardware Compatibility
Windows 2000 Setup automatically checks your hardware and software and reports any potential
conflicts. You can do this by checking the HCL in the support folder in Hcl.txt.
Microsoft supports only those devices on the HCL. If one of the computer’s devices is not on the
HCL, contact the device manager to request a Windows 2000 driver, if it exists.
======================================================================
winser2.html PAGE
4
2002/01/12
Disk Partitions
The Windows 2000 Server Setup program allows you to install Windows 2000 Server onto an
existing partition or to create a partition and then install Windows 2000 onto the new one. You
can do some of the following disk partitioning during setup:
You can do this during the Setup Program. If the disk has partitions, but there is
enough unpartitioned disk space, you can create and size the installation partition by
using that unpartitioned space.
Server onto that partition. If the hard disk has an existing partition, you can delete it
to create more unpartitioned disk space and then use that unpartitioned space to
create the Windows 2000 partition.
to confirm your choice.
another operating system will cause that operating system to be overwritten.
Once you have Windows 2000 installed, you can then partition the remaining space by using the
Disk Management tool.
Sizing the Installation Partition
Windows 2000 Server Setup program requires a boot partition of at least 1 GB of free space for
the Operating system. However, it is recommended that you have 2GB to allow for future files
and programs.
The system partition is used for the initial load of Windows 2000.Windows 2000 looks for certain
files such as Ntldr, Ntdetect.com and Boot.ini in the root directory, usually C: drive (Disk 0) when
the computer is started. The operating system cannot start unless the system partition is marked
active.
The boot partition is where Windows 2000 Server is installed. It contains the operating system
parent directory (Winnt, by default), the \System32 subdirectory, the Windows 2000 kernel, and
all other files required to run the operating system. If Windows 2000 Server is installed on the
active partition, it is both the boot and system partition.
======================================================================
winser2.html PAGE
5
2002/01/12
The disk partition where you store Windows 2000 files must be on a permanent hard disk and must
have enough unused disk space to hold all the files. You should format with NTFS file system.
NOTE: In Windows 2000, if you choose to format NTFS during installation, it will format the
partition directly to NTFS. In previous versions, the partition was formatted FAT and then converted
to NTFS. This new process allows you to create partitions larger than 4GB.
Winnt.exe and Winnt32.exe, the Setup executable files, report an error if they are unable to find a
drive with enough free disk space available (>1GB), or the drive specified with the /t: or /tempdrive:
switch has insufficient free disk space. If such an error occurs, you must free some disk space and
then run Winnt or Winnt32 again.
You can put the operating system on another drive than C, such as D, but you must format it with
NTFS and it must be marked as Active. If you want to dual-boot your computer to operating
systems that do not support NTFS, such as Windows 98, drive C must be FAT16 or FAT32.
If a system’s hard disk contains basic input/output system (BIOS) controlled partitions, other file
systems such as network file system (NFS), stripe sets, volume sets, or mirrors, those elements
appear on the Setup screen as partitions of an unknown type.
If you are setting up a dual-boot configuration of Windows 2000 with another operating system
such as MS-DOS, Windows 3.0, Windows 95, Windows 98, or Windows NT, install Windows
2000 onto its own partition. Sometimes Windows 2000 Setup program can overwrite files in the
Program Files or folders installed by other operating systems, if they are located on another partition.
File Systems
Windows 2000 supports NTFS, and FAT file system. There are two FAT file systems: FAT16
and FAT32.
NTFS
Windows 2000 supports NTFS, and it has the basic features of FAT, plus advanced storage features
such as security, compression, and better scalability to large volumes. Windows 2000 and Windows
NT are the only operating systems designed to access data on a local hard disk that is formatted with
NTFS.
======================================================================
winser2.html PAGE
6 2002/01/12
Windows 2000 includes a new version of NTFS: NTFS version 5.0. It offers many enhancements
such as per-user disk quotas, file encryption, and reparse points.
NTFS requires Windows 2000 or Windows NT. If the computer is booted under a different
operating system, that operating system is not able to access the NTFS partitions. You should
use NTFS when the system requires any of the following features:
File-level and directory-level local security. NTFS allows you to control access to files and
directories regardless of whether access is local or over the network.
Disk compression. NTFS compresses files to store more data on the partition.
Disk quotas. NTFS allows you to control disk usage on a per-user basis.
Encryption. NTFS allows you to encrypt file data on the physical hard disk.
Auditing. This is also available on NTFS.
NTFS is the only one that supports Active Directory. However, you may need to use
FAT16 or FAT32 for a dual booting situation.
FAT16 and FAT32
They allow you to access by and compatibility with more than one operating system. To boot
between Windows 2000 and another operating system, the Windows 2000 system partition must
be formatted either with the FAT16 or the FAT32 file system. If you select FAT and the partition
is smaller than 2048 MB, Setup formats the hard drive as FAT16. On partitions larger than 2GB,
Setup automatically formats the hard drive as FAT32.
NOTE: Windows 2000 supports FAT32 volumes of any size created by Windows 95 OSR2 or
Windows 98. However, Windows 2000 formats FAT32 volumes only up to 32 GB in size. This
limitation stems from memory constraints in recovery
utilities as Autochk.
FAT16 and FAT32 do not offer file-level security. So for most instances you should format the
disk with NTFS. The only need for FAT16 or FAT32 is for dual booting.
======================================================================
winser2.html PAGE
7
2002/01/12
File System Considerations
If the
system and boot partitions are different partitions, Windows 2000 Setup will
format only
the boot partition by default. You must take additional steps during setup to format the
system partition.
the existing file system intact, preserving all files on that partition.
and other file system enhancements.
erases all existing files on that partition.
want to gain access to the partition when running MS-DOS, Windows 3.x, Windows 95,
2GB. Setup formats the disk with FAT32.
take advantage of the feature in NTFS. Setup formats the boot partition with NTFS Version 5.0
******* SEE
THE CHART FROM THE BOOK *******
Licensing
Windows 2000 Server support two licensing modes: Per Server and Per Seat. In per Server the
Client Access Licenses (CALs) are assigned to a server. In Per Seat mode, each computer that
accesses the Windows 2000 Server computer requires a
separate
Per-Server Licensing
With Per Server licensing, CALs
are assigned to a particular server.
Each
connection per client computer to the server for basic network services.
Per Server licensing is preferred by small companies with only one computer running Windows
000 Server. Per Server licensing allows you to specify a maximum number of concurrent server
connections and reject any additional logon attempts.
======================================================================
winser2.html PAGE
8
2002/01/12
NOTE: If you are unsure 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. It is not necessary to notify
Microsoft to make this change. This is a one-way conversion, you cannot convert from Per Seat
to Per Server.
Per-Seat Licensing
The Per Seat licensing mode requires a separate
Windows 2000 Server for basic network services. After a client computer has a
used to access any computer running Windows 2000 Server on the enterprise network. Per Seat
licensing is often more economical for large networks in which client computers will be used to
connect to more than one server.
If you use Terminal Services, the licensing mode is usually Per Seat.
Client Access License (
A
that the client computer can connect to network services, shared folders, and print resources.
The following services do not require CALs:
NOTE: Microsoft Windows 2000 Licenses do not cover the Microsoft BackOffice Products,
you must purchase these separately.
======================================================================
winser2.html PAGE
9
2002/01/12
Workgroups and Domains
You must choose workgroup or domain during the Setup Installation.
Joining a Workgroup
You must give the workgroup a name. A domain and a workgroup can share the same name.
The workgroup computers are not members of the domain and are not included in domain
administration.
The workgroup computers appear with the domain computers in Windows 2000 Explorer.
Joining a Domain.
During the Setup the Wizard stops the the DNS name. You must create a computer account or
add it to the domain database. Only users who have the Join a Computer to The Domain
permission can create a computer account. Members
of the Administrators, Domain Administrators,
or Account
Operators group have this user right by default.
NOTE: When joining a domain, even if the computer account has been previously created,
domain credentials must be supplied.
At least one domain controller and one DNS server must be online when installing a computer
in the domain. If you setup as a standalone, you can join the domain later.
Upgrade or New Installation
Upgrading is the process of installing Windows 2000 Server in a directory that currently contains
certain versions of Windows NT. An upgrade automatically installs Windows 2000 Server into
he same directory as the currently installed operating system. The versions of Windows NT from
which you can upgrade are:
· Windows NT Server 3.51
· Windows NT Server 4.0 Server or Windows NT 4.0 Terminal Server.
Installing, in contrast with upgrading, it the process of placing the operating system in a new
directory, wiping the previous operating system at setup, or installing Windows 2000 Server
on a disk partition with no previous operating system.
======================================================================
winser2.html PAGE
10
2002/01/12
Installation Methods
There are three methods available to install Windows 2000 Server on the Intel Platform:
· Setup boot disk
· CD-ROM
· Over-the-network
Setup Boot Disks
Windows 2000 Server is distributed on a CD-ROM and includes four setup floppy disks.
You can create a set of Setup Boot disks by running Makeboot.exe or Makebt32.exe from the
\Bootdisk directory on the Windows 2000 Server installation CD-ROM.
Setup Disk One
The Setupldr.bin file starts the Setup. The computer is inspected and the machine identification
data is collected. You may need to load a third party driver. The text mode portion of Windows
2000 Setup is loaded. The ntkrnlmp.exe file loads the Windows 2000 Executive.
Setup Disk Two
This disk loads the HAL, configuration tools, fonts, local-specific data, drivers, and controllers.
Windows 2000 continues in Text mode.
Setup Disk Three
This disk loads the Compaq drive array and disk controller drivers. Windows 2000 Setup
continues in text mode.
Setup Disk Four
This disk loads the floppy disk drivers; SCSI CD-ROM, floppy, and fixed drive drivers, and file
system drivers (FAT, NTFS, and CDFS). At this point the CD-ROM drive is accessed. Setup
searches for previous versions of Windows and any existing partitions. The partition is then
formatted. When formatting is complete, file copy begins. Then the system reboots, you must
remove any floppy’s from drive A.
======================================================================
winser2.html PAGE
11
2002/01/12
Beyond Disk Four
After the system reboots, Windows 2000 Setup starts in GUI mode. CD-ROM files continue to
be copied to the hard disk. Choose the type of network installation, typical or custom.
Bootable CD-ROM
If your computer BIOS supports the bootable CD-ROM (no-emulation mode) format, insert the
Windows 2000 Server compact disk into the CD-ROM drive and then turn off the computer.
IMPORTANT Although your system might support bootable CD-ROMs, you might have to
modify your system BIOS to boot to the CD-ROM.
Over-the-Network (Server-Based)
The Windows 2000 Server system files must be available over the network. Copy the Windows
2000 installation CD-ROM, or at a minimum, the source directory (\I386) to a directory on the
hard disk of a network server and share the directory.
Upgrading Windows 95, Windows 98, or Windows NT
If your computer is currently running Windows 95, Windows 98, or Windows NT, connect to the
system files over the network and run (double-click) Winnt32.exe, located in the I386 directory.
Installing New or Upgrading Current Version
If you do not have Windows 95, Windows 98, or Windows NT installed, you need to run
MS-DOS and an MS-DOS network client to establish your connection to the shared network
folder containing the Setup files.
The MS-DOS computer needs 500 KB of free conventional memory to run the setup routine
successfully. Make sure you have loaded Emm386.exe and are loading all device drivers high.
TIP To free some memory, run LoadHigh
Winnt.exe to load portions of Winnt.exe
high.
======================================================================
winser2.html PAGE
12 2002/01/12
Choosing Which Components to Install
Windows 2000 includes a wide variety of core components, including a number of administrative
tools, which are automatically installed by Setup.
These components can be installed at Setup time or added afterward (through the Add/Remove
Windows components option within Control Panel’s Add/Remove Programs Application.
**** See chart page
57-60***** KNOW THIS, only the highlights!!!!!!!!!
Lesson Summary:
you need, ensure that the Hardware can support Windows 2000.
should install.
Lesson 2:
Installing Windows 2000 Server
Regardless of which method you use to install Windows 2000 Server, you must run either
Winnt.exe or Winnt32.exe, correct! You can user the Setup.exe program to launch Winnt.exe
or Winnt32.exe, or you can execute Winnt32.exe or Winnt.exe directly.
Windows 2000 Setup Program
Setup.exe is located in the root directory of the Windows 2000 Server installation CD-ROM.
When you execute Setup.exe, the Microsoft Windows 2000 CD screen appears.
If Autorun is enabled on your system, the Windows 2000 CD screen will appear when you insert
the Windows 2000 Server installation CD-ROM into your CD-ROM drive. Autorun calls
Setup.exe, which checks the operating system.
Winnt.exe Setup Program
Winnt.exe is commonly used for over-the-network installations that use an MS-DOS network
client. Winnt.exe performs the following steps:
Create a $WIN_NT$.~BT temporary directory on the system partition and copies Setup boot
files into this directory. Creates a $WIN_NT$.~LS temporary directory and copies the
Windows 2000 files from the server into this directory. Prompts user to restart their system.
After the computer restarts, the boot menu appear and installation continues.
======================================================================
winser2.html PAGE
13
2002/01/12
Winnt.exe Switches:
You can use a variety of switches to modify the Installation of Winnt.exe.
******* See the List (page 62)****
Winnt32.exe Setup Program:
Winnt32.exe is used to install Windows 2000 Server from an existing Windows 95, 98 or
Windows NT computer. The source folder is I386. Winnt32.exe creates a $WIN_NT$.~LS
temporary directory and copies the Windows 2000 Server files form the server into this directory.
**** See the list of
switches, page 64 and 65 ****
The Installation Process
The Windows 2000 Server installation process includes three phases: The Pre Copy Phase,
Text mode, and GUI mode.
1. Pre-copy Phase
During the Pre-copy Phase, all of the files needed for the installation are copied to temporary
directories on the local hard drive. The temporary directory $WIN_NT$.~LS is where the files
are copied to. Then you continue with the install and move into text mode phase of the
installation process and then to the GUI mode phase.
You can choose not to create the boot floppies by selecting the check box Copy All Setup
Files From the Setup CD To The Hard Drive.
======================================================================
winser2.html PAGE
14
2002/01/12
2. Text Mode
In Text mode setup, Setup prompts you for information needed to complete the installation.
After you accept the license agreement, you specify or create an installation partition and
choose a file system.
Windows 2000 Server Licensing Agreement
If it quite long, you can page down by pressing F8 to agree.
Existing Installations
If Setup detects any existing Windows 2000 installations, it displays them in a list. You can
select and installation, R for repair or press ESC to continue.
Partitions
Setup displays all existing partitions and free space on the system.
File Systems
Setup give you the option of keeping the current file system intact or allows you to convert it to NTFS.
Winnt is the default directory.
3. GUI Mode
After completing the Text mode portion of Setup, the computer restarts and GUI mode begins.
This portion allows you to choose optional selections for the Installation. GUI mode consists
of three distinct stages:
· Gathering Information About Your Computer
· Installing Windows 2000 Server Networking
· Completing Setup
Gathering Information About Your Computer
This stage is a series of dialog boxes that Windows 2000 uses to collect configuration
information for setting up your system.
======================================================================
winser2.html PAGE
15
2002/01/12
Regional Settings. Windows 2000 displays the current (default) regional settings. You can
add support for additional languages, change your location settings for the system, and configure
the user account default settings as well.
Personalize Your Software. You must enter the name of the organizations the system
is registered to.
Licensing Mode. You must select the Per Server or Per Seat licensing method.
Computer Name and Administrator Password. You must enter a computer name
(NetBIOS name of up to 15 characters). You can also enter an Administrator password for
the local Administrator user account.
Optional Component Manager. This allows you to add or remove additional components
during and after installation. Date and Time Settings. You must select the proper time zone.
Installing Windows 2000 Server Networking
When Setup completes the Gathering Information About Your Computer stage, it returns to the
Windows 2000 Setup screen.
Networking Settings. You have a choice of Typical settings (default) or Custom Settings.
Typical settings configure the system with all the defaults: Client for Microsoft Networks,
File and Print Sharing for Microsoft Networks, and Internet Protocol (TCP/IP) configured
as a DHCP client.
Custom settings allows the configuration of the following three items:
Clients. The default client is Client for Microsoft Networks. You can add Gateway (and Client)
Services for NetWare.
Services. The default service is File and Printer Sharing.
Protocols. The default protocol is Internet Protocol (TCP/IP). You can add additional protocols,
including NWLink, IPX/SPX, NetBEUI, DLC, AppleTalk, Network Monitor Driver, and others.
======================================================================
winser2.html PAGE
16
2002/01/12
Completing Setup
The completing Setup requires no user input, it is done automatically.
======================================================================
Task Description
======================================================================
Copying files Setup copies any remaining files necessary to the
Installation directory such as accessories and bitmaps.
Configuring the Setup creates your start menu, program groups, sets
Computer up the print spooler, printers, services, the administra-
tor accounts, fonts the Pagefile, and the registration
of many dynamic-link libraries (DLLs).
Saving the Setup saves your configuration to the registry,
Configuration creates the repair directory, and resets the Boot.ini.
Removing Setup removes the temporary files and directories
Temporary files created and used during installation, such as the
$WIN_NT$.~LS directory, and also compacts the
system hives in the registry.
=======================================================================
Lesson Summary:
is used on computers running MS-DOS or Windows 16-bit operating systems. Winnt32.exe
is used on computers running Windows 32-bit operating systems (Windows 9x, Windows
NT, or Windows 2000).
mode allows you to select which optional components to install and to select the administrator password.
======================================================================
winser2.html PAGE
17
2002/01/12
Lesson 3:
Upgrading to Windows 2000 Server
The process for upgrading existing servers from Windows NT Server to Windows 2000 Server is primarily
automated.
There is just one basic process for upgrading a member server. Once you begin the installation process, the
Setup wizard will guide you through the upgrade.
When you upgrade, you must consider whether to convert the file system on any FAT16 or FAT32 partitions
that you might have to the NTFS file system. It is possible to install Windows 2000 Server and also the
computer to sometimes run another operating system by setting up the computer as a dual-boot system.
Using dual booting, however, presents complexities because of file system issues.
Upgrading Servers
Windows 2000 Server supports upgrades from Windows NT 3.51 Server, Windows NT Server 4.0,
and earlier versions of Windows 2000 Server. If a computer is running versions of Windows NT older
than Windows NT 3.51, upgrade to Windows NT Server 4.0 before upgrading to Windows 2000
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.
Upgrade Methods
The easiest way to upgrade Windows NT Server is to insert the Windows 2000 Server installation
CD-ROM. You can also run Winnt32 from the CD-ROM.
You can also upgrade your system by running Winnt32.exe over the network.
Finding Windows NT Installation to Upgrade
Look in C:\Boot.ini file is examined on x86-based systems.
NOTE: Windows 2000 does not support RISC-based systems.
The Setup process attempts to access the partition indicated by the Advanced RISC Computing
(ARC) path in <active partition>:\Boot.ini for each installation it finds.
======================================================================
winser2.html PAGE
18
2002/01/12
The active partition is usually C:, so references to the drive containing Boot.ini will be C:. If setup
can access the partition, it then examines the root directory by searching for the following items:
·
Directories. The Setup process searches for System32,
System32\Drivers, and
·
System32\Config subfolders.
·
Files.
Under the System32 subfolders, the setup process searches for Ntoskrnl.exe
·
and Ntdll.dll.
After searching for directories and files, the setup process attempts to load portions of the registry to
determine whether an attempt has been made to upgrade this installation and has failed.
Once each installation in C:\Boot.ini has been found and each entry has met the above criteria, setup
presents a menu that lists the installations on the system that can be upgraded.
NOTE: If there are multiple C:\Boot.ini entries that point to the same Windows NT installation, the
installation is listed in the upgrade selection menu only once.
Upgrading a Windows NT Domain
A critical task in upgrading your network to Windows 2000 Server is upgrading the Windows NT Server
domain. Domains are an important feature of both Windows NT Server and Windows 2000 Server.
With Windows 2000, servers can have one of three roles in relation to domains: Domain controllers,
which contain matching copies of the user accounts and other Active Directory services data in a given
domain; member servers, which belong to a domain but do not contain a copy of Active Directory
services data; and stand-alone servers, which do not belong to a domain and instead belong to a
workgroup.
You should plan the roles that your servers will have within domains in Windows 2000 before running
Setup, however, if adjustments are necessary to these roles, they can still be made after Setup.
There are several important points to remember about upgrading and existing Windows NT domain to
Windows 2000 domain:
security. On FAT16 or FAT32 partitions, shared folders can be protected only with
permissions set on the directories, not on individual files, and there is no access protection
against local access to the partition.
======================================================================
winser2.html PAGE
19
2002/01/12
you must upgrade the PDC first.
The roles of the servers in a domain are named somewhat differently with Windows 2000 Server as
compared to Windows NT Server. With Windows NT Server, the possible roles were PDC (limited
to one per domain).
=======================================================================
Role in Windows NT
Domain Role in
Windows 2000 Domain
=======================================================================
Primary domain controller Domain controller
Backup domain controller Your choice of domain controller or member
Server
Member server Your choice of member server or stand-alone
Server
Stand-alone server Your choice of member server (if a Windows
2000 domain exists) or stand-alone server.
=======================================================================
Upgrading a Windows NT domain involves several stages:
· Planning for a Windows NT domain upgrade
· Preparing for a Windows NT domain upgrade
· Upgrading the PDC
· Upgrading the BDC
· Upgrading member servers
Planning for a Windows NT Domain Upgrade
The main features to consider as part of a Windows 2000 upgrade planning are the following:
DNS domain name organization. Develop DNS structure for the root domain of an enterprise
tree or multiple trees in a forest of disjointed DNS Domain names. Once the root DNS domain
is created, other subdomains can be added to build the tree. For example, Microsoft.com is a
root domain, and dev.Microsoft.com and mktg.Microsoft.com are subdomains.
Name space organization within large account domains. Determine how to use OUs to structure
the people and project resources.
======================================================================
winser2.html PAGE
20
2002/01/12
Domain consolidation. Rebalance administration and control of centrally managed and distributed
network services by merging resource domains into a smaller number of Windows 2000 domains.
New machine accounts added for long-term organization. Determine the location of computer
accounts in Windows 2000 OUs. Deployment of advanced technologies.
Deploy new advanced technologies such as PKI security for smart card logon and remote
access authentication or IP security for secure data transfer over private intranet and public
Internet communications.
Preparing for a Windows NT Domain Upgrade
You should always have a good backup before you make changes to your hard disk. After
upgrading your PDC to Windows 2000 Server, this disconnected system is available for promotion
to a Windows NT PDC if needed.
In addition, for any computer that will be a domain controller in the Windows 2000 domain, you
should make sure there is plenty of room for the disk, beyond the space needed for the operating
system itself.
Preparing to Upgrade the Domain Controller
Before upgrading the domain controller you must perform several tasks:
Disable WINS by using the Services option in the Control Panel in Windows NT Server 4.0 so
that the WINS database can be converted during the upgrade process. Disable the DHCP by using
the Services option in Control Panel for the same reason. Set up a test environment by creating test
user accounts so that you can test the upgrade once it is complete.
======================================================================
winser2.html PAGE
21
2002/01/12
The following table describes items you might want to include in a test environment and how to
implement them:
======================================================================
Item Implementation
======================================================================
User and Group Include both user and group policies that are easy to verify
Policies after the upgrade. An example is removing the RUN
Command from the Start menu.
User Profiles Set up individual user profiles for the test users that are
obvious and easy to verify, such as different background
wallpaper.
Logon Scripts Use logon script commands that are easy to verify after
The upgrade, such as mapping network drives with the
Net use command.
======================================================================
Upgrading the Primary Domain Controller
The first domain controller to be upgraded in a Windows NT domain must be the PDC. As you
upgrade this server, you will be given the choices of creating a new domain or a child domain, and
creating a new forest or a domain tree in an existing forest. For upgrading a domain of three to five
servers, create a new domain and a new forest.
During the upgrade, you have the opportunity to choose the location of three important files: the
database containing user accounts and other Active Directory data, the log file, and the system
volume file (SYSVOL).
After the first server is upgraded to a Windows 2000 domain controller, it will be fully backward
compatible. This means that in a multiple-server environment the domain controller appears as a
Windows 2000 domain controller to Windows 2000 servers and client but emulated a Windows
NT 4.0 PDC to other servers and clients.
Upgrading the Backup Domain Controllers
After upgrading your PDC and ensuring that it is functioning to your satisfaction, upgrade any BDCs
next. Be sure the first server upgraded (the former PDC) is running and available on the network as
you upgrade other domain controllers. This server is used a template for the other domain controllers
to copy as they are upgraded.
======================================================================
winser2.html PAGE
22
2002/01/12
Upgrade the BDCs one at a time, and ensure that each is backed up before upgrading. Start and test
each server on the network to ensure that it is functioning to your satisfaction before upgrading another
BDC.
When you have completely upgraded all servers to Windows 2000 domain controllers, you have the
option of changing the domain from Mixed mode to Native mode. This is an important decision,
because you cannot revert to Mixed Mode after changing to native mode.
**** See diagram on
page 88 ****
Mixed Mode
Mixed mode refers to a domain that contains both Windows 2000 and Windows NT 3.51/4.0
domain controllers. In Mixed mode the PDC is upgraded to Windows 2000 Server and one or
more BDCs remain at version Windows NT Server 3.51/4.0.
The PDC appears as a Windows 2000 domain controller to other Windows 2000 computers,
and as a Windows NT 3.51/4.0 domain controller to computers that are not yet upgraded.
Some of the limitations on Windows 2000 operating in Mixed
Mode include the following:
imitations of pre-Windows 2000 trust relationships for access to resources.
Mixed mode is the default mode and is generally an interim step in the implementation of Windows 2000.
Native Mode
Once all domain controllers in a domain are upgraded, the domain can be moved from Mixed mode
to Native mode. In Native mode all clients make use of Windows 2000 Transitive trust. This means
that a user can connect to any resource in the enterprise. Native mode also allows group nesting.
NOTE: Moving to Native mode is a one-way move; once in Native mode, it is not possible to move
the domain back to Mixed Mode.
======================================================================
winser2.html PAGE
23
2002/01/12
Upgrading Member Servers
Upgrade the member servers. Member servers in the domain can be upgraded in any order.
Domain Consolidation
Domain consolidation is a planning process for organizing domain resources to take advantage of
new advanced features of the Windows 2000 Active Directory services. Domain reconfiguration is
optional; it is not a requirement for deploying Windows 2000. It is time-consuming, and quite intense.
Move user accounts from one domain to another to form a single layer There are two general ways
to consolidate domains:
domain.
Move server computers from one resource domain into the OU of another domain.
One advantage to domain consolidation is that the number of master account domains can be
reduced because each domain can be scaled to handle a much larger number of users, groups,
and computer accounts.
User passwords are not preserved when a user account is moved from one domain to another,
although the SID for the user is.
Another advantage to domain consolidation is that the number of resource domains can be reduced
by moving servers from many small domains into a combined resource domain. The domain
controllers of the resource domains become member servers in the larger combined domain.
Domain consolidation also makes it easier to redeploy server computers from one project or
department to another.
Windows 2000 includes the following features that enable
domain reconfiguration:
The SID history is kept with the user account, and access tokens will contain both the
new and the old SID to preserve access rights.
======================================================================
winser2.html PAGE
24
2002/01/12
Lesson Summary:
Upgrading from Windows NT Server to Windows 2000 Server if, for the most part, an
automated process.
· The Setup Wizard will guide you through the installation.
· You must plan your domains and the system layout.
· If you need to upgrade you must promote to a PDC.
· When you have completed these tasks you should consider consolidating domains you can
take advantage of Windows 2000 Active Directory services.
Lesson 4:
Troubleshooting a Windows 2000 Server Installation
You may encounter problems caused by for example, bad media or incompatible hardware.
=====================================================================
Problem Solution
=====================================================================
Media errors If you install from a CD-ROM, contact Microsoft.
Unsupported Replace the CD-ROM drive with one that is
CD-ROM drive supported, or try another method of installation.
Insufficient Use the Setup program to create a partition by
Disk space using existing free space on the hard disk.
Delete and create partitions as needed to create a
Partition that is large enough for installation.
======================================================================
winser2.html PAGE 25
2002/01/12
Reformat an existing partition to create more space.
Failure of dependency Use the Windows 2000 Setup Wizard, and return
Service to start to the Network Settings dialog box and verify that
You installed the correct protocol and network
Adapter.
Inability to connect Verify that the domain name is correct.
To the Domain
Controller Verify that the server running the DNS service and
The domain controllers are both running and online.
Verify that the network adapter card and protocol
Settings are set correctly.
Failure of Windows Verify that Windows 2000 is detecting all of the
2000 Server to install hardware and that all of the hardware is on the HCL.
or start
======================================================================
Lesson Summary: