Chapter2 Installing Windows Server 2003, Standard Edition
Preparing for Installation • Identify hardware requirements and compatibility. • Choose a file system. • Choose a licensing mode. • Decide which protocols to install. • Determine domain or workgroup membership.
Hardware Requirements • Computer should exceed the minimum requirements
Hardware Compatibility • Check the HCL for Windows Server 2003. • Most recent hardware compatibility list is on the Microsoft Web site. • Look for “Designed for Windows Server 2003” logos on products. • Upgrade the BIOS if necessary. • Determine the BIOS version. • Check with the computer manufacturer for compatibility and upgrade files.
Determining Disk Partitioning Options • Setup program determines current partitions. • Setup presents options for partitioning hard disk. • Create a new partition on an unpartitioned hard disk. • Only create the operating system partition during Setup. • Add other partitions with Disk Management later. • Create a new partition on a partitioned hard disk. • Install on an existing partition. • Delete an existing partition.
Choosing a File System • File systems format the hard disk. • Windows Server 2003 supports FAT16, FAT32, and NTFS. • NTFS is recommended because of advanced features such as: • Security and encryption • File compression • Disk quotas • NTFS is required for hosting Active Directory.
FAT16 FAT32 NTFS Tera - 240 (1,099,511,627,776) bytes. Exa - 260 (1,152,921,504,606,846,976) bytes. Moves data and Marks bad sectors Transparently!
File Systems (cont.) • Can use the convert utility to move from FAT32 to NTFS after installation. (not reversible!)
Choosing a Licensing Mode(see handout) • Purchase a client access license (CAL) after installation. • CAL’s give a client permission to connect to a Windows Server 2003 computer. • Two licensing modes: • Per server (max # accessing a server simultaneously) • Per seat (one for each client or pc but may have multiple servers) • Per seat is preferred for companies with more than one server. • One time conversion from per server to per seat.
Making a Protocol Selection • The default protocol setup: • TCP/IP with an assumedDHCP server • Used on most networks • Additional protocols can be configured after installation.
Determining Membership • Workgroup • Provide name of workgroup. • Domain • Provide DNS name of existing domain and join if have administrative domain account. OR • Have administrator create a computer account prior. (Verify that one domain controller and DNS server are present.)
Overview of Installation • Methods • CD-ROM • Network • Upgrade • Unattended • Installation files • Winnt for CD-ROM or network installation for Windows operating systems before Windows 95 • Winnt32 for operating systems Windows 95 or higher (32 bit windows environment) • Windows NT must have Service Pack 5 or higher for an upgrade.
CD-ROM Installation • Verify that the computer’s BIOS boots from CD-ROM: • Insert installation CD-ROM into drive. • Turn off power. • Turn on power and boot from CD-ROM. • Follow the instructions of the Setup program.
Network Installation • Copy installation files to a host computer. • Share the host’s folder and assign read permissions. • Connect to the shared folder from the target computer. • Run Winnt.exe or Winnt32.exe with any desired switches. • Follow Setup instructions.
Installing from an Existing Operating System • Upgrades are possible from the following: • Windows NT Server 4.0 (running Service Pack 5 or higher) • Windows 2000 Server • Steps to begin upgrade: • Boot the current OS. • Insert the installation CD-ROM. • Choose the Upgrade option on the Setup screen. • Keeps existing settings and applications.
Unattended Installation • Usually performed via a network installation • Before installation, specify a set of parameters in an answer file. • The answer file contains responses to questions asked during installation such as computer name. • No license agreement is presented during Setup.
Performing a CD-based Attended Installation: Phase 1 • Boot from the Standard Edition CD-ROM. • Installation Setup process is similar for all methods. • First phase of Setup: • Inspect configuration and load files. • Display license agreement. • Scan hard drive to determine OS, partitions, and file systems. • Prompt user to choose partition and file system. • Partition is formatted with file system.
Performing a CD-based Attended Installation: Phase 2 • Second phase of Setup prompts user for: • Language, date, time, and network settings • Product Key • Licensing mode • Computer name, Administrator account, and password • Domain or workgroup membership • Setup completes installation. • Installs and registers selected components. • Installs Start menu items. • Saves settings and removes temporary files.
Performing an Unattended Installation • Create an answer file. (Unattend.txt & UDF file) • Use a text editor or Setup Manager Wizard. • Option to use answer file with booting • Save the answer file as Winnt.sif on a floppy disk. • Boot from CD-ROM. • Insert floppy after first Setup screen.
Installing and Managing Service Packs • Download the latest service pack from the Microsoft Web site. • Check regularly for updates to correct security issues and improve performance. • Review the documentation on installation procedures and problems. • Perform a full backup on a production server. • Alert clients to the installation schedule. • After installation, document problems and solutions and backup.
Creating an Automated System Recovery Set • An ASR set contains two components for system recovery: • Backup of all system files (1.5 GB or more) • Backup of system settings (approx. 1.44 MB requires a floppy drive!) • ASR does not(?) back up application data files. • Create an ASR with the Backup utility. • Make a new ASR set each time there is an important change to the server. • Adding protocols • Installing new drivers
Read through table 2-4 on pages 55 – 56 for common installation problems and procedures.! Review Homework for Chapter 2& Perform Lab Exercise #1