Failed PXE boot on new computer. Can someone take a look at this log and tell me why it failed?

https://skydrive.live.com/#cid=D9560DD121B6BF0F&id=D9560DD121B6BF0F%21138

Failed to resolve the source for SMS PKGID=P010006B, hr=0x80070002

Failed to run the action: Use Toolkit Package. 
The system cannot find the file specified. (Error: 80070002; Source: Windows)

Check the above package and make sure its been distributed to the DP.

Thanks for your reply.

I have verified the packages exist on the secondary pxe server via content status from the parent site server. That site is 100% green.

Could it be a missing network driver then?

It looks like you are talking to the network fine.  It was able to copy files etc....

Do you have a cas.log and DataTransferService.log

files have been uploaded

https://skydrive.live.com/?cid=D9560DD121B6BF0F&id=D9560DD121B6BF0F%21138

yes the client can nslookup the Primary Site Server

c:\windows\ccmcache has been cleared, I will have him try again

CLibSMSMessageWinHttpTransport::Send: URL: CGD2SC12.cgi.int:80  CCM_POST /ccm_system/request    TSManager    27.06.2013 18:03:36    1852 (0x073C)
Error. Received 0x80072ee7 from WinHttpSendRequest.    TSManager    27.06.2013 18:03:36    1852 (0x073C)
unknown host (gethostbyname failed)    TSManager    27.06.2013 18:03:36    1852 (0x073C)

Has the client got an IP address? Can it reach the MP?

yes it gets an IP address and access MP.

failed again, here is an updates smsts.log

https://skydrive.live.com/#cid=D9560DD121B6BF0F&id=D9560DD121B6BF0F%21138

Try to ping the server using FQDN.

For some reason it turned out to be a problem with the registered DNS names on the SCCM server acting as MP.

The solution was simply to run Ipconfig /registerdns on the server. 

Make sure proper permission for Network access acount

But:

unknown host (gethostbyname failed) still persists.

In the Network Settings Step, do you have configured something Special there?

I find
"Unable to find Win32_NetworkAdapter where MACAddress = "60:a4:4c:64:a4:69""

in your log.

nope, it can't ping "anything" so how did it get those files and an IP address?

think I'm going to try and embed the nic driver it wants

The client does get a valid IP address, the MAC above belongs to the client.

It failed again, I have uploaded more info.

https://skydrive.live.com/#cid=D9560DD121B6BF0F&id=D9560DD121B6BF0F%21138

We need to make sure it take IP agian after windows pe start

Enable command line support within your boot images

1. Go to the properties of your boot image(s) <Right click | Properties)
2. Go to the Windows PE tab and tick the Enable command support (testing only) option
3. When prompted, click on yes to update your distribution points
4. From within your boot image (Windows PE) environment, you can now pres F8 to open up a command window very useful for troubleshooting

After the windows pe start -- press F8 and Ipconfig and try to ping SCCM Server FQDN

update

I embeded the drivers into the PE and now it boots and gets farther but new error:

PXE has failed with error code (0x800700A1)

Note: We successfully deployed 4 other PXE images this morning so its definitly something with this unit. I was told they replaced the mother board, deleted from AD and SCCM a couple days ago.

also found this in the smspxe.log

60:A4:4C:64:A4:69, 26F85F15-3649-2954-05B4-60A44C64A469: found optional advertisement P012001B

P01 is the correct prefix but I can't find any advertisement for 2001B, strange???

So, when you are using the onboard nic, it might possible, that the Client with the new MAC address 60:A4:4C:64:A4:69 is recongnized as unknown Computer. Do you have set a deployment on the unknown Computer collection?

And have you chekced, if your old Computer object has the correct MAC Address?

Weird. It's working now.<o:p></o:p>