Server Administration-05

Chapter 5: Server Installation : 

Chapter 5: Server Installation A.Sai Bala Subrahmanyam, MCA,MCPIT,MCSA,MCPS

Learning Objectives: 

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

Learning Objectives (continued): 

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

Learning Objectives (continued): 

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

Installation Preparations: 

Installation Preparations Planning Steps: Gather information about what hardware components are installed Does it meet the minimum requirements Is it on the Hardware Compatibility List (HCL) Is the hardware sufficient for the software to be installed Download the latest drivers for NIC, SCSI adapter, Video card, etc.

Installation Preparations: 

Installation Preparations Plan disk and file system usage How to partition the disk or disks Hardware or Software RAID Which file system will be used Administrator account password Name of the server Which protocols to install What licensing method to use

Decide Whether to Set Up a Dual Boot System: 

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 None of these operating systems can read the NTFS file system without 3 rd party drivers. Dual-boot is not recommended in a production environment

Partitioning the Disk: 

Partitioning the Disk Partitioning – process in which a hard disk or section of a hard disk is setup for use by an operating system (Windows 2000) or file system (NTFS, FAT32, etc.) A partition is usually associated with a drive letter such as C: or D:. Formatting – operation that physically divides a disk into small sections called tracks and sectors During the installation of Windows 2000, only create the partition required for the operating system files. You can create other partitions later after Windows is installed.

File Systems: 

File Systems Choose between FAT and NTFS during the Windows 2000 installation. NTFS offers the best security, performance, and file handling FAT will automatically format 2GB or smaller partitions as FAT16 and larger than 2 GB partitions as FAT32. New FAT32 partitions are limited to 32GB in Windows 2000. Windows 2000 will read FAT32 partitions larger than 32GB if they were created with another operating system.

Server Naming: 

Server Naming Use a name that makes sense to users and administrators Make the name descriptive of the server’s function or of the organization Allow for growth in your naming scheme For DNS purposes, avoid using special characters other than the hyphen Make sure the name is not already used on the network

Administrator Password: 

Administrator Password Use a “strong” or difficult-to-guess password for the critical Administrator account Characteristics of a strong password: 8 or more characters Has a combination of letters (upper and lower case), numbers, and symbols Includes at least one symbol in characters two through six

Protocol Selection: 

Protocol Selection Use the default TCP/IP setup as a starting point during installation Add other protocols later as needed

Licensing Methods: 

Licensing Methods Per server licensing: A server license scheme based on the maximum number of clients that log on to the server at one time (used when there are multiple “shifts” of workers using the same PC). Per seat licensing: A server license scheme that requires enough licenses for all network clients that will ever access the server.

Initial Server Installation: 

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 by using DCPROMO.EXE)

Installation Methods: 

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

Installation Programs: 

Installation Programs Use Winnt.exe when installing from installation floppy 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 (an upgrade installation)

Command-line Switches for Winnt.exe (16-bit version): 

Command-line Switches for Winnt.exe (16-bit version) Switch Purpose /? Lists the switches /r:foldername Creates an optional folder of files copied from the Windows 2000 Server CD (the folder remains after installation is complete) /rx:foldername Creates an optional folder of files copied from the Windows 2000 Server CD (the folder is deleted after installation is complete).

Command-line Switches for Winnt.exe (16-bit version): 

Command-line Switches for Winnt.exe (16-bit version) Switch Purpose /s:drive:\folder Uses a source path for the installation files other than the current path /u:script file Used in an unattended installation to specify the name of the answer file. Should be used with the /s switch. udf:id Uniqueness database file to be used with an unattended install.

Command-line Switches for Winnt32: 

Command-line Switches for Winnt32 Switch Purpose /? Lists the switches for Winnt32 /checkupgradeonly Creates only a report to tell you if the computer is compatible with Windows 2000 (the report is called Upgrade.txt for computers running Windows 95/98 and Winnt32.log for computers running Windows NT 3.51 or 4.0) /comdcons Adds a Recovery Console option to the BOOT.INI file so that you can fix problems with an installation /copydir: folder Creates a special subfolder in the final Winnt directory, usually implemented for information specific to that installation, such as to store specialized drivers for use only during the installation (the folder is deleted after the installation is completed)

Command-line Switches for Winnt32 (continued): 

Command-line Switches for Winnt32 (continued) Switch Purpose /s: drive:\folder /s:\\ server\share Uses a path for the installation files other than the current path – also enables you to copy files from two or more sources by specifying multiple /s commands /unattend Enables you to upgrade a version of Windows 2000 to a later version, using the parameters already in place for your current version /unattend [seconds]: script file Used in an unattended installation to specify the name of the answer file containing installation commands (the seconds parameter is used to create an interval between when the setup files are copied and the computer reboots so you can interrupt to enter a command) udf:id Enables a uniqueness database file to be used with an unattended installation so that particular information in the script can be changed, such as the name of the server (id specifies the name of the database file, such as udf:install.dbf )

