Windows server 2003 recovery cd

When the installation completes, you will see a message indicating that installation of the Recovery Console has been successful. Now that you know how to install the Recovery Console, you can access it by rebooting the system and selecting the Microsoft Windows Recovery Console option from the boot menu. When you do, Windows will give you the opportunity to press [F6] if you need to load a third-party driver for your SCSI controller.

If you don't press [F6], the Recovery console will continue to boot. After a few seconds, you will see a screen asking you which Windows installation you would like to log into. Normally, there will only be one choice, but if your server happens to have multiple operating systems installed, you can select which operating system you want to work with.

The reason why this is possible is because the Recovery Console isn't version specific. It simply tries to detect any Windows installation that might exist on your hard disk. Select the installation that you wish to repair and press [Enter].

Windows will now prompt you for the Administrator's password. Keep in mind that Windows is asking for the password for the Administrator's account, not the password for someone who happens to be a member of the Administrators group. At this point, you might be curious to do a little looking around and see exactly what you can access.

One of the first things that you might notice is that the CD command Change Directory behaves strangely. By default, the CD command is restricted to allow you to move deeper into the directory structure, but not to let you backtrack. I have absolutely no idea what Microsoft's reasoning was behind this. What makes the restrictions on the CD command even stranger is the fact that Microsoft included a comparable command with fewer restrictions.

First, any time that you use CHDIR, or any other command, to access a file or folder with a long file name multiple words such as Program Files , the file or folder name must be placed in quotation marks. This leads me to the other quirk that you need to know about. It might seem strange not to have access to the entire system being that you are the Administrator, but as I explained earlier, Microsoft has seriously restricted access as a safety feature to protect your data in the event that you have to let someone else work on your server.

By default, there are only four things that you are allowed to access from the Recovery Console. These include:. There are also some other restrictions placed on the Recovery console as well. EXE , then all files in the current directory with the. EXE extension would be deleted. In the Recovery Console though, the asterisk does not act as a wild card. This is a safety feature to prevent you from accidentally deleting, renaming, or modifying multiple files.

As I will show you later though, there is a way to get wild card functionality back. Another way that the Recovery Console protects Windows is by controlling access to removable media.

Remember, removable media is one of the four things that the Recovery Console gives you access to. However, the default access level to the removable media is read only.

This prevents a consultant from copying pieces of your server's registry to a floppy in an effort to later use the stolen information to crack passwords. Again, the restrictions on removable media can be circumvented through a technique that I will show you later.

The final security measure that the Recovery Console uses to protect you from yourself is copy protection. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No.

Any additional feedback? Note Only the Administrator account can obtain access to Recovery Console. Note Recovery Console uses the Administrator password that you configured when you installed Windows Server Note The copy command in Recovery Console does not support wildcard characters. In this article. In any case, the system starts to book OK, certainly beyond that point which I would say that either of the errors that would be fixed by running these command you be useful.

Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Windows Server General Forum. Sign in to vote. Hi all, I had a failure on a Windows SBS server this morning after shutting down fine down last night.

Tried running some diagnostics on the disk - they all appear fine It seem as though maybe some registry or security system is hosed The only saving grace is that I have a relatively recent copy of the entire system 2 weeks ago on a spare disk.

Ideas welcome. Chris Chris. Saturday, November 5, PM. If the Windows CD displays the What would you like to do? Turn off your computer, wait ten seconds, and then turn your computer back on.