Subscribe to Windows IT Pro
July 17, 2001 12:00 AM

The Recovery Console

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

You can use the RC's Set command to display the current rules. Remember that you're working in an independent command processor, not a Win2K session's command window. Therefore, the Set command doesn't display the same information you're used to seeing when you use the command during a Windows session.

You can enable the Set command so that you can use it to reset the rules rather than simply display the current rules. I suggest that you give yourself this power on any computer on which you've preinstalled the RC. You need to take this step before trouble strikes because it requires that you change the computer's Group Policy—and the system must be operational for you to do so. After you enable the Set command to let you change the rules, you can change the rules at any time from within the RC.

In a Windows session, click Start, Run. In the Open box, type

mmc

to open a new Microsoft Management Console (MMC) console. In the Console1 dialog box, choose Console, Add/Remove Snap-in from the menu bar. Click Add to open an Add Standalone Snap-in dialog box. In that dialog box, select Group Policy and click Add. In the resulting Select Group Policy Object dialog box, choose Local Computer and click Finish. In the Add Standalone Snap-in dialog box, click Close. In the Add/Remove Snap-in dialog box, click OK.

In the console, expand the Local Computer Policy object and navigate to Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options. The right pane will display the local security policies. Double-click the policy Recovery Console: Allow floppy copy and access to all drives and folders. Select Enabled and click OK. Close and save the MMC console (you can then access the console from the Administrative Tools menu if you want to make changes later).

You can also set the policy to permit automatic administrative access to the RC, but doing so creates a computer that you could rename "a disaster waiting to happen." You might entrust this power to certain users on certain computers, but requiring a password instead of providing automatic access is safer.

Incidentally, if you or another administrator configure any policy for the domain, that configuration overrides any policy you set for the local computer. (Setting a domain policy for the RC would be unusual, however.)

After you change the security policy for the RC, you can change the rules when you're working in the RC. To do so, use the Set command with the following syntax:

set <rule> = <parameter>

For example, to allow access to all the directories on the computer, type

set AllowAllPaths = TRUE

A Genuine Must-Have
The RC is unbelievably useful for many reasons. First, this built-in tool replaces the third-party utilities that we needed to buy and learn to use to repair previous versions of Windows.

Second, the RC provides access to the original CD-ROM's system files. This access can help you overcome system corruption. Third, the tool's ability to repair the Master Boot Record (MBR) can help you rescue your system from viruses. You won't need to prepare special boot disks for NTFS systems.

Fourth, the ability to stop and start services gives the RC far more power than any other built-in Windows repair tool. In short, the RC is an administrative necessity.

Related Content:

ARTICLE TOOLS

Comments
  • Jerome Glass
    10 years ago
    Jan 18, 2002




    Deceptive Fixmbr Error Message


    I used the information in Kathy Ivens's Getting Started with Windows 2000: "The Recovery Console" (August 2001, InstantDoc ID 21538) to install the Recovery Console (RC) on our file and print servers and on my own workstation. I made all the Group Policy changes that the article recommended. Two days later, my computer wouldn't boot into Windows. Outside consultants told me they suspected a problem with the Master Boot Record (MBR)--possibly a virus. They told me to boot into the RC and use the fixmbr command. I received an error message telling me that I seemed to have an invalid boot record and that using this command might destroy my computer. I ended up reinstalling Win2K Professional. Is there an RC command that will fix an invalid boot record?


    Jerome Glass



    My Microsoft RC expert tells me that you could have safely ignored the message. Apparently, the message always appears, and it's deceiving. He wouldn't call this situation a bug, but I have no problem labeling it with that term! The Microsoft article "Error Message When You Run fixmbr Command" (http://support.microsoft
    .com/default.aspx?scid=kb;en-us;
    q266745) addresses the problem.


    Kathy Ivens

  • Ron Weekley
    11 years ago
    Nov 01, 2001

    My Win2000 Adv Server CD does not contain a i386\\winnt32 folder. Is this only for Win2000 Pro users? The help feature on my Win2000 Adv Server also refers to this non-existent folder, but also makes a reference to Win2000 Pro. What did I miss?

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

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