1. Goals Identify pre-installation tasks
Understand the phases of the installation process
Install Windows Server 2003 using the CD-ROM
Install Windows Server 2003 over a network
Upgrade Windows NT Server or Windows 2000 Server
Troubleshoot failed installations
Work with the Add Hardware Wizard
Work with the Device Manager
Configure driver signing options
Work with hardware profiles and event logs

2. Identifying Pre-installation Tasks
(Skill 1)
Identifying Pre-installation Tasks
Minimum hardware requirements
Pentium 133 MHz or faster processor
VGA monitor
128 MB RAM for five or fewer clients and 256 MB for larger networks
1.5 GB hard disk space is required for setup; 2.5 GB hard disk space is recommended
High-density, 3.5-inch floppy disk drive
A 12X CD-ROM drive when installing from CD
A network interface card (NIC) if network connectivity is required
Mouse and keyboard

3. Identifying Pre-installation Tasks (2)
(Skill 1)
Identifying Pre-installation Tasks (2)
Other pre-installation tasks
Make sure that the hardware components of the system are listed on Microsoft’s Windows Server Catalog
Determine whether it is a new installation or an upgrade of an existing version
Examine hard disk partitions (Microsoft recommends a partition of at least 2 GB)
Determine the file system format for the partition (FAT, FAT32, or NTFS)
Determine whether the computer on which Windows Server 2003 is to be installed will be joining a workgroup or domain
Decide which Windows Server 2003 optional components to install

4. Identifying Pre-installation Tasks (3)
(Skill 1)
Identifying Pre-installation Tasks (3)
Other pre-installation tasks
Uncompress any compressed volumes on the computer before upgrading to Windows Server 2003
You can only upgrade to Windows Server 2003 if the drive was compressed with NTFS compression
Disable disk mirroring
Disable any anti-virus software installed on the computer
Check for software compatibility using the Microsoft Application Compatibility Analyzer tool
Disconnect UPS devices from the computer on which Windows Server 2003 is to be installed

5. Figure 2-1 Microsoft Application Compatibility Analyzer
(Skill 1)
Figure 2-1 Microsoft Application Compatibility Analyzer

6. Identifying Pre-installation Tasks (4)
(Skill 1)
Identifying Pre-installation Tasks (4)
Licensing modes for Windows Server 2003
Per Server licensing mode
Provides a specific number of Client Access Licenses (CALs) per server
Suitable for small companies
Need enough CALs to over all simultaneous users
Per Device or Per User licensing mode
Provides a separate CAL for each named user or specified device
Ideal for large networks

7. Figure 2-2 Types of Windows Server 2003 licenses
(Skill 1)
Figure 2-2 Types of Windows Server licenses

8. (Skill 2)
Identifying the Different Phases of the Windows Server 2003 Installation Process
Pre-copy phase
Text mode phase
GUI mode phase
Gathering Information About Your Computer stage
Installing Windows Server 2003 Networking Components stage
Completing Setup stage

9. Figure 2-3 The three installation phases
(Skill 2)
Figure 2-3 The three installation phases

10. Figure 2-4 The three stages of the GUI Mode Phase
(Skill 2)
Figure 2-4 The three stages of the GUI Mode Phase

11. Figure 2-5 Completing Setup
(Skill 2)
Figure 2-5 Completing Setup

12. Installing Windows Server 2003 Using the Installation CD-ROM
(Skill 3)
Installing Windows Server Using the Installation CD-ROM
Attended installation
Requires user interaction
The most common method for an attended installation is using the installation CD-ROM
Full installations are performed on computers that either have no current operating system or that have an operating system that you are going to overwrite

13. Figure 2-6 Welcome to Setup
(Skill 3)
Figure 2-6 Welcome to Setup

14. Figure 2-7 Windows Licensing Agreement
(Skill 3)
Figure 2-7 Windows Licensing Agreement

