Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

September 27, 1999 12:00 AM

The Windows 2000 Recovery Console

Windows IT Pro
InstantDoc ID #7250
Rating: (0)

There are a lot of administrators who risk security on Windows NT servers by configuring their system partitions with FAT. Why? Although they keep their data on NTFS partitions, the FAT partition gives them a DOS prompt that lets them copy or delete files, update DLLs manually, and even copy Emergency Repair Disk (ERD) information to the appropriate directory to fix NT problems. These administrators will be glad to know that Windows 2000 (Win2K) eliminates the need to maintain a FAT partition. They can now tackle most of the chores they accomplished at the DOS prompt with the Win2K Recovery Console on domain controllers. In fact, administrators can now perform some tasks at the Recovery Console that they couldn’t do at the DOS prompt without third-party tools or Windows NT Server 4.0 Resource Kit utilities.

The Recovery Console offers a command-line console that lets administrators perform various administrative tasks. You can read or write files to FAT or NTFS partitions, format local hard disk drives, fix master boot records, and stop or start services.

You must install the Recovery Console on your system manually after you install Win2K. Go to the location of your Win2K source files and, at the command prompt, type winnt32.exe /cmdcons. You can also start the Recovery Console from your Win2K setup disks or CD-ROM. Running the /cmdcons switch takes you through a process that seems similar to installing Win2K on your computer, but actually ends quickly after copying certain files to your system. You are prompted to continue installation, as Screen 1 shows. After the files copy over, which requires about 7MB of disk space, you will see a completion notice (see Screen 2). Restart your system to finish the installation and get to the Recovery Console.

After the restart, select Windows 2000 Recovery Console from the Win2K boot menu option screen and select an installation number. If you have multiple Win2K installations on the same system, you can choose to repair different instances of Win2K. If you have only one, type 1 to select the only available option. Next, you have to supply an Administrator password, as Screen 3 shows, which is the Directory Services Restore Mode Administrator Password you entered when you installed Active Directory (AD) and made your machine a domain controller. At this point, you’re ready to use the console. The sidebar "Recovery Console Commands" provides a listing of all available commands, which you can access by typing HELP in the console. To get help for a specific command, use the syntax "HELP command name" (e.g., HELP FIXBOOT) or "command name /?" (e.g., LISTSVC /?).

There are some limitations to what you can do with the Recovery Console. The information in this column pertains to the latest Win2K release (RC2 build 2128). Based on the tests I performed, you can copy files from a floppy disk to a hard disk, but not the other way around. You can create directories only in the systemroot directory (e.g., \WINNT) and not at the root level (e.g., C:\). Also, you can copy files only to the systemroot directory and the root directory. The copy command doesn’t support the wildcard characters, so you can copy only one file at a time.

To remove the Recovery Console from your system (not something you typically want to do), you need to reveal protected OS files by clicking My Computer, Tools, Folder Options, View, Show hidden files and folders. You also need to delete the cmdcons folder at the root directory, delete cmldr file, and delete the reference to the Recovery Console in the boot.ini file.

The Recovery Console is a great tool for administrators. I’m sure most of us will want it to do more, and future service packs might give us additional commands. Perhaps we’ll get a GUI some day—naah!

Related Content:

ARTICLE TOOLS

Comments
  • Brian Alaway
    10 years ago
    Mar 15, 2002

    How can I install the Recovery Console in unattended mode using a bootable CD. I'm aware of the [GuiRunOnce]option but I haven't been able to get it to work with the bootable CD option. It seems that winnt32.exe must have access to the entire i386 directory to install the Recovery Console. Since only the C drive is partitioned and fomatted during the initial install I'd rather not copy the entire i386 directory to C just to give winnt32 acess to the necessary setup files for the RC. Is there a list somewhere of the exact files that winnt32 needs in order to install the Recovery Console. Or am I off base here in my assumptions and approach? Thanks.

  • Mauricio
    12 years ago
    Aug 01, 2000

    A good point to Microsoft Windows 2000.

  • Paul Willy
    13 years ago
    Oct 08, 1999

    Great article, and it's about time we get a faster tool than the stupid emergency repair. You did not mention that the most important source of uncorupted registry files, RDISK.EXE has been removed from W2k. Has anyone found a replacement?

  • Don Michelli
    13 years ago
    Sep 28, 1999

    Any idea if the recovery console can be loaded under NT 4.0? (similiar to how the ms-installer service can be used)

  • Brad Karal
    13 years ago
    Sep 28, 1999

    This is very useful information. I was considering purchasing ERD Commander for command-line based disaster recovery work, but I will reconsider seriously now.

    Brad Karal

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.