I remember that if you have a different boot image on the boot media as the one assigned to the TS then the TS will try to download the boot WIM from SCCM. This was where you would see the message, Ready to Start - Eject CD and click Finish to continue (or similar).
Do you have the same boot image assigned to the PXE DP as the TS? As much a stab in the dark as anything, I'm still reeling from the MMS news. :( Von: [email protected] [mailto:[email protected]] Im Auftrag von Stuart Watret Gesendet: Dienstag, 1. Oktober 2013 16:43 An: [email protected] Betreff: RE: [mssms] ConfigMgr 2012 SP1 CU3: PXE Boot: 0xc000000f what happens if you use the same boot image as bootable media instead? I did see that error when we first trialled Win8 via MDT and it was because I had hijacked an old TS instead of creating a new one. Stuart Watret Offshore - IT Ltd ________________________________ From: [email protected] [[email protected]] on behalf of Niall Brady [[email protected]] Sent: 01 October 2013 06:50 To: [email protected] Subject: Re: [mssms] ConfigMgr 2012 SP1 CU3: PXE Boot: 0xc000000f hi Trevor a few things to check, try diskparting that computer and cleaning the disk thereby removing anything that's on it (like broken bcd entries etc) once done, pxe boot again, do you see the same message ? secondly, check the SMSPXE.log file on the server hosting the distribution point role, search for the MAC address of the computer you are PXE booting, does it reveal anything interesting ? lastly verify that you've enabled PXE on the boot image, the task sequence, and the dp itself and that the computer is in a collection targeted with a deployment. On Tue, Oct 1, 2013 at 3:28 AM, Jason Wallace <[email protected]<mailto:[email protected]>> wrote: Does this show on all systems? As in if you build a VM from scratch? On 1 Oct 2013, at 03:19, "Trevor Sullivan" <[email protected]<mailto:[email protected]>> wrote: Niall, We ran through a PXE boot again (a couple times) and didn't see anything just prior to the error I posted earlier. Cheers, Trevor Sullivan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Niall Brady Sent: Monday, September 30, 2013 2:36 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] ConfigMgr 2012 SP1 CU3: PXE Boot: 0xc000000f 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]<mailto:[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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Niall Brady Sent: Monday, September 30, 2013 12:53 PM To: [email protected]<mailto:[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]<mailto:[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<http://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