15. Figure 2-8 List of existing partitions and unpartitioned space
(Skill 3)
Figure 2-8 List of existing partitions and unpartitioned space

16. Figure 2-9 Windows Server 2003 Setup
(Skill 3)
Figure 2-9 Windows Server 2003 Setup

17. Figure 2-10 Licensing Modes
(Skill 3)
Figure 2-10 Licensing Modes

18. Figure 2-11 Passwords message box
(Skill 3)
Figure 2-11 Passwords message box

19. Figure 2-12 Welcome to Windows Microsoft Windows Server 2003
(Skill 3)
Figure 2-12 Welcome to Windows Microsoft Windows Server 2003

20. Figure 2-13 Activating the Server License
(Skill 3)
Figure 2-13 Activating the Server License

21. Installing Windows Server 2003 Over a Network
(Skill 4)
Installing Windows Server 2003 Over a Network
Considerations
If you are performing a network installation from a shared folder, you must connect to the share, then locate and open the \I386 folder
If you are connecting to the share from a computer with MS-DOS or Windows 3.x installed, you must run Winnt.exe
If you are connecting to the network share from a computer with Windows 9.x, Windows NT 3.51 or higher, or Windows 2000 Server installed, you must run Winnt32.exe
You can customize the installation of Windows Server 2003 by using various switches

22. Installing Windows Server 2003 Over a Network (2)
(Skill 4)
Installing Windows Server 2003 Over a Network (2)
Unattended installation
Enables you to install Windows Server 2003 on multiple computers over a network via an automated process
An answer file provides all specifications normally entered by a user
The files required to install Windows Server 2003 over a network are stored in a distribution folder
Answer files and distribution folders are created using the Setup Manager

23. Figure 2-14 Winnt.exe and Winnt32.exe
(Skill 4)
Figure 2-14 Winnt.exe and Winnt32.exe

24. (Skill 5)
Upgrading Windows NT Server or Windows 2000 Server to Windows Server 2003
Before upgrading
Perform a full backup of your computer with a complete recovery procedure
Run a hardware and software compatibility check from the Windows Server 2003 installation CD
Review the file systems and partitions that exist on the server
If some of your domain controllers run Windows 2000 and some run Windows NT, upgrade the Windows NT domain controllers as soon as possible
Synchronize primary and backup controllers

25. (Skill 5)
Upgrading Windows NT Server or Windows 2000 Server to Windows Server 2003 (2)
Migration paths
When upgrading from Windows NT 4.0, consider three migration paths related to domain architecture and Active Directory
In-place upgrade preserves existing domain architecture
Migrate Windows NT objects to a new Windows Server 2003 forest and Active Directory structure
Consolidate multiple existing Windows NT domains into a single Active Directory domain configuration

26. (Skill 5)
Upgrading Windows NT Server or Windows 2000 Server to Windows Server 2003 (3)
Supported domain and forest functional levels (modes)
Windows 2000 mixed mode
Windows 2000 native mode
Windows Server 2003 interim mode
Windows Server 2003 mode

27. Figure 2-15 The Welcome to Windows Server 2003 screen
(Skill 5)
Figure 2-15 The Welcome to Windows Server 2003 screen

28. Figure 2-16 The License Agreement screen
(Skill 5)
Figure 2-16 The License Agreement screen

29. Figure 2-17 The Get Updated Setup Files screen
(Skill 5)
Figure 2-17 The Get Updated Setup Files screen

30. Troubleshooting Failed Installations
(Skill 6)
Troubleshooting Failed Installations
Typical problems that may occur during installation
Media errors
Hardware driver errors
Insufficient disk space
Failure of Windows Server 2003 to install

