Chapter2 Installing Windows Server 2003, Standard Edition
Objectives • Prepare for a Windows Server 2003 installation • Explain and perform the different Windows Server 2003 installation methods, such as attended, unattended, and upgrades • Install and manage service packs • Create an Automated System Recovery set • Troubleshoot installation problems • Uninstall 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 Hardware Compatibility List (HCL) for Windows Server 2003. • Most recent hardware compatibility list is on the Microsoft Web site: http://www.microsoft.com/whdc/hcl/default.mspx • 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 present 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. • Check partitioning with the Disk Management Snap-in if upgrading from Windows 2000 Server.
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 • POSIX support • Indexing • NTFS is required for hosting Active Directory.
File Systems (cont.) • Use the convert utility to move from FAT32 to NTFS after installation.
Choosing a Licensing Mode • 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 • Per seat • Per seat is preferred for companies with more than one server.
Making a Protocol Selection • The default protocol setup: • TCP/IP with an assumed DHCP server • Used on most networks • Additional protocols can be configured after installation. • NetBEUI is not supported by Windows Server 2003 or by Windows XP Professional. • Convert to TCP/IP before upgrade.
Determining Membership • Workgroup • Provide name of workgroup. • Domain • Provide DNS name of domain. • Create a computer account. • 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, or for Windows operating systems before Windows 95 • Winnt32 for operating systems Windows 95 or higher • Windows NT must have Service Pack 5 or higher.
Switches • Winnt and Winnt32 support switches to customize installation. • /s • Specifies location of installation files • /a • Initiate accessibility options • /checkupgradeonly • Checks compatibility • /? • Command-line Help
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. • First create a shared network folder on the host. • 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. • Keep 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. • No license agreement is presented during Setup.
Performing a CD-based Attended Installation • 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 (cont.) • 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. • 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. • Option to specify components • Create a Cmdlines.txt file to use with the answer file. • Use the Sysprep.exe or Syspart.exe programs to clone server operating systems.
Upgrading a Windows NT Server and Domain • Two methods: • Upgrade member servers first. • Upgrade domain controllers first. • Guidelines • Schedule the upgrade during minimal access times. • Back up each server and registry. • Create an emergency repair disk. • If upgrading domain controllers first, then: • Take one BDC out of production as a backup. • Upgrade the PDC first.
Upgrading a Windows NT Server and Domain (cont.) • Installation steps: • Start Winnt32.exe. • Select Upgrade during Setup and retain existing settings. • Upgrade Active Directory with the Active Directory Installation Wizard. • After installation, convert the domain to either Windows 2000 native mode or to Windows .NET mode.
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.
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) • 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
Troubleshooting Installation Problems • Most installations problems are related to hardware or hardware drivers. • Many issues can be avoided by testing hardware and performing diagnostics before installation. • Find solutions through documentation.
Uninstalling Window Server 2003, Standard Edition • Back up important data. • Boot from the CD-ROM of the new operating system. • Can also boot from the Windows Server 2003 CD-ROM and exit Setup after deleting the partition • Restart the computer. • Choose to delete and/or format the partition on which Standard Edition is installed. • Install the new operating system.
Summary • Preinstallation tasks: • Verify hardware is compatible through the HCL. • Determine system configurations. • Installation methods: • CD-ROM • Network • Upgrade • From Windows NT Server 4.0 with Server Pack or higher, or Windows Server 2000 Server • Unattended • Create an answer file to automate the installation.
Summary • Upgrading a Windows NT 4.0 domain: • Begin with member servers or domain controllers. • PDC should be upgraded first. • Service packs should be installed to fix any known problems. • Create an ASR set after installation. • Uninstalling Windows Server 2003: • Repartition and format the hard drive. • Install the new operating system.