Jump to content


JHBPJF

UEFI PXE Boot - Need Help

Recommended Posts

Time has come where we're getting more involved with getting tablets imaged, but these pesky things always use UEFI and don't support legacy. I'm having a hard time booting these things into PXE.

 

From my understanding, you should use IP Helpers instead of DHCP Scope. I've done this already and my legacy setup still works, and I've made more progress with UEFI, but they still don't get pushed into downloading the correct .wim file I setup in SCCM. My DP which have the WDS role on them are all Server 2012.

 

I unfortunately wish I could provide more insight, but the screen flashes so quickly I don't know what the error is.

 

It says it's downloaded the NBP file, then it goes into WDS Boot Manager, and that's where it fails and continues to load Windows.

 

Does anyone know how to not have it continue on error? Or what exactly is going on?

 

Dell says I need to add boot images to WDS. Since I've never touched WDS and everything is controlled by SCCM, I'm a bit lost.

Share this post


Link to post
Share on other sites


Are you running SCCM 2012 SP1 and the Windows 8 ADK? You need these to have the required boot images for deploying UEFI as far as I am aware.

 

In any case, there is a stack of information about deploying with UEFI on this page that should help:

http://www.windows-noob.com/forums/index.php?/topic/6250-how-can-i-deploy-windows-8-in-uefi-mode-using-configuration-manager-2012/

Share this post


Link to post
Share on other sites

make sure that you have distributed both the 32 bit and the 64 bit boot wim's to your distribution points and that your UEFI capable task sequence has the 64bit boot wim attached to it if your hardware is 64bit, lastly make sure the UEFI device is in UEFI mode (and not legacy mode) and verify from the vendor (or boot into windows and find out) if it's 32 bit or 64 bit hardware, if it's 32 bit you'll need to image it using standalone media (usb or cd) and that usb media must have a task sequence with a 32 bit boot wim, if it's 64bit hardware (most UEFI hardware is 64bit capable) then use the 64bit boot wim... or separate the deployments using collections targetting the computer architecture

Share this post


Link to post
Share on other sites

UEFI machines are tricky to boot, what hardware are you using? the HP elitepad 900 for instance is a pure 32 bit tablet and it requires a 32 boot image as it cannot boot from a 64-bit boot image. So as Niall wrote you need to make sure that you have a task sequence that supports UEFI partitioning, and that you use the correct architecture that matches the device for boot image and so on.

And as you wrote you have already the DP's running server 2012 so then you should be able to support pxe booting 32 bit UEFI devices as well.

Regards,

Jörgen

Share this post


Link to post
Share on other sites

Are you running SCCM 2012 SP1 and the Windows 8 ADK? You need these to have the required boot images for deploying UEFI as far as I am aware.

 

In any case, there is a stack of information about deploying with UEFI on this page that should help:

http://www.windows-noob.com/forums/index.php?/topic/6250-how-can-i-deploy-windows-8-in-uefi-mode-using-configuration-manager-2012/

 

Yes I am.

Share this post


Link to post
Share on other sites

make sure that you have distributed both the 32 bit and the 64 bit boot wim's to your distribution points and that your UEFI capable task sequence has the 64bit boot wim attached to it, lastly make sure the UEFI device is in UEFI mode (and not legacy mode) and verify from the vendor (or boot into windows and find out) if it's 32 bit or 64 bit hardware, if it's 32 bit you'll need to image it using standalone media (usb or cd) and that usb media must have a task sequence with a 32 bit boot wim, if it's 64bit hardware (most UEFI hardware is 64bit capable) then use the 64bit boot wim...

 

 

What makes a task sequence "UEFI capable"?

Share this post


Link to post
Share on other sites

UEFI machines are tricky to boot, what hardware are you using? the HP elitepad 900 for instance is a pure 32 bit tablet and it requires a 32 boot image as it cannot boot from a 64-bit boot image. So as Niall wrote you need to make sure that you have a task sequence that supports UEFI partitioning, and that you use the correct architecture that matches the device for boot image and so on.

And as you wrote you have already the DP's running server 2012 so then you should be able to support pxe booting 32 bit UEFI devices as well.

