Description
This is the fifth course in a seven-part series intended for network support professionals working in a Microsoft Windows NT Server 4.0 based enterprise environment. The series aims to enable these professionals to pass Microsoft's certification examination 70-68. This series gives participants the opportunity to design, implement, and support the Windows NT Server network operating system in a multidomain enterprise environment.
Audience
This series is intended for IT professionals who will be responsible for supporting Windows NT Server 4.0 in an enterprise environment. In addition, this series aims to enable these professionals to pass Microsoft's certification examination 70-068. Participants should have taken Networking Essentials 2nd Edition (courses 71441-71444) and Supporting Microsoft Windows NT 4.0 Core Technologies (courses 71410-71413) and the first four courses in this series.
Prerequisites
(Currently no course prerequisite information)
Objective
- Identify the troubleshooting methodology, functions of the Kernel Mode networking components and Distributed networking Components.
- Identify the registry structure, subtrees and configuration information about a local machine.
- Identify the functions of the processes in every boot phase and troubleshoot through system files.
- Match the stop screen sections and parameters with their contents and use various debugging utilities.
- Identify types of startup errors and troubleshoot disk related and configuration problems.
- Troubleshot RAS problems, resource access and permission problems, recover a mirror set and stripe set with parity.
Topics Include
Unit 1: Troubleshooting from an Architectural Perspective - Identify the steps of the troubleshooting methodology and the components of the Windows NT executive.
- Identify the function of the Windows NT Architectural layers.
- User Mode.
- Kernel Mode.
- Identify the functions of the Kernel Mode components in Windows NT Executive, Executive Services Layer, Microkernel Layer, Hardware Abstraction Layer.
- Identify the functions of the Distributed Networking components of the Networking Architecture.
Unit 2: Modifying the System through the Registry - Match the Windows NT components with the way in which they use the information stored in the registry.
- Match the registry subtrees with the information they store.
- Display a registry subkey content using the Registry Editor.
- Set up an interactive session to troubleshoot through a remote Windows NT server registry, using the remote command service.
- Match the HKEY_LOCAL_MACHINE subtree to the information they store.
- Match the HKEY_LOCAL_MACHINE\HARDWARE subtrees with their functions.
- Identify the subkeys of HKEY_LOCAL_MACHINE\SYSTEM.
- Match the subkeys of CurrentControlSet to their functions.
- Match the CurrentControlSet\Services value entries to their functions.
- Match the CurrentControlSet\Services value names with their functions.
- Troubleshoot the problem using the Drives Utility, given that a service has failed to initialize.
- Troubleshoot service problems using the services subkey value entries.
Unit 3: Boot Failures: Troubleshooting - Match processes in every boot phase to their functions, Initial Phase, Boot Loader Phase, Kernel Phase, Logon Phase.
- Set the parameters in the Boot.ini file using the system editor, Timeout, Default.
- Match the Boot.ini switches with their functions.
- Match the column names of the DRIVERS utility to the information they display.
- Enable event logging using the Registry Editor.
- Match the Emergency Repair Process options to their functions.
- Replace corrupted files using the Expand-R command.
- Create an Emergency Repair Disk.
- Create a disk to use the Windows NT hardware detection tool.
- Display registry information, using the Windows NT diagnostics administrative tool.
- Display hardware components using the debug version of Ntdetect.com.
- Display Windows NT compatible hardware using the hardware query tool.
Unit 4: Stop Screens and Debugging Utilities - Match the stop screen sections with their contents.
- Match the stop screen parameters with the information they display.
- Match the debugging terms with their descriptions.
- Match the debugger types with their features.
- Identify the functions of the debug setup methods.
- Configure the Windows NT Kernel Debugger.
- Setup the Windows NT Kernel Debugger for remote access.
- Configure Windows NT system to store the content of a stop screen in a dump file and use the following Utilities, DumpCheck, DumpExam, Dr. Watson.
Unit 5: Troubleshooting System Problems - Identify the types of startup problems on x86 systems.
- Troubleshoot system partition problems using the FDISK utility.
- Display the Master Boot Record using the DiskProbe utility.
- Display the Partition Boot Sector using the DiskProbe utility.
- Identify the causes of CMOS problems.
- Identify the types of problems that are rectified using the LastKnownGood configuration.
- Match the post logon disk problems with their solutions.
Unit 6: Troubleshooting Connectivity and Resource Access Problems - Create a DEVICE.LOG file to troubleshoot modem problems using the Registry Editor.
- Create a PPP.LOG file to solve authentication problems using the Registry Editor.
- Match the error messages related to port problem with their solutions.
- Match the printer problems with their solutions and the permission problems with their solutions.
- Sequence the steps to construct the mirror set.
- Sequence the steps to reconstruct a stripe set with parity.
Duration
8
Minimum Requirements
The CDROM version of this course requires:
- At least a 486DX 33Mhz CPU.
- Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
- At least 8MB RAM.
- At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).
- At least a double speed CDROM drive.
- An MPC compliant sound card with attached speakers or headphones is recommended (Currently, only the CDROM version supports audio).
The network version of this course requires:
- At least a 486DX 33Mhz CPU.
- Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
- At least 8MB RAM and 22MB available hard disk space or file server space.
- At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).
Media
|
