J
Jack Wishbone
I have a Windows Server 2003 Standard R1 SP2 machine that I've setup with
hopes to utilize Windows Deployment Services to push XP Pro images to aging
lab desktop machines. I have recently become a sysadmin, and thus, I have
no desire to rebuilt a desktop every again.
I'm at the stage of the WDS process where I need to grab a sysprep'd image
from a workstation. During the process of booting from the "Vista PE"
environment from the server via PXE, my workstation crashes with:
Windows failed to start...
File: \WINDOWS\system32\ntoskrnl.exe
Status: 0xc0000221
Info: Windows failed to load because the kernel is missing or corrupt.
I was under the impression that the PE environment was loading from the
server. Does this error message mean that the kernel within my "Boot
Images" on the WDS server is corrupt? Or is it looking at my workstation's
hard disk and finding an incompatible kernel?
hopes to utilize Windows Deployment Services to push XP Pro images to aging
lab desktop machines. I have recently become a sysadmin, and thus, I have
no desire to rebuilt a desktop every again.
I'm at the stage of the WDS process where I need to grab a sysprep'd image
from a workstation. During the process of booting from the "Vista PE"
environment from the server via PXE, my workstation crashes with:
Windows failed to start...
File: \WINDOWS\system32\ntoskrnl.exe
Status: 0xc0000221
Info: Windows failed to load because the kernel is missing or corrupt.
I was under the impression that the PE environment was loading from the
server. Does this error message mean that the kernel within my "Boot
Images" on the WDS server is corrupt? Or is it looking at my workstation's
hard disk and finding an incompatible kernel?