CD-ROM Installation: 

CD-ROM Installation Insert the Windows 2000 Server CD-ROM Set the computer’s BIOS to boot first from CD-ROM While booting, you will be prompted to “press any key” to boot from CD-ROM After Winnt.exe starts, follow the instructions on the screen

Floppy Disk and CD-ROM Installation: 

Floppy Disk and CD-ROM Installation Set the BIOS to boot first from drive A: 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

Making Copies of the Setup Floppy Disks: 

Making Copies of the Setup Floppy Disks 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. ex: E:\bootdisk\makebt32.exe Click OK Follow the on-screen instructions

Network Installation: 

Network Installation Copy the installation files from the “i386” folder on the Windows 2000 Server CD-ROM to a network server Share the i386 folder and set appropriate permissions (read and execute is enough) Map a drive from the target computer to the server’s shared folder. Run Winnt.exe or Winnt32.exe from the shared folder using any necessary switches Follow the on-screen instructions

Upgrading a Previous Operating System: 

Upgrading a Previous Operating System Boot the computer to use its existing operating system Insert the Windows 2000 Server CD-ROM Click Start, click Run, enter the drive letter of the CD-ROM and the path to the Winnt.exe or Winnt32.exe file, such as \I386\winnt32 plus any switches Follow the on-screen instructions

Installation Tip: 

Installation Tip If you install Windows 2000 from MS-DOS, you can significantly reduce the installation time if you start the SMARTDRIVE utility before running Winnt.exe To load smartdrive, type “smartdrv /x” at the DOS prompt.

Unattended Installation Over the Network: 

Unattended Installation Over the Network Create an answer file using Setup Manager (setupmgr.exe) from the Windows 2000 Support Tools Use the /s and /u (or /unattend) switches to specify the location of the installation files and 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

Unattended Installation via CD-ROM: 

Unattended Installation via CD-ROM An alternative to a unattended network installation is to create an answer file to use when booting via the CD-ROM When used with booting from a CD-ROM, the answer file MUST be named Winnt.sif

Installation Troubleshooting Tip: 

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 a multiprocessor computer, restart the installation, press F5, and provide the computer manufacturer’s Hal.dll

Installation Part 1: 

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

Installation Part 1 (continued): 

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

Installation Part 1 (continued): 

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

Installation Part 1 (continued): 

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

Installation Part 1 (continued): 

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

Installation Part 2: 

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

Installation Part 2 (continued): 

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

Installation Part 2 (continued): 

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

Installation Part 2 (continued): 

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

Installation Part 2 (continued): 

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

Installation Part 2 (continued): 

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)

Installation Part 2 (continued): 

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

Installation Part 2 (continued): 

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

Log On and Test the Server: 

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

Configure Your Server Tool: 

Configure Your Server Tool Figure 5-8 Configuration dialog box

Testing the Desktop Icons: 

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

Desktop: 

Desktop Figure 5-9 Windows 2000 Desktop

Upgrading a Windows NT 4.0 Server and Domain: 

Upgrading a Windows NT 4.0 Server and Domain Coordinate a time for the upgrade Backup each server that will be upgraded You must upgrade the PDC first Upgrade the BDCs one at a time Upgrade using Winnt32 Select the Upgrade to Windows 2000 (recommended) option Follow the directions in the Windows 2000 Setup

Upgrading a Windows NT 4.0 Server and Domain (continued): 

Upgrading a Windows NT 4.0 Server and Domain (continued) Figure 5-10 Selecting the upgrade option

Upgrading a Windows NT 4.0 Server and Domain (continued): 

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

Troubleshooting Tip: 

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

Boot.ini File: 

Boot.ini File The Boot.ini file on the system partition contains information about the location of certain files necessary to boot the operating system. You can edit the boot.ini file using any text editor such as notepad. You will have to turn off the “read-only” attribute before editing the file.

Sample Boot.ini File: 

Sample Boot.ini File Figure 5-2 Boot.ini file

ARC Pathname Rules:: 

ARC Pathname Rules: Example 1 multi(0)disk(0)rdisk(1)partition(1)\WINNT Example 2 scsi(1)disk(2)rdisk(0)partition(1)\WINNT “scsi” = SCSI disk with BIOS disabled “multi” = IDE disk or SCSI disk with the BIOS enabled

ARC Pathname Rules:: 

ARC Pathname Rules: “disk” = the ID of the SCSI device in the SCSI chain starting with 0. Only used when the arcpath begins with “scsi”. “rdisk” = the ID of the non-scsi device starting with 0. Only used when arcpath begins with “multi”. “partition” = the number of the partition (counting from 1-4) where the Windows 2000 system files are installed.

Service Packs: 

Service Packs Check Microsoft’s Web site for the latest information about service packs and the option to download them Install service packs using the Update.exe command

Chapter Summary: 

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

Chapter Summary: 

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