Recovery Console That You Create from a Sysprep Image Does Not Work (296251)

The information in this article applies to:

Microsoft Windows 2000 Professional SP2
Microsoft Windows 2000 Professional SP1

This article was previously published under Q296251

SYMPTOMS

When you create a Sysprep image from a computer on which you have installed the recovery console, and then load that image onto another computer, the recovery console on the new computer may not work until you re-install it.

CAUSE

When you install the recovery console, it creates a Bootsect.dat file that is unique to each computer based on the dynamics of the computer's hard disk. When the recovery console starts a computer, it does not use Ntldr; therefore the standard boot sector is not used. Instead, the recovery console uses a virtual boot sector which is specified in Bootsect.dat

MORE INFORMATION

You can install the recovery console during an unattended installation of a Sysprep image by using the winnt32 /cmdcons /unattend command. To install the recovery console during the unattended installation of Windows, you must use the [GuiRunOnce] section of the Unattend.txt file:

Command1="path\winnt32 /cmdcons /unattend"

For more information about how to use the Unattend.txt file, see the Deployment Planning Guide of the Windows 2000 Server Resource Kit.

Modification Type:	Major	Last Reviewed:	9/22/2003
Keywords:	kbPerformance kbprb w2000perf KB296251