Regards,

Jörgen

 

The unit I am trying to image is a Dell Venue 11 Pro (5130) Tablet. It has Windows 8.1 already on it. 32-bit operating system on x64 based processor.

Share this post


Link to post
Share on other sites

 

What makes a task sequence "UEFI capable"?

 

the hard disc partitioning steps need to be present for UEFI - see this post for more info

Share this post


Link to post
Share on other sites

 

the hard disc partitioning steps need to be present for UEFI - see this post for more info

 

My task sequence already has a UEFI partition setup.

 

My issue right now is getting it to download the x64 boot wim in order to get into selecting the task sequence.

 

I'm using MDT if that matters.

Share this post


Link to post
Share on other sites

well whatever is the LAST deployed task sequence will be the task sequence that runs and that decides what boot wim is downloaded

 

so if you have a task sequence with a x64 bit boot wim, and you deploy it to All Unknown Computers, and if you then network boot an unknown computer, it will attempt to run that task sequence.

Share this post


Link to post
Share on other sites

hi guy,I have same toy Dell venue 11 Pro with 32-bit operating system on x64 based processor and stuck in same issue with you.

There should be two separated symptom you have.

Scenario 1. screen flashes quickly when download NBP file in the UEFI PXE progress.

-->the right behavior of this step should be "download NBP file successful" message (WDS Boot Manager)solid displayed and waiting for user to press enter key to continue the progress

for this symptom:what your version of boot image? did you use the SCCM native contained(6.3.9600.16384)? If yes,update to 6.3.9600.17031 and try again.after that it works properly in my here.

Scenario 2. the client don't download the right .wim file accordingly

-->maybe anyweb's comments is the right point.Deploy both x86 and x64 TS to unknown computers collections should the root cause of this failure.Need separate the deployments using collections targetting the computer architecture firstly

sorry for poor English and hope help!!

Share this post


Link to post
Share on other sites

Time has come where we're getting more involved with getting tablets imaged, but these pesky things always use UEFI and don't support legacy. I'm having a hard time booting these things into PXE.

 

From my understanding, you should use IP Helpers instead of DHCP Scope. I've done this already and my legacy setup still works, and I've made more progress with UEFI, but they still don't get pushed into downloading the correct .wim file I setup in SCCM. My DP which have the WDS role on them are all Server 2012.

 

I unfortunately wish I could provide more insight, but the screen flashes so quickly I don't know what the error is.

 

It says it's downloaded the NBP file, then it goes into WDS Boot Manager, and that's where it fails and continues to load Windows.

 

Does anyone know how to not have it continue on error? Or what exactly is going on?

 

Dell says I need to add boot images to WDS. Since I've never touched WDS and everything is controlled by SCCM, I'm a bit lost.

 

Hi topic owner, any feedback?

Share this post


Link to post
Share on other sites

I had the exact same issue deploying to a Dell Venue 11 Pro tablet (well actually 60 total). For some reason, even though the processor shows as 64-Bit architecture under "System" in the OS, I cannot deploy 64-Bit OS to it, it fails saying the architecture doesn't support it so I'm assuming its limited to 32-Bit since that's what was on it when purchased as well. Either way, doesn't matter, these only came with 2GB of RAM.

 

* To answer your question about the error, its due to "Secure Boot" being enabled in the BIOS. Disable this feature and viola!

 

* I am unaware of a way to have a task sequence that can do both 32-bit / 64- bit OSD so I created a whole new task sequence for 32-Bit deployments and attached a x86 boot image under the Properties of the task sequence, all works well. If your OSD still fails, its because you need drivers.

 

* I also had to add drivers for the docking station's NIC which I found here:

http://en.community.dell.com/techcenter/enterprise-client/w/wiki/5029.winpe-5-0-driver-cab

 

( Older winpe files here on the main page: http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065 )

 

 

That should be everything, the deployment is super slow compared to a normal laptop, I'm assuming its due to the hardware of tablet and dock. But it is working.

 

 

Hopefully this helps someone who comes across this older thread.

 

- Shawn

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...