This is our ARCHIVE site. This site contains content that was on our community site "amset.info" and is no longer maintained. However as there are large numbers of links to the content on the internet, it has been retained on this site so that people who find that information of use, can still access it. However it cannot be guaranteed to be up to date, or accurate, particularly with regards to modern best practises. Most of the content was originally written between 1998 and 2008.

Image watermarks refer to the old url of amset.info, which is another domain under control of Sembee Ltd.

Our Exchange Server related content can be found at http://exchange.sembee.info/ and is actively maintained. Other sites from Sembee include: dosprompt.info - loginscripts.info - office-recovery.com - wuauclt.info - statuspages.co.uk

Windows

Windows 2000 XP and Server 2003 Recovery Console

In Windows 98 you had the option to boot in to a command prompt (DOS) window to troubleshoot and fix a system. This capability is not available in Windows 2000/XP/2003 natively. However Microsoft have an optional component which you can install on your machine called the Recovery Console. This has been removed from Windows Vista and later versions (including Windows 2008 and higher) - see more information from Microsoft here.

The recovery console is also available from the CD, if you boot from the disk then you will get the option to use the Recovery Console. However it is much more convenient to have it already installed on the system - especially if access to a installation CD could be difficult.

To install, you will need an installation CD-ROM for your operating system, or a copy of the i386 stored locally or on your network.

1. Put the CD in to your drive.
2. Click Start, Run.
3. Enter the following command
   32 bit Windows:"x:\i386\winnt32.exe /cmdcons"
   64 bit Windows: "x:\AMD64\winnt32.exe /cmdcons" 
   Where x is the drive letter for your CD-ROM drive. Adjust this path if you are using a network location.
4. Follow the prompts.

It is best to be connected to the Internet when installing the console as the application will connect to Microsoft's web site to get the latest files.

Note: If you have installed a service pack on to your machine, then you need to use an installation point that contains the service pack. Windows 2003 64 bit edition will give you an error message if the source installation files do not have the service pack but the destination server does.

Reducing the Boot Menu Countdown

Once the console is installed, a boot menu will show for 30 seconds. You can remove this or cut the time down by editing your start up options.

1. Right click on "My Computer" and choose properties.
2. Click on the "Advanced" tab.
3. Then click on the "Startup and Recovery" (Windows 2000) or the "Settings" button under "Startup And Recovery" (Windows XP / Server 2003)
4. Adjust the display time settings as required.

Changing Access Permissions

After installing the recovery console you should use the Group Policy editor to change the access settings so that you can copy files to a floppy disk in the event of a problem. This setting needs to be changed before you have to use the recovery console.
The setting you need to change is to enable the following:

Computer Configuration, Windows Settings, Security Settings, Security Options, Recovery Console, Allow Floppy Copy and Access to all drives and folders.

This setting can either be made via the local policy, or if you are a domain administrator, make the change in your Domain Group Policy so that it applies to all machines with the recovery console installed.

Automatic Logon to Recovery Console

You can also configure the recovery console to automatically logon. This is by modifying two registry keys.
You should be aware of the security implications of this. The recovery console can be used to bypass any security on your machine, so if you automatically login, then your security is useless.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole

Modify the keys "Security Level" and "Set Command" from 0 to 1. After pressing OK, the value will be 0x00000001 (1)

Removing the Recovery Console

Removing the recovery console is a little more involved.

1. In Windows Explorer, verify that you can see hidden files and folders as as protected operating system files.
   ("Tools", "Folder Options", on the "View" tab select "Show hidden files and folders". "Hide protected operating system files" should be unselected - acknowledge the message you get when clearing this option.)
2. Select the drive that the recovered console is installed on and delete the "Cmdcons" folder and the "Cmldr" file.
3. Still in Windows Explorer, right click on "boot.ini" and choose Properties.
4. Unselect the "Read-only" option.
5. Open "boot.ini" in Notepad (double clicking on the file will usually open it, otherwise open a new notepad session and drag and drop)
6. Find and delete the line
   Windows 2000: "C:\cmdcons\bootsect.dat="Microsoft Windows 2000 Recovery Console" /cmdcons".
   Windows XP/2003 Server: "C:\cmcons\bootsect.dat="Microsoft Windows Recovery Console" /cmdcons"
7. Save the file, overwriting the existing "boot.ini" file, then close notepad.
8. In Windows Explorer, right-click on "boot.ini" again and choose Properties
9. Enable "Read-only" again and then close the dialogue box.

More Information

Microsoft have a number of Knowledge base articles on using the Recovery Console.

Windows 2003: http://support.microsoft.com/default.aspx?kbid=326215
Windows XP: http://support.microsoft.com/default.aspx?kbid=307654
Windows 2000: http://support.microsoft.com/default.aspx?kbid=216417

There are no equivalent articles for Windows Vista/Windows 2008 and higher.

If you are installing the recovery console on to a domain controller, then you may want to read this article from Microsoft about resetting the password. http://support.microsoft.com/default.aspx?kbid=239803

If you get an error message about "The Password Is Not Valid" when you try to login to the Recovery Console, then you should look at this article from Microsoft on resolving the problem: http://support.microsoft.com/default.aspx?kbid=308402