Preparing to Install Windows 2000 Server
Before you can begin to install Windows 2000 Server, you must prepare for the installation by gathering information and making decisions about how you want to install the software. This lesson gives you the foundation you need to install Windows 2000 Server. It describes the tasks that you should complete before moving on to the installation.
During installation, the Windows 2000 Setup program asks you to provide information about how to install and configure Windows 2000. You should gather all the necessary information. Good preparation helps you avoid problems during and after the installation.
Before you begin the Windows 2000 installation process, review the list of tasks outlined in the table below. Each task is discussed in greater detail in the sections that follow. Initially, you should complete only the first two tasks in this table—verifying that your computer meets the minimum hardware requirements and checking hardware compatibility. The remaining tasks are completed during the actual installation of Windows 2000 Server, which you will perform in the exercises later in this chapter. This table is meant only to prepare you for the installation so that you can install Windows 2000 Server without any unnecessary delays.
| Task | |
|---|---|
| Verify that your computer meets the minimum hardware requirements. For example, your hard disk should meet the minimum space requirements and preferably have a minimum of 2 gigabytes (GB) of free disk space. | |
| Check all hardware (network adapters, video drivers, sound cards, CD-ROM drives, PC cards, and so on) for compatibility by checking the Windows 2000 Hardware Compatibility List (HCL). | |
| Identify how you want to partition the hard disk drive on which you are going to install Windows 2000 Server. | |
| Choose a file system that meets your requirements and provides the services you need. Choose NTFS unless you need to run more than one operating system on your computer. | |
| Select a licensing mode. You can switch to per-seat from per-server mode after installation, but not to per-server from per-seat. | |
| Choose the type of network group (workgroup or domain) your computer will join. If you are joining a domain, you need additional information such as the domain name and the computer account name created for you. With an administrator account and password in the domain, you can create a computer account in the domain. | |
| Determine whether to perform a new installation or upgrade an existing version of Windows NT Server. Windows NT Workstation and Windows 9x cannot be upgraded to Windows 2000 Server. | |
| Select an installation method: Setup boot disks, CD-ROM, or over-the-network. | |
| Choose which components you need to install, such as Networking Services or Microsoft Indexing Service. | |
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 DNS 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
You should write down the following 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 Server, you should back up the files that you want to preserve. You can back up files to a disk, a tape drive, or another computer on the network.
Uncompressing the Drive
Uncompress any DriveSpace or DoubleSpace volumes before installing Windows 2000. You should not install Windows 2000 on a compressed drive unless the drive was compressed with the NTFS compression utility. DriveSpace or DoubleSpace volumes are created in Windows 9x. Windows 9x cannot be upgraded to Windows 2000 Server but can coexist on the same computer running Windows 2000 Server.
Disabling 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 completing the installation. If you are upgrading to Windows 2000, you can leave Windows NT mirroring enabled during Setup.
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 (in the root directory of the Windows 2000 Server installation CD-ROM) for information regarding applications that need to be disabled or removed before running Setup. 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 of Windows 2000 to fail. To verify that the boot sector is not infected with a virus, run the Makedisk.bat file in the \Valueadd\3rdparty\CA_antiv directory on the Windows 2000 Server installation CD-ROM. The Makedisk.bat utility creates a diskette that is used to check the boot sector. After creating this diskette, boot the computer with the diskette inserted. This will run a boot sector virus check. After the utility has run, remove the diskette and proceed to the next preinstallation step.
Gathering Materials
Gather the following materials to prepare for the Windows 2000 installation:
- Read any documentation pertaining to installing Windows 2000 for updated installation information. Review the pertinent .txt and .doc files located on the Windows 2000 Server installation CD-ROM.
- Make sure you have all device driver disks and configuration settings for third-party hardware, including any third-party device driver disks and documentation.
- Have the Windows 2000 Server installation CD-ROM or a network share with the Windows 2000 Server files available.
- Format three 3.5-inch 1.44 MB floppy disks (if creating optional Setup Startup disks).
Minimum Hardware Requirements
You should be familiar with the minimum hardware requirements necessary to install and operate Windows 2000 Server so that you can determine whether your system meets these requirements. The minimum installation requirements for Windows 2000 are listed in the following table.
| Component | Minimum requirement |
|---|---|
| Processor | 32-bit Pentium 133 MHz. |
| Free hard disk space | One or more hard disks where %systemroot% (C:\WINNT by default) is located on a partition with at least 671 MB of free space (2 GB is recommended). |
| Memory | 64 MB for networking with one to five client computers; 128 MB minimum is recommended for most network environments. |
| Display | VGA monitor capable of 640 x 480 (1024 x 768 recommended). |
| CD-ROM drive | 12x or faster recommended; not required for network installations. |
| Additional drives | High-density 3.5-inch disk drive, unless your CD-ROM is bootable and supports starting the Setup program from a CD-ROM. |
| Optional components | Mouse or other pointing device. For network installation: a network adapter and an MS-DOS-based network operating system that permits connection to a server containing the Windows 2000 Setup files. |
Hardware Compatibility
Windows 2000 Setup automatically checks your hardware and software and reports any potential conflicts. However, to ensure a successful installation, you should make sure that your computer hardware is compatible with Windows 2000 Server before starting the setup process. To do this, verify that your hardware is on the HCL. The HCL is included on your Windows 2000 Server installation CD-ROM in the Support folder in Hcl.txt. The HCL lists each hardware model that has passed the Hardware Compatibility Tests (HCTs). The list also indicates which devices Windows 2000 Server supports. Testing is conducted by Windows Hardware Quality Labs (WHQL) and by some hardware vendors. Installing Windows 2000 Server on a computer that does not have hardware listed in the HCL might not be successful.
Installing Windows 2000 Server
Once you have performed all the necessary steps to prepare for a Windows 2000 Server installation, you are ready to begin the Windows 2000 Setup process. This lesson focuses on performing a new installation of Windows 2000 Server. It begins with a discussion of the various installation programs and then describes the phases of the installation process.
Windows 2000 Server Setup Programs
Regardless of which method you use to install Windows 2000 Server, you must execute either Winnt.exe or Winnt32.exe. You can use the Setup.exe program to launch Winnt.exe or Winnt32.exe, or you can execute Winnt32.exe or Winnt.exe directly. For a clean installation on a computer running MS-DOS or Windows 3.x, run Winnt.exe from the MS-DOS command line. For a clean installation from Windows 95, Windows 98, or Windows NT Workstation, run Winnt32.exe. For a clean installation or upgrade from Windows NT Server 3.51 or 4.0, run Winnt32.exe. Several switches can be used with Winnt.exe and Winnt32.exe to customize how Windows 2000 Server is installed on your computer.
Windows 2000 Setup Program
The 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. From there, you can choose to install Windows 2000 Server, install add-on components, browse the CD, or exit the Setup program. If you select the Install Windows 2000 option, the Winnt.exe or the Winnt32.exe program runs, depending on which operating system you are currently running.
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. If Setup determines that the computer is running Windows NT Server 3.51, Windows NT Server 4.0, or an earlier version of Windows 2000 Server, you are prompted either to upgrade or install Windows 2000. If a newer version of Windows 2000 Server is installed on the computer, Setup.exe will not allow the installation of Windows 2000 Server to continue.
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:
- Creates 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 users to restart their systems. After the computer restarts, the boot menu appears and installation continues.
Winnt.exe installs Windows 2000 Server and can be executed from an MS-DOS or a Windows 16-bit operating system command prompt.
Winnt.exe Switches
You can use the following switches to modify the behavior of the Winnt.exe Setup program:
WINNT [/s[:sourcepath]] [/t[:tempdrive]] [/u[:answer_file]] |
These switches are described in detail in the following table:
| Switch | Description |
|---|---|
| /s[:sourcepath] | Specifies the source location of the Windows 2000 files. The location must be a full path of the form x:[path] or a valid UNC. |
| /t[:tempdrive] | Directs Setup to place temporary files on the specified drive and to install Windows 2000 on that drive. If you do not specify a location, Setup attempts to locate a drive for you. |
| /u[:answer file] | Performs an unattended Setup using an answer file (requires /s). The answer file provides answers to some or all of the prompts that the end user normally responds to during Setup. |
| /udf:id[,UDF_file] | Indicates an identifier (id) that Setup uses to specify how a Uniqueness Database File (UDF) modifies an answer file (see /u). The /udf parameter overrides values in the answer file, and the identifier determines which values in the UDF file are used. If no UDF_file is specified, Setup prompts you to insert a disk that contains the $Unique$.udb file. |
| /r[:folder] | Specifies an optional folder to be installed. The folder remains after Setup finishes. |
| /rx[:folder] | Specifies an optional folder to be copied. The folder is deleted after Setup finishes. |
| /e | Specifies a command to be executed at the end of GUI-mode Setup. |
| /a | Enables accessibility options. |
Winnt32.exe Setup Program
Winnt32.exe is used to install Windows 2000 Server from an existing Windows 95, Windows 98, or Windows NT computer. It can be executed by double-clicking Winnt32.exe in the root of the source folder (such as \i386) on the Windows 2000 Server installation CD-ROM or in a network share location for over-the-network installations. You can also execute Winnt32.exe by using the run command from the Start Menu, which allows switches to be specified. In addition, the Winnt32 command can be run from a Windows 95, Windows 98, or Windows NT (all Windows 32-bit operating systems) command prompt.
If the Windows 2000 Server installation is initiated over the network, Winnt32.exe creates a $WIN_NT$.~LS temporary directory and copies the Windows 2000 Server files from the server into this directory. The temporary directory is created on the first partition that is large enough, unless otherwise specified by the /t switch. This is known as the Pre-Copy Phase.
WINNT32.EXE Switches
You can use the following switches to modify the behavior of the Winnt32.exe Setup program:
winnt32 [/s:sourcepath] [/tempdrive:drive_letter] |
These switches are described in detail in the following table:
| Switch | Description |
|---|---|
| /s:sourcepath | Specifies the source location of the Windows 2000 files. To simultaneously copy files from multiple servers, specify multiple /s sources. If you use multiple /s switches, the first specified server must be available or Setup will fail. |
| /tempdrive:drive_letter | Directs Setup to place temporary files on the specified partition and to install Windows 2000 on that partition. |
| /Unattend or /u | Upgrades your previous version of Windows 2000 in unattended Setup mode. All user settings are taken from the previous installation, so no user intervention is required during Setup. Using the /unattend switch to automate Setup affirms that you have read and accepted the End-User License Agreement (EULA) for Windows 2000. Before using this switch to install Windows 2000 on behalf of an organization other than your own, you must confirm that the end user has received, read, and accepted the terms of the Windows 2000 EULA. OEMs may not specify this key on machines being sold to end users. |
| /unattend[num][:answer_file] | Performs a fresh installation in unattended Setup mode. The answer file provides Setup with your custom specifications. Num is the number of seconds between the time that Setup finishes copying the files and when it restarts your computer. You can use num on any computer running Windows NT or Windows 2000. The answer_file placeholder is the name of the answer file. |
| /copydir:folder_name | Creates an additional folder within the folder in which the Windows 2000 files are installed. For example, if the source folder contains a folder called Private_drivers that has modifications just for your site, you can type /copydir:Private_drivers to have Setup copy that folder to your installed Windows 2000 folder. So then the new folder location would be %systemroot%\Private_drivers. You can use /copydir to create as many additional folders as you want. |
| /copysource:folder_name | Creates a temporary additional folder within the folder in which the Windows 2000 files are installed. For example, if the source folder contains a folder called Private_drivers that has modifications just for your site, you can type /copysource:Private_drivers to have Setup copy that folder to your installed Windows 2000 folder and use its files during Setup. So then the temporary folder location would be %systemroot%\Private_drivers. Unlike the folders /copydir creates, /copysource folders are deleted after Setup completes. |
| /cmd:command_line | Instructs Setup to carry out a specific command before the final phase of Setup. This would occur after your computer has restarted twice and after Setup has collected the necessary configuration information, but before Setup is complete. |
| /debug[level][:filename] | Creates a debug log at the level specified, for example, /debug4:C:\ Win2000.log. The default log file is %systemroot%\Winnt32.log, with the debug level set to 2. The log levels are as follows: 0-severe errors, 1-errors, 2-warnings, 3-information, and 4-detailed information for debugging. Each level includes the levels below it. |
| /udf:id[,UDF_file] | Indicates an identifier (id) that Setup uses to specify how a Uniqueness Database File (UDF) modifies an answer file (see the /unattend entry). The UDF overrides values in the answer file, and the identifier determines which values in the UDF are used. For example, /udf:RAS_user, Our_company.udb overrides settings specified for the identifier RAS_user in the Our_company.udb file. If no UDF is specified, Setup prompts the user to insert a disk that contains the $Unique$.udb file. |
| /syspart:drive_letter | Specifies that you can copy Setup startup files to a hard disk, mark the disk as active, and then install the disk into another computer. When you start that computer, it automatically starts with the next phase of the Setup. You must always use the /tempdrive parameter with the /syspart parameter. The /syspart switch for Winnt32.exe runs only from a computer that already has Windows NT 3.51, Windows NT 4.0, or Windows 2000 installed on it. It cannot be run from Windows 9x. |
| /checkupgradeonly | Checks your computer for upgrade compatibility with Windows 2000. For Windows 95 or Windows 98 upgrades, Setup creates a report named Upgrade.txt in the Windows installation folder. For Windows NT 3.51 or 4.0 upgrades, it saves the report to the Winnt32.log in the installation folder. |
| /cmdcons | Adds a Recovery Console option to the operating system selection screen for repairing a failed installation. It is only used post-Setup. |
| /m:folder_name | Specifies that Setup copies replacement files from an alternate location. Instructs Setup to look in the alternate location first, and if files are present, use them instead of the files from the default location. |
| /makelocalsource | Instructs Setup to copy all installation source files to your local hard disk. Use /makelocalsource when installing from a CD to provide installation files when the CD is not available later in the installation. |
| /noreboot | Instructs Setup not to restart the computer after the file copy phase of winnt32 is completed so that you can execute another command. |
The Installation Process
The Windows 2000 Server installation process includes three phases: the Pre-Copy Phase, Text mode, and GUI mode.
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. When you use the Winnt.exe or Winnt32.exe command to initiate an installation over the network, all the files needed to complete the installation are copied over the network to a temporary directory named $WIN_NT$.~LS. Setup then continues, as it would if you were performing the installation from a local drive, moving on to the 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. The check box is under the Advanced Options button. When you select this option, a $WIN_NT$.~BT directory is created on the disk. This directory contains the files that would have been on the four boot floppies.
While the files are being copied into the $WIN_NT$.~LS directory, Windows 95, Windows 98, or Windows NT is still running. This means there is less down time during the upgrade.
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. All files required for installation are copied from the temporary directory (or the CD-ROM) into the installation directory on the hard disk of the target computer.
Windows 2000 Server Licensing Agreement
The Windows 2000 Server Licensing Agreement takes up several pages. Use the Page Down key to move through the agreement, and then press F8 to agree. This appears before Text mode if you use Winnt32 or Autorun to start your setup.
Existing Installations
If Setup detects any existing Windows 2000 installations, it displays them in a list. You can select an installation and press R to repair it, or press Esc to continue.
Partitions
Setup displays all existing partitions and free space on the system. Using the Up and Down arrow keys you can select where you want to install Windows 2000 Server. At this point you can create and delete partitions. Press Enter to continue.
File Systems
Setup gives you the option of keeping the current file system intact or allows you to convert it to NTFS. If you do not want to change it, select the Leave Current File System Intact option, which is the default, and press Enter to continue.
Setup examines your hard disks and copies the files it needs for installation from the temporary directory to the installation directory. (Winnt is the default directory.)
GUI Mode
After completing the Text mode portion of Setup, the computer restarts and GUI mode begins. This phase allows you to select which optional components to install and allows you to select the administrator password.
GUI mode consists of three distinct stages:
- Gathering Information About Your Computer
- Installing Windows 2000 Server Networking
- Completing Setup
Gathering Information About Your Computer
The Gathering Information About Your Computer stage is a series of dialog boxes that Windows 2000 uses to collect configuration information for setting up your system. During this stage, Windows 2000 security features are installed and devices are installed and configured.
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
When configuring your system, you must enter the name that Windows 2000 Server is registered to. In addition, you can add the name of the organization, although this is optional.
Licensing Mode
You must select the Per Server or Per Seat licensing method. If you select Per Server, you must enter the number of Per Server licenses.
Computer Name and Administrator Password
You must enter a computer name (NetBIOS name of up to 15 characters) when you install Windows 2000. Note that the autogenerated name is 15 characters long. The name you enter must be different from other computer, workgroup, or domain names on the network. A default computer name is displayed. You can access the default name or type in a computer name.
You can also enter an Administrator password for the local Administrator user account. This password can be up to 127 characters long, or it can be left blank.
Optional Component Manager
The Optional Component Manager allows you to add or remove additional components during and after installation. For details about each of these components, see "Lesson 1: Preparing to Install Windows 2000 Server."
Date and Time Settings
During the installation process, you must select the appropriate time zone and adjust the date and time settings, if necessary, including automatic adjustments for daylight savings time.
Installing Windows 2000 Server Networking
When Setup completes the Gathering Information About Your Computer stage, it returns to the Windows 2000 Setup screen. Setup then examines the computer to detect installed network adapters. This can take several minutes.
Networking Settings
The Windows 2000 networking setup begins with a dialog box offering a choice between Typical settings (default) or Custom settings. Typical settings configure the system with the 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 for Microsoft Networks. You can add SAP Agent and QoS Packet Scheduler. You can modify the settings for File and Printer Sharing for Microsoft Networks by highlighting the service and clicking Properties. This allows you to optimize server service settings and provide server service compatibility for LAN Manager 2.x clients.
- 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. You can also modify the settings for a protocol (if applicable) by highlighting the protocol and clicking Properties.
Completing Setup
The Completing Setup stage performs the following actions and requires no user interaction. The following table provides an overview of the tasks performed by Setup during this stage.
| Task | Description |
|---|---|
| Copying files | Setup copies any remaining files necessary to the installation directory such as accessories and bitmaps. |
| Configuring the computer | Setup creates your start menu, program groups, sets up the print spooler, printers, services, the administrator account, fonts, the Pagefile, and the registration of many dynamic-link libraries (DLLs). |
| Saving the configuration | Setup saves your configuration to the registry, creates the repair directory, and resets the Boot.ini. |
| Removing temporary files | Setup removes the temporary files and directories created and used during installation, such as the $WIN_NT$.~LS directory, and also compacts the system hives in the registry. |
No comments:
Post a Comment