struggling with this problem for some time now..

saw some related threads but not really providing an answer

have one customer who bought a bunch of Thinkpad 10 machines from lenovo and the purpose is to install them with a 8.1 SOE, untill now the only thing that works is to use a standalone usb medium

our setup is SCCM 2012 R2 on top of Server 2008R2 using infoblox instead...

the thinkpad 10 has the latest ATOM cpu and is definitely a 64 bit UEFI machine

we also noticed that some switches have problems to (try and ) boot the UEFI machines, dont know why yet

the issue is that the only thing we see during a UEFI only PXE boot is that the NBP file gets succesfully downloaded (even twice) and then just switches back to the next bootoption.

i've checked:

-PXE boot another UEFI device: same symptom

-PXE boot legacy devices: ok

-changed the bootfile in option 67 to the efi file: same symptom

-all files are in the smsboot\x64 folder

lenovo support now wants me to do this: include a winPE x64 image that supports UEFI and then run the following command on the server:

"WDSUTIL /New-MulticastTransmission /FriendlyName:"WDS Boot Transmission" /Image:"Microsoft Windows PE (x64) Win8" /ImageType:Boot /Architecture:x64 /TransmissionType:AutoCast"
 

but I don't see what UEFI/pxe has to do with multicasting and why should I change something on wds if UEFI boot under similar circumstances works in other implementations?

any more useful ideas folks?

• Edited by grundlichkeit Thursday, September 11, 2014 1:00 PM typo

have you verified via smspxe.log file that the mac addres of the usb dongle is indeed being picked up by your distribution point ?

also, do any other uefi devices (like hyperv Gen2 Virtual machines) work with UEFI network boot in your setup

niall,

the macaddress has been imported and indeed it shows up in the smspxe.log

apart from two different types of Lenovo hardware (one tablet and one laptop) I haven't tested any other uefi devices yet no.

With UEFI devices you should use x64 boot image. x86 works for most but issues have been reported while using them as in your case. Go for x64 WinPE.

I know.  the task sequence we use to install them is using a specific x64 bootimage that includes the touchscreen driver for that tablet (makes it easier to troubleshoot during installation)

nonetheless also x86 PE images are available to support other machines

Hi,

I noticed that you referred NBP file inyour original post. I'm not quite sure which indeed with this statement.

But actually you need use bootmgfw.efi as boot file insteadfor UEFI boot purpose.

• Edited by Daniel JiSunMicrosoft contingent staff, Moderator 4 hours 36 minutes ago

Hi,

I noticed that you referred NBP file inyour original post. I'm not quite sure which indeed with this statement.

But actually you need use bootmgfw.efi as boot file insteadfor UEFI boot purpose.

that's one of the things I tried, did not change the problem

in the meantime what we did was add on the install subnet another DP but with server 2012.

this is working fine.

so still to rule out:

- problem due to OS version of the sccm DP

- problem due to switching

- problem due to infoblox

Hi,

I noticed that you referred NBP file inyour original post. I'm not quite sure which indeed with this statement.

But actually you need use bootmgfw.efi as boot file insteadfor UEFI boot purpose.

• Edited by Daniel JiSunMicrosoft contingent staff, Moderator Monday, September 22, 2014 6:49 AM