I get this everytime I try to PXE a UEFI device.  I have even moved my PXE to server 2012.  Changed to IP helpers.

Windows failed to start.  A recent hardware or software change might be the cause.  To fix it... <blahblah>

File:\Windows\System32\boot\winload.efi

Status: 0xc0000359

Any ideas?

Thanks,

Jason

Hi Jason

Can you post your smspxe.log?

Thomas,

Yes, I can do you need just the client boot action reply string?  It is a big log.

Thanks,

Jason

Here it is...

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
 SMSPXE 1/13/2014 12:28:09 PM 732 (0x02DC)
78:45:C4:C6:B1:74, 4C4C4544-0037-5210-8047-C7C04F525431: device is not in the database. SMSPXE 1/13/2014 12:28:09 PM 732 (0x02DC)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 1/13/2014 12:28:09 PM 732 (0x02DC)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>8f2e8c16-543f-4204-a65a-701cc4c40f3f</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BSD200F7" OfferIDTime="1/9/2014 1:11:00 PM" PkgID="BSD000AB" PackageVersion="" PackagePath="http://sccm-dp04.HIDDEN/SMS_DP_SMSPKG$/BSD00001" BootImageID="BSD00001" Mandatory="0"/></ClientIDReply>
 SMSPXE 1/13/2014 12:28:09 PM 732 (0x02DC)
78:45:C4:C6:B1:74, 4C4C4544-0037-5210-8047-C7C04F525431: found optional advertisement BSD200F7 SMSPXE 1/13/2014 12:28:09 PM 732 (0x02DC)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 1/13/2014 12:28:12 PM 732 (0x02DC)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>8f2e8c16-543f-4204-a65a-701cc4c40f3f</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="BSD200F7" OfferIDTime="1/9/2014 1:11:00 PM" PkgID="BSD000AB" PackageVersion="" PackagePath="http://sccm-dp04.HIDDEEN/SMS_DP_SMSPKG$/BSD00001" BootImageID="BSD00001" Mandatory="0"/></ClientIDReply>
 SMSPXE 1/13/2014 12:28:13 PM 732 (0x02DC)
78:45:C4:C6:B1:74, 4C4C4544-0037-5210-8047-C7C04F525431: found optional advertisement BSD200F7 SMSPXE 1/13/2014 12:28:13 PM 732 (0x02DC)
Looking for bootImage BSD00001 SMSPXE 1/13/2014 12:28:13 PM 732 (0x02DC)
Looking for bootImage BSD00001 SMSPXE 1/13/2014 12:28:16 PM 732 (0x02DC)
Looking for bootImage BSD00001 SMSPXE 1/13/2014 12:28:16 PM 732 (0x02DC)

BSD000001 is the x86 but why would it choose that when x64 is there?  I am using ip helpers with no DHCP options.

Jason

What bootimage is used on the task sequence you intend to run? As said, 64bit is required for UEFI devices :) iphelpers has no impact on which bootimage is chosen.

I have 2 uefi devices and they are both still picking the BSD00001 which is the x86.  This is the beginning of the PXE boot process so I have not chosen a Task Sequence yet.

Does it choose the boot file for the above optional advertisement bsd200f7? 

Thanks,

Jason

As others have mentioned, it looks like your task sequence is associated with the x86 boot image.

You need to go to the task sequence properties and set the boot image to the 64-bit boot image package.

It is an unknown device and I have multiple task sequences advertised to unknown.  So I am just out of luck and should boot with a USB device? 

I can't and why would I set all task sequences to x64 boot.  Unless I have all UEFI devices.

You can make the machine "known" (by importing the MAC address), then assign a task sequence to it that has a 64-bit boot image.

The PXE server will use the boot image that is associated with the task sequence. It can't just use some other boot image because that is not guaranteed to work (e.g., the device drivers could be missing). So, it is using the boot image which you said should be used for the task sequence.

You can make the machine "known" (by importing the MAC address), then assign a task sequence to it that has a 64-bit boot image.

• Marked as answer by oliphanj 14 hours 37 minutes ago

If I imported the MAC address of the devices, advertised the task sequence to its collection then the device was able to PXE boot with the x64 boot image.  

If I was unable to do this, I used a SCCM USB key if I had the drivers on the key for the USB dongle.  

Problem is if it is a device like a Surface with one USB port, then you need a USB hub, with USB drive and USB dongle.  It gets to be an expensive setup for imaging many devices at once.  

Thanks for all the responses.  I hope this helps someone.  

• Marked as answer by oliphanj 14 hours 31 minutes ago