Contents Module 14: Troubleshooting Client Computer Startup and User Logon Problems Overview The Startup Process for Clients Running Windows 95 and Windows 98 The Windows NT–Based Startup Process Using Advanced Startup Options to Start the Computer 12 Using the Last Known Good Configuration to Start the Computer 19 Lab A: Identifying Client Computer Startup Options 21 Using the Recovery Console 30 Troubleshooting the User Logon Process 35 Lab B: Using the Netdiag Utility to Validate Logon 40 Review 44 Information in this document, including URL and other Internet Web site references, is subject to change without notice Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, places or events is intended or should be inferred Complying with all applicable copyright laws is the responsibility of the user Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property  2001 Microsoft Corporation All rights reserved Microsoft, MS-DOS, Windows, Windows NT, are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries The names of actual companies and products mentioned herein may be the trademarks of their respective owners Module 14: Troubleshooting Client Computer Startup and User Logon Problems iii Instructor Notes Presentation: 90 Minutes This module provides students with the skills and knowledge necessary to troubleshoot client startup and user logon problems Labs: 75 Minutes After completing this module, students will be able to: ! Describe the startup process and the required files for clients running Microsoft® Windows® 95 and Windows 98 ! Describe the startup process and the required files for clients running Microsoft Windows NT® ! Use advanced startup options to start a computer ! Use the Last Known Good configuration to start a computer ! Install and use the Recovery Console to start a computer ! Describe and troubleshoot the user logon process Materials and Preparation This section provides the materials and preparation tasks that you need to teach this module Required Materials To teach this module, you need the following Microsoft PowerPoint® file 2126A_14.ppt Preparation Tasks To prepare for this module: ! Read all of the materials for this module ! Complete the labs iv Module 14: Troubleshooting Client Computer Startup and User Logon Problems Module Strategy Use the following strategy to present this module: ! The Startup Process for Clients Running Windows 95 and Windows 98 Explain the startup process for operating systems running Microsoft Windows 95 and Windows 98 Emphasize that the detailed information refers to the Windows 98 startup process, but that other members of the operating system family behave similarly during their startup process ! The Windows NT–Based Startup Process Explain the structure of the startup process for operating systems in the Microsoft Windows NT family, including Windows NT, Windows 2000, and Windows XP Emphasize that the detailed information refers to the Windows 2000 startup process, but that other members of the operating system family behave similarly during their startup process ! Using Advanced Startup Options to Start a Computer Summarize the various startup options available on Microsoft operating systems, and describe which options are available on which operating systems Present the information on starting the computer in safe mode Explain the differences between the three safe mode options Next, restart the instructor computer, and demonstrate how to find the Advanced Startup Options Use the table that shows available startup options to describe the function of each option, and the circumstances under which each option is used ! Using the Last Known Good Configuration to Start the Computer Explain how the Last Known Good configuration is created and how to use this configuration when troubleshooting the startup process on client computers running Windows NT–based operating systems ! Using the Recovery Console to Start the Computer Emphasize that the Recovery Console is a powerful tool that can help recover a failed operating system, but if it is used incorrectly, it can also damage the operating system Next, explain the tasks that can be accomplished by using the Recovery Console Explain that the Recovery Console can be installed for later use, or run from the product compact disc when needed If you have not already installed the Recovery Console, you can demonstrate the installation process or how to run the Recovery Console from the product compact disc Start the Recovery Console; demonstrate how to enter the administrator’s password, and how to run a command Using the tip in the student materials, ask the students find the Recovery Console commands in Microsoft Windows 2000 Help, describe the various commands, and provide examples of when particular commands might be used Finally, discuss the common reasons for using the Recovery Console ! Troubleshooting the User Logon Process Explain how the user logon process works, and how a user may be logged on with cached credentials if a domain controller cannot be located Also, explain the use of the Netdiag utility to troubleshoot user the logon process Module 14: Troubleshooting Client Computer Startup and User Logon Problems Overview Topic Objective To provide an overview of the module topics and objectives ! The Startup Process for Clients Running Windows 95 and Windows 98 ! The Windows NT-Based Startup Process ! Using Advanced Startup Options to Start the Computer ! Using the Last Known Good Configuration to Start the Computer ! Using the Recovery Console ! Troubleshooting the User Logon Process Lead-in In this module, you will learn about troubleshooting client computer startup and user logon problems *****************************illegal for non-trainer use****************************** Troubleshooting startup and logon problems on client computers are extremely important tasks for a network administrator Startup and logon problems can arise because of missing files, corrupt files, or configuration errors, among other reasons To effectively troubleshoot startup and logon problems on client computers, you must understand both the startup process and the user logon process In addition, knowledge of the special startup options and utilities that are included with Microsoft® operating systems can help you identify and resolve startup problems Important Microsoft operating systems for client computers fall into two major categories: Microsoft Windows® 95– and Windows 98–based operating systems, and operating systems based on Microsoft Windows NT® While the startup and logon process for operating systems in each category are not identical, they are very similar As a result, understanding the startup and logon process for a representative operating system in each category will help you to troubleshoot problems on computers running similar operating systems This module uses Windows 98 as representative of Windows 95– and Windows 98– based operating systems and Windows 2000 as representative of Windows NT– based operating systems Module 14: Troubleshooting Client Computer Startup and User Logon Problems After completing this module, you will be able to: ! Describe the Windows 95– and Windows 98–based startup process and the required files ! Describe the Windows NT–based startup process and the required files ! Use advanced startup options to start a computer ! Use the Last Known Good configuration to start a computer ! Install and use the Recovery Console to start a computer ! Describe and troubleshoot the user logon process Module 14: Troubleshooting Client Computer Startup and User Logon Problems " The Startup Process for Clients Running Windows 95 and Windows 98 Slide Objective To introduce the topics associated with the Windows 95– and Windows 98–based startup process ! Files Required by the Windows 98 Startup Process ! The Windows 98 Startup Process Lead-in To troubleshoot the startup process on computers running Windows 95 or Windows 98, you must understand the files that are required by the process and how the process proceeds *****************************illegal for non-trainer use****************************** Remind students that this topic discusses the Windows 98 startup process, which is representative of, though not identical to, that of Windows 95 To troubleshoot the startup, or boot, process on computers running Microsoft Windows 95 or Windows 98, you must understand the files that are required by the process and how the process proceeds Note When a computer starts, it runs a built-in set of essential software routines known as the basic input/output system (BIOS) The BIOS runs a Power-On Self Test (POST) routine to verify that critical system components are operational, to set all of the hardware to a predefined state, to find and load an operating system, and then to hand off control of the system to the operating system This routine is part of computer hardware’s startup process After the POST routine is completed, the operating system startup process begins Module 14: Troubleshooting Client Computer Startup and User Logon Problems Files Required for the Windows 98 Startup Process Slide Objective To identify the files that are involved in the Windows 98 startup process ! Io.sys—Loads real-mode Windows 98 and drivers Lead-in ! Msdos.sys—Controls startup process ! Config.sys—Sets system environment variables ! Autoexec.bat—Specifies commands before protectedmode Windows 98 starts ! Win.ini and System.ini—Sets some configuration options ! Win.com—Initiates Windows 98 load phases Several files are involved in the Windows 98 startup process *****************************illegal for non-trainer use****************************** Windows 98 requires hundreds of files to run correctly, but several files are particularly important because they are involved in the Windows 98 startup process The following table identifies the location and purpose of the files that are associated with the Windows 98 startup process File and location Purpose C:\Io.sys Starts into real-mode Windows 98 It also loads realmode drivers and terminate-and-stay-resident (TSR) programs specified in Config.sys and Autoexec.bat This file is marked as hidden, system, and read-only C:\Msdos.sys Controls the startup process and is required for compatibility with older applications that require this file to be present before they can be installed This file is marked as hidden, system, and read-only C:\Config.sys Sets and specifies system environment variables and loads real-mode drivers This file is optional C:\Autoexec.bat Sets and specifies commands and TSRs to be executed in real mode before protected-mode Windows 98 initializes This file is optional %windir%\Win.ini, %windir%\System.ini Holds configuration information for Windows 98 Most options that were present for Windows 3.x are now stored in the registry %windir%\Win.com Initiates the Windows 98 load phases Module 14: Troubleshooting Client Computer Startup and User Logon Problems The Windows 98 Startup Process Slide Objective To discuss the stages of the Windows 98 startup process Lead-in ! Real-Mode Startup ! Real-Mode Configuration The Windows 98 startup process has three stages ! # Loads Himem.sys and Ifshlp.sys # Processes Config.sys and Autoexec.bat if present Protected-Mode Load *****************************illegal for non-trainer use****************************** Delivery Tip Emphasize that you are presenting this information to help students understand the overall startup process This is important because problems that occur in the startup process affect troubleshooting The Windows 98 startup process occurs in three distinct stages: real-mode startup, real-mode configuration, and protected-mode load Real-Mode Startup Real mode is the only operating mode that is supported by MS-DOS® In real mode, the processor can execute only one application at a time The Windows 98 real-mode startup process begins when Io.sys loads into RAM Io.sys directs the initialization of the startup process by reading configuration files, such as Config.sys and System.dat, and by initializing the file system for use in drive compression, if specified Problems that occur during the real-mode startup phase may involve difficulties with corrupted or incompatible video or disk subsystem drivers, real-mode drivers, or a damaged registry Real-Mode Configuration Although Windows 98 does not require Config.sys to start, Io.sys processes that file if it is present Even if Config.sys is not present, Windows 98 automatically loads Himem.sys and Ifshlp.sys, which are required to operate Windows 98 and sets several environment variables Io.sys then processes Autoexec.bat, which like Config.sys, is not required but provides backward compatibility with older applications and device drivers Config.sys is not required unless you want to override or add to the default settings Note For more information about the Config.sys settings in Io.sys, see Io.sys Settings under Additional Reading on the Web page on the Student Materials compact disc Module 14: Troubleshooting Client Computer Startup and User Logon Problems Protected-Mode Load After Autoexec.bat runs, Win.com runs and begins the protected-mode load process Protected mode provides support for multitasking and the use of virtual memory Win.com loads Vmm32.vxd and other virtual device drivers according to the registry and System.ini Win.com then switches the processor into protected mode and initializes the virtual device drivers Next, the core Windows kernel, Graphics Device Interface (GDI), and user libraries are loaded, together with the desktop and network support The final step in the startup process is to run applications in the startup group or those in the registry that run at startup Problems encountered during this phase of the startup operation may be attributed to faulty or incompatible protected-mode drivers and difficulties with programs set to launch at startup 32 Module 14: Troubleshooting Client Computer Startup and User Logon Problems Running the Recovery Console from the Compact Disc If you have not installed the Recovery Console as a startup option, and your installation of Windows 2000 ceases to function, start the Recovery Console from the compact disc: Insert the Microsoft Windows 2000 compact disc into your CD-ROM drive, and then restart the computer When the Press any key to boot from CD message appears, press ENTER Allow all of the files to load On the Setup Notification screen, press ENTER On the Welcome to Setup screen, type r for recovery Select an installation to repair, and then type the password for the Administrator account Tip Microsoft Windows 2000 Help contains information about each Recovery Console command You can read and print the function and full syntax for each command Examine this information thoroughly before using the Recovery Console Module 14: Troubleshooting Client Computer Startup and User Logon Problems 33 Using the Recovery Console to Start the Computer Topic Objective To describe the process for using the Recovery Console to start the computer Start the Recovery Console from the Operating System Selection menu or from the compact disc Lead-in To use the Recovery Console to start the computer, you must have the skills to locate and identify problems by using basic commands, and you must know the administrator’s password Select the installation to recover Enter the administrator’s password *****************************illegal for non-trainer use****************************** To use the Recovery Console to start the computer, perform the following steps: Start the Recovery Console from the Operating System Selection menu or from the Microsoft Windows 2000 compact disc If the computer has a dual-boot or multi-boot configuration, select the number representing the installation that you want to repair, and then press ENTER Enter the administrator’s password, and then press ENTER After you enter the administrator’s password, a command prompt will display For information about the available commands, type help and then press ENTER 34 Module 14: Troubleshooting Client Computer Startup and User Logon Problems Common Reasons to Use the Recovery Console Topic Objective To explain when to use the Recovery Console Lead-in The disable, expand, copy, fixboot, and fixmbr commands are most often used in the Recovery Console ! Problem with a service ! Problem with a device driver ! Missing files ! Damaged boot sector ! Damaged master boot record *****************************illegal for non-trainer use****************************** You can use the Recovery Console to fix a variety of startup problems Some of the most common startup problems and their Recovery Console solutions are defined in the following table These solutions are advanced techniques that should be performed by qualified personnel only Problem Recovery Console solution A service or device driver is starting, but it prevents the computer from starting properly Use the disable command to disable the service or driver, restart the computer without the service or driver functioning, and then determine the problem A missing file prevents the computer from starting properly Use the expand command to repair the computer by uncompressing a compressed file and copying it from a floppy disk or compact disc to the appropriate folder A missing file is preventing the computer from starting properly Use the copy command to repair the computer by copying an uncompressed file from a floppy disk or compact disc to the appropriate folder The boot sector is damaged Use the fixboot command to write a new partition boot sector on the system partition The master boot record is damaged Use the fixmbr command to repair the master boot record on the partition boot sector Module 14: Troubleshooting Client Computer Startup and User Logon Problems 35 " Troubleshooting the User Logon Process Topic Objective To introduce the topics associated with troubleshooting the user logon process Lead-in To troubleshoot the user logon process on client computers running Windows operating systems, you must understand the user logon process ! The User Logon Process ! Logging On with Cached Credentials ! Using Netdiag to Verify User Logon *****************************illegal for non-trainer use****************************** To troubleshoot the user logon process on client computers running Windows operating systems, you must understand the user logon process In a networked environment, normally, a user logs on and is authenticated by a domain controller, but if a domain controller cannot be located, the user may still be able to log on 36 Module 14: Troubleshooting Client Computer Startup and User Logon Problems The User Logon Process Slide Objective To illustrate the difference between the logon process in the Windows 95 and Windows 98 operating systems and Windows NT– based operating systems Windows 95 and Windows 98 Domain Controller User User Logon Logon Lead-in The authentication process in Windows 2000 ensures that only valid users can gain access to network or computer resources Windows NT-based Domain Controller User User Logon Logon Computer Computer Logon Logon *****************************illegal for non-trainer use****************************** The logon process for the Windows 95 and Windows 98 operating systems differ from the logon process for Windows NT–Based operating systems Understanding the user logon process for each operating system will help you troubleshoot the process on computers running either family of operating systems The Windows 95 and Windows 98 Logon Process When you start a computer running a Windows 95 or Windows 98 operating system, the computer is not a member of a domain and does not have a computer account Therefore, the computer does not have to authenticate with a domain controller You can configure the system so that when it is started, a logon window appears and the user can log on to the system You can also configure the computer so that the user can provide a user name and password that are valid in a domain, and when the user logs on, this information is validated for the domain and the computer can access network resources If this validation does not occur, for whatever reason, the user cannot gain access to most network resources that are controlled by the domain controller The Windows NT–Based Logon Process When you start a Windows NT–based computer, the computer is a member of a domain, so it has a computer account Therefore, when the computer is started, it must authenticate with a domain controller After the user is authenticated by a domain controller, the user can provide a valid user name and password for the domain and authenticate with the domain controller Computers running Windows 2000 and Windows XP support logging on with cached credentials With cached credentials, if a user cannot authenticate with a domain controller, the user can be validated with previously used logon credentials and can access local resources Module 14: Troubleshooting Client Computer Startup and User Logon Problems 37 Logging On with Cached Credentials Topic Objective To illustrate the purpose of cached credentials Lead-in If you log on without being connected to the network, Windows 2000 recognizes that your credentials match previously used logon credentials Windows NT-based Domain Controller User User Logon Logon Computer Computer Logon Logon Cached Cached Credentials Credentials *****************************illegal for non-trainer use****************************** If you can log on to the domain by using the logon credentials that are located on the domain controller, access to user accounts at the selected domain has been successfully granted If you log on without being connected to the network, Windows 2000 recognizes that your credentials match previous successful logon credentials, and you receive the following message: “Windows cannot connect to a server to confirm your logon settings You have been logged on using previously stored account information.” To troubleshoot the problem, verify that the physical connection (network adapter and cables) and logical connection (transport protocol configuration) permits access to the domain controller When the problem is resolved, the cached credentials are sent to your Windows 2000 domain, and you are able to access network resources without providing a password again 38 Module 14: Troubleshooting Client Computer Startup and User Logon Problems Using the Netdiag Utility to Verify User Logon Topic Objective To identify some of the tests performed by the Netdiag utility ! Lead-in The Netdiag utility provides diagnostic information about the computer and its connectivity state When you run the Netdiag utility, it performs: # Adapter test # Default gateway test # DNS test # DC discovery test # LDAP test *****************************illegal for non-trainer use****************************** For computers running Windows 95 or Windows 98, you can verify that the user logon settings are configured correctly and use the ipconfig and ping utilities to verify Internet Protocol (IP) configuration and basic network connectivity You can then use the net use command to verify that the system can resolve a network basic input/output (NetBIOS) name to an IP address and establish communications Then, you can ask the user to attempt to log on to the system again You can use the Netdiag utility to verify logon and network connectivity The Netdiag utility provides diagnostic information about a computer and its connectivity state The Netdiag utility runs a series of tests on the computer The results of these tests can help you troubleshoot connectivity problems When you run the Netdiag utility, the tests that it performs include: ! Adapter test The Netdiag utility queries each network interface card (NIC) that the computer has configured If the query result indicates a disconnection, you should check the network cable ! Default gateway test The Netdiag utility tries to contact the default gateway If the default gateway cannot be reached, there may be a problem on the network If the domain controller is on the other side of the router, the domain controller will not be reachable either, and the user cannot be authenticated ! DNS test The Netdiag utility queries a DNS server If no DNS server can be reached, the computer cannot query the DNS server to find either the name or the IP address of a domain controller Module 14: Troubleshooting Client Computer Startup and User Logon Problems 39 ! DC discovery test The Netdiag utility tries to find a domain controller If no domain controller can be found, network authentication cannot take place ! LDAP test The Netdiag utility tries to submit a Lightweight Directory Access Protocol (LDAP) query to a domain controller A failure of the LDAP test when the domain controller could be contacted may indicate an Active Directory problem Note Install the Netdiag utility from the \support\tools folder on the Microsoft Windows 2000 Professional or Microsoft Windows Server compact disc 40 Module 14: Troubleshooting Client Computer Startup and User Logon Problems Lab B: Using the Netdiag Utility to Validate Logon Slide Objective To introduce the lab Lead-in In this lab, you will use the Netdiag utility to validate logon *****************************illegal for non-trainer use****************************** Objectives After completing this lab, you will be able to use the Netdiag utility Scenario You are a systems administrator for your company You have been managing users and groups and providing access permissions to network resources Now you are being asked to support end users and to support file and print servers in your area You must locate tools that you can use to better troubleshoot the end users’ problems Estimated time to complete this lab: 30 minutes Module 14: Troubleshooting Client Computer Startup and User Logon Problems 41 Lab Setup The Lab Setup section lists the tasks that you must perform before you begin the lab Tasks Detailed steps Log on as Administrator a Log on as Administrator with a password of password Install the Netdiag utility a In Windows Explorer, navigate to D:\Moc\2126\Labfiles\Lab14B, double-click Netdiag_Setup.exe, and accept the default settings b Close any open windows 42 Module 14: Troubleshooting Client Computer Startup and User Logon Problems Exercise Using the Netdiag Utility In this exercise, you will use the Netdiag utility to verify that a user is connected to the network and authenticated with a domain controller You will then disable your network interface card (NIC) and compare the information that is provided by the Netdiag utility Scenario You recently visited the Microsoft Web site and downloaded and installed the Netdiag utility You now want to use the tool in a test environment to determine what information the tool provides You determine that you must run the Netdiag utility while your system is operating properly, and then run the utility when not connected to the network so you can better use the tool when needed Tasks Open a command prompt, and start the Netdiag utility Detailed steps a Click Start, point to Programs, point to Accessories, and then click Command Prompt b At the command prompt, type ”D:\Program Files\Resource Kit\Netdiag.exe” and then press ENTER Using the information that is provided by the Netdiag utility, record the following information: Computer Name: List of installed hotfixes: Default Gateway Test: DNS Test: Disconnect your NIC cable a Disconnect your NIC cable Run the Netdiag utility a At the command prompt, type ”D:\Program Files\Resourcekit\Netdiag.exe” and then press ENTER Using the information that is provided by the Netdiag utility, record the following information: Computer Name: List of installed hotfixes: Default Gateway Test: DNS Test: Module 14: Troubleshooting Client Computer Startup and User Logon Problems 43 (continued) Tasks Detailed steps When might the Netdiag utility be of use? When a user has difficulty connecting to networked resources, the user can use the Netdiag utility to verify that the computer is connected to the network and operating properly Close any open windows, and then log off a Close any open windows, and then log off 44 Module 14: Troubleshooting Client Computer Startup and User Logon Problems Review Topic Objective To reinforce module objectives by reviewing key points Lead-in The review questions cover some of the key concepts taught in the module ! The Windows 9x-Based Boot Process ! The Windows NT-Based Boot Process ! Using Advanced Boot Options to Start the Computer ! Using the LastKnownGood Configuration to Start the Computer ! Using Recovery Console ! Troubleshooting the NT-Based Boot Process ! Troubleshooting the User Logon Process *****************************illegal for non-trainer use****************************** What are the primary steps in the Windows 98 startup process? The primary steps in the Windows 98 startup process are: Real mode startup, which means starting the computer in real mode Real mode configuration, which means processing Io.sys, which then configures the real-mode environment as required Protected mode load, which means switching from real mode to protected mode, and loading the virtual drivers that are required to operate Windows 98 During the Windows NT startup process, when is the startup considered complete? The startup process is not complete until the user logs on At that time, the files that support the Last Known Good configuration are updated What client operating systems not support safe mode? Only Windows NT operating systems not support safe mode Module 14: Troubleshooting Client Computer Startup and User Logon Problems 45 Your company maintains a centralized store of drivers for the client computers, which is accessed over the network You have loaded a video driver onto a client computer running Windows 98 When you restart the computer, the computer starts normally, but then it stops and shows only a blank screen This occurs every time you restart the computer You must start the computer and gain network access to load the correct video drivers onto the client computer How can you repair the configuration? During the startup, press F8 When the menu options appear, select Safe Mode with Networking complete will start the computer with basic VGA drivers and, at the same time, load network drivers How you install the Windows 2000 Recovery Console as a startup option? After starting Windows 2000, run \i386\winnt32.exe /cmdcons from the Microsoft Windows 2000 compact disc You want to edit the Boot.ini file on a Windows 2000 server, but cannot locate it What steps can you take to locate and edit the file? When Windows 2000 is installed, it creates Boot.ini in the root folder of the system partition as a read-only, hidden System text file To edit the Boot.ini file by using a text editor, the read-only option must be turned off so changes can be made Use Windows Explorer to make the file visible and change any necessary attributes Your computer is a Windows 2000 Professional workstation that is a member of an Active Directory–enabled Windows 2000 domain Your connection to the network is temporarily disabled You are nevertheless able to log on to the domain controller After some time, you discover that you are connected to the domain controller and are able to browse network resources How is this possible if the domain controller was not available when the client logged on? When the workstation cannot locate a domain controller, you are logged on by using cached credentials By using cached credentials, you can continue to work at your workstation without logging on locally While you are working, the network connection is restored Your workstation automatically locates the domain controller and authenticates without requiring you to log on again THIS PAGE INTENTIONALLY LEFT BLANK [...]... operating systems, press F8 during system startup Module 14: Troubleshooting Client Computer Startup and User Logon Problems 13 What Are the Advanced Startup Options? Topic Objective Option To identify the advanced startup options that are available for Windows client operating systems Lead-in There are a number of advance startup options that are available on client computers running Windows operating... or missing or corrupted files The Last Known Good configuration cannot resolve these problems Module 14: Troubleshooting Client Computer Startup and User Logon Problems 21 Lab A: Identifying Client Computer Startup Options Slide Objective To introduce the lab Lead-in In this lab, you will identify client computer startup options *****************************illegal for non-trainer use******************************.. .Module 14: Troubleshooting Client Computer Startup and User Logon Problems 7 " The Windows NT–Based Startup Process Slide Objective To identify the topics associated with the Windows 2000 startup process Lead-in ! Files Required by the Windows 2000 Startup Process ! The Windows 2000 Startup Process To troubleshoot the startup process on computers running a member of the... Debugging mode No No Yes Yes 16 Module 14: Troubleshooting Client Computer Startup and User Logon Problems When to Use Each Advanced Startup Option Topic Objective To identify when to use each advanced startup option Lead-in Logged (\Bootlog.txt) Enable Boot Logging Command prompt only Each advanced startup option has a specific use Safe mode command prompt only Safe Mode with Command Prompt ? Last Known Good... when the computer is restarted, and the Memory Management key, which controls creation of the paging files Win32 Subsystem Start When the Win32 subsystem starts, it automatically starts Winlogon.exe, which starts the Local Security Authority (Lsass.exe) and displays the CTRL+ALT+DEL logon dialog box 12 Module 14: Troubleshooting Client Computer Startup and User Logon Problems " Using Advanced Startup. .. the last time the system started and a user successfully logged on Last Know Good Configuration mode might be used when a new device or driver has been installed and loaded and the system does not start properly 2 Close any open windows, and then log off a Close any open windows, and then log off 30 Module 14: Troubleshooting Client Computer Startup and User Logon Problems " Using the Recovery Console... the Recovery Console, and only if advanced startup options cannot solve the problem To use the Recovery Console, you must have the skills to locate and identify problem files by using commands typed at a command prompt You must also know the administrator’s password to use the Recovery Console Module 14: Troubleshooting Client Computer Startup and User Logon Problems 31 Installing and Starting the Recovery... the hardware, and then returns the list of detected hardware to Ntldr Module 14: Troubleshooting Client Computer Startup and User Logon Problems 11 6 Loads Ntoskrnl.exe, Hal.dll, and System.dat 7 Scans System.dat and loads the device drivers that are configured to start at startup time 8 Starts Ntoskrnl.exe Load Phases When control is passed to Ntoskrnl.exe, Windows 2000 begins to load and initialize... Configuration Utility to show the startup options, perform the following steps: 1 Run Msconfig.exe 2 In the System Configuration Utility dialog box, on the General tab, click Diagnostic startup, and then click OK 3 Restart the computer Module 14: Troubleshooting Client Computer Startup and User Logon Problems 19 Using the Last Known Good Configuration to Start the Computer Topic Objective To illustrate... POST routine To troubleshoot the startup process on computers running the Windows NT family of operating systems, including Windows NT, Windows 2000, or Windows XP, you must understand the files that are required by the process and how the process proceeds 8 Module 14: Troubleshooting Client Computer Startup and User Logon Problems Files Required by the Windows 2000 Startup Process Slide Objective ... a computer ! Describe and troubleshoot the user logon process Module 14: Troubleshooting Client Computer Startup and User Logon Problems " The Startup Process for Clients Running Windows 95 and. .. troubleshoot user the logon process Module 14: Troubleshooting Client Computer Startup and User Logon Problems Overview Topic Objective To provide an overview of the module topics and objectives ! The Startup. .. Module 14: Troubleshooting Client Computer Startup and User Logon Problems After completing this module, you will be able to: ! Describe the Windows 95– and Windows 98–based startup process and