31. Troubleshooting Failed Installations (2)
(Skill 6)
Troubleshooting Failed Installations (2)
Common STOP errors
STOP Message IRQL_NOT_LESS_OR_EQUAL
STOP Message KMODE_EXCEPTION_NOT_HANDLED
STOP Message FAT_FILE_SYSTEM or NTFS_FILE_SYSTEM
STOP Message UNKNOWN_HARD_ERROR
STOP Message DRIVER_POWER_STATE_FAILURE
STOP Message INACCESSIBLE_BOOT_DEVICE

32. Figure 2-18 Problems that cause failed installations
(Skill 6)
Figure 2-18 Problems that cause failed installations

33. Figure 2-19 Booting with Last Known Good Configuration
(Skill 6)
Figure 2-19 Booting with Last Known Good Configuration

34. Working with the Add Hardware Wizard
(Skill 7)
Working with the Add Hardware Wizard
Windows Server 2003 is Plug and Play (PnP)-compatible
Common PnP devices are usually detected
Makes it easy to install and configure hardware devices
Use the Add Hardware Wizard when Windows Server 2003 does not automatically detect and install a new hardware device
Windows Server 2003 Setup Dynamic Update feature downloads critical content to enhance the Setup program, including device drivers and replacement files
Use the Add Hardware Wizard to troubleshoot a malfunctioning device

35. Figure 2-20 The Add Hardware Wizard
(Skill 7)
Figure 2-20 The Add Hardware Wizard

36. Figure 2-21 Is the hardware connected? screen
(Skill 7)
Figure 2-21 Is the hardware connected? screen

37. Figure 2-22 The list of installed hardware
(Skill 7)
Figure 2-22 The list of installed hardware

38. Figure 2-23 The Confirm Device Removal dialog box
(Skill 7)
Figure 2-23 The Confirm Device Removal dialog box

39. Figure 2-24 Searching for connected hardware
(Skill 7)
Figure 2-24 Searching for connected hardware

40. Figure 2-25 Completing the Add Hardware Wizard
(Skill 7)
Figure 2-25 Completing the Add Hardware Wizard

41. Working with the Device Manager
(Skill 8)
Working with the Device Manager
Capabilities
Verify the status of hardware devices and update the device drivers associated with these hardware devices
Obtain about hardware is installed and configured information
Obtain information about how the hardware is interacting with other applications on the computer
Uninstall hardware devices
Disable and enable hardware devices
Roll back to a previous version of a driver
Modify resource settings that are allocated for a device

42. (Skill 8)
Figure 2-26 Devices by connections view provides information about how hardware is installed and configured
Devices without drivers will be Unknown and will display a yellow question mark instead of a device icon, while devices that are not working properly will display with a yellow exclamation point over the device icon Click to view the driver provider, file version, copyright, and digital signer as well as the location of the driver files

43. Figure 2-27 The Driver tab in the Properties dialog box for a device
(Skill 8)
Figure 2-27 The Driver tab in the Properties dialog box for a device
Click to view the driver provider, file version, copyright, and digital signer as well as the location of the driver files

44. Working with the Device Manager (2)
(Skill 8)
Working with the Device Manager (2)
Device Manager View menu
Provides a graphical list of all installed hardware devices
Available views
Devices by type
Devices by connection
Resources by type
Resources by connection
Show Hidden Devices

45. Working with the Device Manager (3)
(Skill 8)
Working with the Device Manager (3)
Plug and Play
Automatically configures resources a device needs using system resources that are not currently in use
If a device is not PnP-compatible, you may need to manually configure resource settings on the devices themselves
Resources commonly used by hardware
I/O address
DMA (Direct Memory Access) channel
Interrupt Request (IRQ)
Memory addresses

46. Figure 2-28 Devices by type view
(Skill 8)
Figure 2-28 Devices by type view

47. Figure 2-29 Resources by type view
(Skill 8)
Figure 2-29 Resources by type view

48. Figure 2-30 The Resources tab
(Skill 8)
Figure 2-30 The Resources tab
If the Use automatic settings check box is grayed out, you cannot modify the resources used by the device; if you can clear it, click the Change Setting button to modify a resource setting

