Chapter Overview

1
Chapter Overview

• Installing New Hardware
• Installing Updates
• Managing Client Access Licenses
• Troubleshooting Boot Problems

2
Installing New Hardware

• This is a common maintenance task that
  administrators perform.
• Many hardware devices can be installed by using
  Add/Remove Hardware in Control Panel.
• The procedures for installing various hardware
  devices are similar, regardless of the type of
  device being installed.

3
Understanding the Hardware Installation Process

• Installing hardware is a two-part process
• Install the physical device.
• Install a device driver in the computer.
• A device driver is a software component that
  provides the interface between the piece of
  hardware and the operating system.

4
Understanding the Hardware Installation Process
(Cont.)

• The hardware device and the device driver must be
  configured to use the same hardware resources.
• There are four hardware resource types
• Interrupt requests (IRQs)
• Input/output (I/O) port addresses
• Direct memory access (DMA) channels
• Memory addresses
• Configuring the driver and the hardware can be a
  difficult process.

5
Using Plug and Play

• Plug and Play allows Microsoft Windows 2000 to
  automatically detect new hardware and install the
  appropriate device driver with little or no user
  intervention.
• Plug and Play capabilities
• Detects the new hardware
• Assesses devices already installed on the
  computer and the resources they use
• Configures both the hardware device and the
  driver to use available resources

6
Installing NonPlug and Play Hardware

• When the hardware you want to install does not
  support Plug and Play, you can install device
  drivers manually by using the Add/Remove Hardware
  Wizard.
• To start the wizard, open Control Panel and then
  double-click Add/Remove Hardware.

7
The Add/Remove Hardware Wizard Choose a Hardware
Task
8
The Add/Remove Hardware Wizard Choose a Hardware
Device
9
The Add/Remove Hardware Wizard Select a Hardware
Type
10
The Add/Remove Hardware Wizard Select a Device
Driver
11
Configuring System Resource Settings

• You can use Device Manager to view or modify the
  system resources used by a device driver.
• Device Manager displays
• The resources used by a device
• The settings of those resources
• Whether resource conflicts are present
• Device Manager is accessed in the Hardware tab in
  the System application in Control Panel.

12
The Device Manager Window
13
The Resources Tab for a Hardware Device in Device
Manager
14
The Device Manager Status Display

• There are three Device Manager status indicator
  icons
• Normal icon the device is operating properly.
• Icon with ! the device is incorrectly configured
  or drivers are not functioning properly.
• Icon with stop sign the device is disabled
  because of resource conflicts.

15
Driver Signing

• Windows 2000 drivers and operating systems are
  digitally signed by Microsoft.
• Sometimes applications overwrite existing
  operating system files as part of their
  installation process.
• By verifying the digital signatures on Windows
  2000 system files, you can determine if they have
  been altered.

16
Configuring Driver Signing

• To configure how the computer responds to
  unsigned files, click Driver Signing in the
  Hardware tab in the System application.
• There are three file signature verification
  settings
• Ignore enables all files to be installed
• Warn displays a warning message before
  permitting an unsigned file to be installed
• Block prevents the installation of unsigned
  files

17
Monitoring and Troubleshooting Driver Signing

• You can also use Windows 2000 System File Checker
  (SFC), a command-line utility, to check the
  digital signature of files.
• The syntax of the SFC utility is
• Sfc /scannow /scanonce /scanboot /cancel
  /quiet /enable /purgecache /cachesizex

18
Using the File Signature Verification Utility

• Use the Windows 2000 File Signature Verification
  utility (Sigverif.exe) to determine if any files
  are not digitally signed.
• You can configure the File Signature Verification
  Utility to examine system files only or nonsystem
  files as well.
• To use it, click Start, point to Run, type
  sigverif, and press Enter.

19
Lesson Summary

• Windows 2000 supports Plug and Play.
• Use the Add/Remove Hardware Wizard to install
  most hardware devices.
• Use Device Manager to view or modify the system
  resources used by a device driver.
• Configure driver signing by using the Hardware
  tab in the System application.
• Use SFC or the File Signature Verification
  utility to verify the digital signature of driver
  files.

20
Installing Updates

• Applications and operating systems must be
  updated.
• Microsoft provides three different methods for
  obtaining and installing updates
• Install Windows 2000 service packs.
• Apply hotfixes.
• Use the Windows Update Web site.

21
Installing Windows 2000 Service Packs

• A service pack is a collection of software
  patches with a single installation program that
  has been tested and found to be stable.
