There are a lot of posts about PXE boot, but I can't find the common thread to tie them all together.  My test machines cannot PXE boot.
My lab environment is very simple:

10.10.0.0/24 subnet

10.10.0.10 = W2k8 R2 DC, DHCP, DNS

10.10.0.11 = SCCM2012 (on W2k8R2 with SQL Server 2008 SP3 and CU4)

All machines are Hyper-V virtual machines connecting through the same virtual network.

Setup the PXE service from DP properties.  I let SCCM install WDS.  WDS in Server Manager does not have a server node, but the WDS service is running.  DP PXE tab is configured as follows:
"Enable PXE support for clients" is checked
"Allow this distribution point to resond to incoming PXE requests" is checked
"Enable unknown computer support" is checked
"Require a password when computers use PXE" is not checked
"User device affinity" is set to "Allow user device affinity with automatic approval"
PXE is configured to respond on all network interfaces
The PXE server response delay is 0 seconds

The DHCP server has options configured as follows:
Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com

Both DP and MP on SCCM server are configured for HTTP.

Both x86 and x64 boot images have been distributed to DP.  The media was updated after PXE was enabled on the DP.

Both x86 and x64 boot images have "Deploy this image from the PXE service point" enabled on the Data Source tab of their properties.

I have tried both unknown computer task sequence and a computer import task sequence (old computer association).  They all end in abortpxe.com

Complete PXE response is as follows:

=================================================================

PXE Network Boot 03.23.2009
(C) Copyright 2009 Microsoft Corporation, All Rights Reserved

CLIENT MAC ADDR: 00 DD CC BB AA 00  GUID: 532D27E3-A184-4D27-A822-30A8B6F4A39D
CLIENT IP: 10.10.0.106    MASK: 255.255.255.0    DHCP IP: 10.10.0.10
GATEWAY IP: 10.10.0.5

Download WDSNBP...

Architecture: x64
WDSNBP started using DHCP Referral.
Contacting Server: 10.10.0.11 (Gateway: 0.0.0.0)

The detalis below show the information relating to the PXE boot request for
this computer.  Please provide these details to your Windows Deployment Services
Administrator so that this request can be approved.

Pending Request ID: 6

Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com

PXE Boot aborted.  Booting to next device

=========================================================== 

From the smspxe.log:

]LOG]!><time="16:31:39.445+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: {C9929C4D-735A-4973-8659-4D3D5D5E4F92}]LOG]!><time="16:31:39.445+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6428">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:31:39.480+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:31:39.505+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:31:39.505+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:31:39.533+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:31:39.553+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:32:00.963+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:01.008+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:01.027+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.027+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.084+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="16:32:01.108+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: {C9929C4D-735A-4973-8659-4D3D5D5E4F92}]LOG]!><time="16:32:01.108+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6428">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:01.151+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:01.174+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.174+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.209+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:32:05.230+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:05.290+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:05.325+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:05.325+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:05.366+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>

=============================================================================================

I've been hammering this for about 10 hours now (or to be honest, it's been hammering me) and it must be something very simple I'm missing.  I have a feeling that I'm doing something I used to do in 2007 and whatever that is, it does not work in 2012.

If I connect using boot media, Task Sequences execute perfectly.

TIA,

Tom

Why are you using DHCP scope options? They are not required for PXE booting in the same subnet and are generally discouraged in favor of iphelpers anyway.

And, you have them configured wrong: http://technet.microsoft.com/en-us/library/c169579c-c0fc-4ec6-aa8d-0af5504fda01 and http://www.windowsitpro.com/article/dhcp2/configuring-dhcp-and-wds

Hi Jason,

Thank you for your response.  There are dozens of unanswered threads on this topic. I know, I've looked at all of them today.  You've told me what I should not do, the question is what should I do?  The PXE boot did not work at all until I configured options 66 and 67 on the DHCP server.  Until that time I received "PXE E53 - No boot filename received."  I appreciate your help, how do I move forward?

Thanks,

Tom 

Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com
[...]
Pending Request ID: 6

Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com

PXE Boot aborted.  Booting to next device

<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>

Hi Torsten,

Thanks for your input.  I will look for the resource ID today and post an update tonight in my "spare" time.\

Tom

Hi Torsten,

Your suggestion was spot-on.  I found an "unknown computer" resource buried from a couple of failed deployment attempts ago. 

Thanks!

Tom

I do not like how they are now making you look into the SMSPXE.log to find this non-descriptive line.  In 2007, you could look under site status/Component status and look at the pxe service point log that told you very plainly that it instructed the device to boot normally since no advertisements were found.  What hapened to this level of detail!  glad I found this post or I could have been chasing nothing for hours.

LvilleSystemsJockey

Had a same issue. Found that computer is known to SCCM. Deleted the computer from SCCM console.

PXE boot worked like charm !

Thank you

Cheers!

Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com
[...]
Pending Request ID: 6

Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com

PXE Boot aborted.  Booting to next device

<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>

Those options are fine when using DHCP options. They must be configured right because ConfigMgr does send a reply to the client ("abortpxe"). It basically tells you that ConfigMgr knows the MAC address and/or SMBIOSGUID of the client, but cannot find a deployment for it.
Just find ResourceID 16777218 in the console (you might have to add the ResourceID column) and double check if there's an deployment available (properties of the client with resourceID 16777218).