Backup/Recovery - Using Last Known Good Configuration To Restore an NT System

SignalQ Sites:
NetAdminTools - Coprolite - NoNIC - SpotBridge - NAW
RoboCoop - AreWeDown - SolarPower - SysAdminTools
Xfig - Gold Loaf - GeekPapa - FixGMC - MCJ - FixRambler

Categories:
·GNU/Linux
·Homebrew designs
·Perl
·Administration
·Backup/Recovery
·Bugs/Fixes
·Certification
·Database
·Email
·File/Print
·Hardware
·Information Grab Bag
·Interoperability
·GNU/Linux ABCs
·Monitoring
·Name Resolution
·Network Services
·Networking
·Remote Control
·Security
·Desktop
·Web
·BSD
·Solaris
·GIAGD
·REALbasic
·All Categories

Using Last Known Good Configuration To Restore an NT System
Topic: Backup/Recovery Posted:2003-07-27
Printer Friendly:

In this article we used the Windows 2000 recovery console to fix the filesystem on an NT server. Let's use the recovery console to make a BSOD. We'll just disable a required boot service:

Let's reboot:

Nice!! That is what we wanted. Now, we could boot again and fix with the recovery console:

That works to recover from our shenanigans, but this is an article about Last Known Good Configuration. When NT boots you will see this screen:

Push the space bar:

Select L to load the Last Known Good Configuration, then push enter. NT boots fine now, using the settings from before we messed with our SCSI driver. Last Known Good Configuration gets loaded after the system boots completely, so you can always go back unless you have overwritten some system files.

Please read our Terms of Use
Microsoft, Windows, Windows XP, Windows 2003, Windows 2000, and NT are either trademarks or registered trademarks of Microsoft Corporation. NetAdminTools.com is not affiliated with Microsoft Corporation. Linux is a registered trademark of Linus Torvalds, and refers to the Linux kernel. The operating system of most distributions that contain the Linux kernel is GNU/Linux. All logos and trademarks in this site are property of their respective owner. Copyright 1997-2008 NetAdminTools.com

Created by:

MCJ CMS