• Microsoft service packs are cumulative.
• There are two types of Microsoft service pack
  downloads
• Express installation
• Network download

22
Testing and Evaluating Service Packs

• Before you deploy a service pack on your network
• Read the documentation supplied with the service
  pack
• Familiarize yourself with the issues the service
  pack addresses
• Test the service pack on a single computer and
  monitor it for a few days

23
Slipstreaming

• Is the process of streamlining the service pack
  installation for new network workstation
  deployments by integrating the service pack into
  the Windows 2000 distribution files
• Works only on new Windows 2000 installations, not
  on existing computers running Windows 2000 on the
  network

24
Deploying Service Packs

• Ways to automate the installation of service
  packs on existing computers running Windows 2000
• Microsoft Windows Installer Service works with
  Group Policy to deploy a software installation
  package
• Microsoft Systems Management Server (SMS) a
  network management product used to distribute
  software

25
Applying Hotfixes

• Hotfixes are software updates released between
  major service pack releases.
• They typically address a single problem or issue.
• They are not as fully tested as service packs.
• Format
• Q_XXX_YYY_ZZZ_LL.EXE

26
Using Windows Update

• You can also keep computers running Windows 2000
  updated by using the Windows Update Web site at
  http//www.microsoft.com/windowsupdate/.
• At this site, you can download an applet that
  will scan your computer and display available
  product updates for that computer.
• You can update only the computer on which you
  access the site.

27
The Windows Update Web Site
28
Verifying Update Installations

• Sometimes you need to determine whether a
  computer has had a particular service pack or
  hotfix installed.
• Microsoft provides two tools for this purpose
• Winver.exe
• Add/Remove Programs

29
The About Windows Dialog Box

• Use Winver.exe to display the About Windows
  dialog box, which displays the version of the
  operating system and latest service pack
  installed.

30
The Add/Remove Programs Tool

• Use Add/Remove Programs to display a list of
  installed hotfixes.

31
Removing Service Packs and Hotfixes

• There are two ways to uninstall a Windows 2000
  service pack
• Use Add/Remove Programs in Control Panel.
• Run the service pack's uninstall program
  (Spuninst.exe) from the command prompt.
• To uninstall a Windows 2000 hotfix, use
  Add/Remove Programs.

32
Lesson Summary

• A Microsoft service pack is a cumulative
  collection of software patches with a single
  installation program.
• You can deploy service packs to a large group of
  computers by using Windows Installer Service or
  SMS.
• Hotfixes are software updates released between
  major service pack releases.
• You can uninstall service packs and hotfixes.

33
Managing Client Access Licenses

• A client computer requires a license to access a
  computer running Windows 2000 Server.
• Administrators must ensure that their
  organization has sufficient licenses for its
  software products.

34
Understanding Windows 2000 Licensing Modes

• When you purchase an operating system, it comes
  with a license to run that operating system on
  one computer.
• With a client access license (CAL) assigned, a
  client computer running any operating system can
  access and use resources on a computer running
  Windows 2000 Server.
• You can configure a computer running Windows 2000
  Server to use CALs in either of two modes Per
  Server or Per Seat.

35
Understanding Windows 2000 Licensing Modes
(Cont.)

• Per Server licensing mode
• CALs are purchased and assigned to a particular
  server and can be used by any client computer.
• The server permits only as many simultaneous
  connections to the server as it has licenses. 
• Per Seat licensing mode
• A CAL is purchased and assigned to every client
  computer.
• A client computer with a CAL can access one or
  more computers running Windows 2000 Server
  simultaneously and still use only one CAL.

36
Choosing a Licensing Mode

• You specify the licensing mode when you install
  Windows 2000 Server.
• Per Server licensing is usually best on a
  single-server network.
• When there are multiple Windows 2000 servers on a
  network, evaluate the number of concurrent
  connections.
• How many concurrent connections per server are
  needed?
• How many client computers connect to any server?
• If the number of concurrent connections is less
  than the number of clients, use Per Server. If
  not, use Per Seat.

37
Choosing a Licensing Mode (Cont.)

• If you do not know which mode to use, choose Per
  Server.
• You cannot legally change from Per Seat mode to
  Per Server mode.
• Legally, you can change from Per Server mode to
  Per Seat mode one time only.

38
Using the Windows 2000 Licensing Tools

• For Per Server mode, use the Licensing tool in
  Control Panel to manage licenses on individual
  Windows 2000 servers.
• For Per Seat mode, use the Licensing Manager (in
  the Administrative Tools program group) to manage
  licenses on a site license server for all Windows
  2000 servers in an enterprise.