49. Figure 2-31 The Edit Direct Memory Access dialog box
(Skill 8)
Figure 2-31 The Edit Direct Memory Access dialog box

50. Figure 2-32 Adding hardware not on the Installed hardware list
(Skill 8)
Figure 2-32 Adding hardware not on the Installed hardware list

51. Figure 2-33 Selecting the type of hardware to install
(Skill 8)
Figure 2-33 Selecting the type of hardware to install

52. Figure 2-34 The Select Network Adapter screen
(Skill 8)
Figure 2-34 The Select Network Adapter screen

53. Configuring Driver Signing Options
(Skill 9)
Configuring Driver Signing Options
Windows Server 2003 uses driver signing options to ensure the use of high quality drivers for any hardware device
Microsoft uses digital signatures for device drivers to identify drivers that are compatible with Microsoft Windows Server 2003
A driver’s digital signature indicates that the driver was tested with Windows for compatibility and has not been altered since testing

54. Configuring Driver Signing Options (2)
(Skill 9)
Configuring Driver Signing Options (2)
Levels of driver signing security
Ignore setting
Allows any driver to be installed
The driver does not need to have a digital signature
Warn setting
Default setting
Notifies the user if a driver that is being installed does not have a Microsoft digital signature
Block setting
Prevents the installation of unsigned drivers
The installation program will not install any device driver that does not have a digital signature

55. Figure 2-35 Opening the System Properties dialog box
(Skill 9)
Figure 2-35 Opening the System Properties dialog box

56. Figure 2-36 The Hardware tab in the System Properties dialog box
(Skill 9)
Click to initiate the Add Hardware Wizard
Click to open the Driver Signing Options dialog box
Figure 2-36 The Hardware tab in the System Properties dialog box

57. Figure 2-37 The Driver Signing Options dialog box
(Skill 9)
Select to set the selected driver signing option as the default option for all of the users that log on to the system
Figure 2-37 The Driver Signing Options dialog box

58. Working with Hardware Profiles and Event Logs
(Skill 10)
Working with Hardware Profiles and Event Logs
Hardware profiles
Describe the selection of a specific configuration of hardware devices (such as network cards, printers, etc.) at the time the operating system is initialized
Are most commonly used in situations where one hardware profile is used at one location and another at an alternate location
Profile 1 (Current)
A default hardware profile created when you install Windows Server 2003
Every device that is installed during the initial installation will be included in Profile 1

59. Working with Hardware Profiles and Event Logs (2)
(Skill 10)
Working with Hardware Profiles and Event Logs (2)
Event logs
Provide historical information to help track system and security problems
Windows Server 2003 computers have at least three logs
Application log contains events recorded by applications
Security log records events generated from audited activities
System log records events logged by Windows components including Error, Warning, and Information event types
Domain controllers have two additional logs
Directory Service log
File Replication log

60. Figure 2-38 The Hardware Profiles dialog box
(Skill 10)
Figure 2-38 The Hardware Profiles dialog box

61. Figure 2-39 Entering a new profile name
(Skill 10)
Figure 2-39 Entering a new profile name

62. Figure 2-40 Selecting profile property options
(Skill 10)
Figure 2-40 Selecting profile property options

63. Figure 2-41 Disabling a device for a hardware profile
(Skill 10)
Figure 2-41 Disabling a device for a hardware profile

64. Figure 2-42 A disabled device in Device Manager
(Skill 10)
Figure 2-42 A disabled device in Device Manager
Disabled devices display with a red x

65. Figure 2-43 Event logs on a member server
(Skill 10)
The System log records events such as the failure of a service or device driver to start at boot time
Figure 2-43 Event logs on a member server

66. Figure 2-44 Event logs on a domain controller/DNS server
(Skill 10)
The Directory Service log records events logged by Active Directory
Figure 2-44 Event logs on a domain controller/DNS server