hi Trevor are you sure you arn't seeing anything on the black PXE boot screen just before this error ? that error looks suspiciously like something generated from the recovery partition or a bde config gone bad (i.e. your hard drive).
On Mon, Sep 30, 2013 at 7:53 PM, Trevor Sullivan <[email protected]> wrote: > Niall,**** > > ** ** > > I’m not quite sure what you mean. We are attempting to PXE boot, not boot > to the hard drive. The only error I’m seeing at this point is the one in > the original e-mail.**** > > ** ** > > Cheers,**** > > Trevor Sullivan**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Niall Brady > *Sent:* Monday, September 30, 2013 12:53 PM > *To:* [email protected] > *Subject:* Re: [mssms] ConfigMgr 2012 SP1 CU3: PXE Boot: 0xc000000f**** > > ** ** > > What error do you see before it tries booting from the hdd > > Sent from my phone, please excuse any typo's as a result.**** > > ** ** > > > On 30 sep 2013, at 15:28, "Trevor Sullivan" <[email protected]> wrote:**** > > Hey folks,**** > > **** > > I’ve got a ConfigMgr 2012 Service Pack 1 Cumulative Update 3 Primary Site > running on Windows Server 2008 R2 Service Pack 1 that I’m trying to PXE > boot a non-UEFI (Dell Latitude E6520) client from. When I attempt to PXE > boot the client, I receive a 0xc000000f error with the text “The Boot > Configuration Data for your PC is missing or contains errors.” The > Distribution Point for this location is on the same server as the Primary > Site.**** > > **** > > I’ve used Wireshark to capture and validate the DHCP options that are > configured, and I am waiting to find out from the network team if there is > an IP helper configured for this VLAN.**** > > **** > > DHCP Option 66 (TFTP Server Name) = <*IP Address of PXE-Enabled > Distribution Point*>**** > > DHCP Option 67 (Bootfile name) = SMSBoot\x86\wdsnbp.com**** > > **** > > <image001.png>**** > > **** > > When I initially reviewed the infrastructure, it had the Windows 8.1 ADK > Preview installed. I reverted it back to Windows 8.0 ADK, and imported > fresh WinPE 4.0 boot images. Additionally, I removed Windows Deployment > Services (WDS) from the Distribution Point, deleted the RemoteInstall$folder, > re-installed WDS, and re-distributed the new boot images. > **** > > **** > > We’re able to successfully build a USB flash drive (UFD) or ISO image as > bootable media, so I know that the boot images themselves are working > perfectly.**** > > **** > > Does anyone know what might cause the error above?**** > > **** > > Cheers,**** > > Trevor Sullivan**** > > ** ** > > ** ** > >