39
Using the Licensing Tool in Control Panel

• The Licensing tool manages licenses for a single
  Windows 2000 server operating in Per Server mode.
• You can use this tool to
• Add or remove CALs
• Configure replication of licensing information
• Change the licensing mode from Per Server to Per
  Seat

40
The Choose Licensing Mode Dialog Box
41
Using the Licensing Manager

• The Licensing Manager manages licenses for an
  entire enterprise.
• You can use this tool to
• View the Per Server and Per Seat licenses for the
  site
• View usage statistics
• Add or remove Per Seat CALs on any site license
  server
• Add or remove Per Server CALs for any server
• Change the licensing mode of any server
• Configure the replication of licensing
  information

42
The Windows 2000 Licensing Manager
43
Lesson Summary

• A CAL enables a client computer to access and use
  resources on a computer running Windows 2000
  Server.
• There are two Windows 2000 licensing modes Per
  Server and Per Seat.
• Use the Licensing tool to manage licenses on
  individual Windows 2000 servers in Per Server
  mode.
• Use the Licensing Manager tool to manage licenses
  on a site license server for Windows 2000 servers
  in Per Seat mode.

44
Troubleshooting Boot Problems

• The consequences of boot problems on a network
  can be serious, especially when they occur on a
  network server.
• There are several methods for troubleshooting
  boot problems
• Boot a computer running Windows 2000 in Safe
  mode.
• Use the advanced boot options.
• Create a parallel installation.
• Use the Recovery Console.

45
Using Safe Mode

• In Safe mode, only the essential operating system
  files and drivers are loaded, providing basic
  access to the computer while allowing you to
  repair a malfunctioning driver.
• To boot a computer running Windows 2000 in Safe
  mode, press F8 during the operating-system
  selection phase of the boot process, and then
  select Safe Mode.

46
Using Advanced Boot Options

• In addition to the Safe mode options available,
  the Advanced Options Menu offers the following
  options
• Enable Boot Logging
• Enable VGA Mode
• Last Known Good Configuration
• Directory Services Restore Mode
• Debugging Mode
• Boot Normally

47
Creating a Parallel Installation

• This method involves installing a second copy of
  Windows 2000 on the computer that has the boot
  problem. To do this
• 1. Try to install the second instance of Windows
  2000 into another partition, or at least into a
  different folder.
• 2. Then boot to the secondary copy of Windows
  2000 and perform repairs.
• A parallel installation lets you access drives
  formatted with the NT file system (NTFS).

48
Using the Recovery Console

• This Windows 2000 command-line interface can be
  used to
• Start and stop services
• Read and write data on a local drive, including
  drives formatted with the NT file system (NTFS)
• Format hard disks

49
Installing and Starting the Recovery Console

• You need access to the Windows 2000 Server
  installation files, either on a CD-ROM or on the
  network.
• To install the Recovery Console
• 1. Click Start, and then click Run.
• 2. Click Browse, and then navigate to the \I386
  folder on the Windows 2000 Server CD-ROM or
  network share.
• 3. Select the Winnt32.exe program file, and then
  click Open. 
• 4. Add the /cmdcons parameter to the Winnt32.exe
  command line, and then click OK.
• 5. In the Windows 2000 Setup dialog box (which
  prompts you to install the Recovery Console),
  click Yes, and then click OK.
• To start the Recovery Console, select it from the
  Please Select The Operating System To Start menu
  during the boot process.

50
Running the Recovery Console from CD-ROM

• If a computer does not have the Recovery Console
  installed on it, you can run the Recovery Console
  directly from the installation CD-ROM.
• 1. Insert the Windows 2000 Server CD-ROM in the
  CD-ROM drive, and then restart the computer.
• 2. In the Windows 2000 Server Setup screen, type
  R.
• 3. In the Windows 2000 Repair Options screen,
  type C to start the Recovery Console.

51
Using the Recovery Console

• The Recovery Console looks like a standard
  Windows 2000 command prompt and uses many of the
  same commands.
• After you finish using the Recovery Console, type
  exit at the command prompt, and then press Enter.

52
Lesson Summary

• In Safe mode, only essential operating system
  files and drivers are loaded, providing basic
  access to the computer while allowing you to
  repair a malfunctioning driver.
• A parallel installation is a second copy of
  Windows 2000 installed on the same computer in a
  different folder or partition.
• The Recovery Console is a command-line interface
  that enables you to perform basic maintenance and
  troubleshooting tasks without loading the
  complete operating system.