PXE boot new PC with Boot Mode UEFI only - black screen

[kennysarmy]

Hi,

 

I've had PXE boot issues over the years and they've all been sorted by adding updated drivers to the boot.wim, but sadly that does n't seem to fix this issue I'm having.

 

I'm evaluating a new small form factor case from Stone Computers and the BIOS is UEFI only.

 

I've set the BIOS Boot Manager so that the only option is UEFI: IPV4 Realtek PCIe GBE Family Controller

 

PXE over IP4 begins and then I get a confirmation screen which says:

 

 

 

WDS Boot Manager

Client IP

Server IP

Server Name

 

Press ENTER for Network Boot Service

 

The Windows Boot Manager Screen shows my list of boot images, including the one I've updated with all the drivers for this new motherboard!

 

If I choose that Boot image from the list then it says Loading Files across the bottom as expected with the progress bar then the screen goes black apart from some slivers of horizontal colour near the top of the monitor (!)

 

 

 

Am I missing a step that's required because the BIOS is UEFI only?

[kennysarmy]

To add if I chose my windows 10 test Lite Touch Windows PE (x64) boot image it gets to my Microsoft Deployment Toolkit Task Sequence OK

[sted]

what os are the images you are trying to boot to if its a windows 7 boot image it will fail because windows 7 dosent (at least by default as far as i know) do uefi

[kennysarmy]

Windows 7.

 

And on the Stone website for the PC's serial number are both windows 7 and windows 10 drivers....so I'm assuming it should work.

 

Anyway - I'm not even getting as far as choosing the main image to pull down from WDS.

[sted]

Windows 7.

 

And on the Stone website for the PC's serial number are both windows 7 and windows 10 drivers....so I'm assuming it should work.

 

Anyway - I'm not even getting as far as choosing the main image to pull down from WDS.

if the pc is uefi only i dont think you will get window 7 on it

[kennysarmy]

Doing a bit of reading suggest we should add some additional scope items to our DHCP:

 

Option 60, 66 & 67 !

 

Which currently are not set.

 

Would/Could this help?

[Blue_Cookeh]

Doing a bit of reading suggest we should add some additional scope items to our DHCP:

 

Option 60, 66 & 67 !

 

Which currently are not set.

 

Would/Could this help?

 

Those DHCP options wont have much effect if you're getting past the boot stage and into the 'Loading files' screen. It suggests there's something wrong with your image/drivers/hardware IMO.

 

I would suggest getting the latest Windows 10 ADK and using the WinPE image from that.

[free780]

Is the bios up to date on the PC?

[LytchettNM]

UEFI is for Windows 8 and up. We had some new machines that showed UEFI as the only options to start with but there was an OS default option "I think it was called" which was set to enable, changing this to disabled allowed for BIOS boot or UEFI and turned also off Secure boot.

[KibosJ]

Doing a bit of reading suggest we should add some additional scope items to our DHCP:

 

Option 60, 66 & 67 !

 

Which currently are not set.

 

Would/Could this help?

 

We had a similar issue here and it turns out that our UEFI machines were actually attempting to boot to the BIOS boot image, I've added the options into DHCP and now it works brilliantly.

 

I can send you over the options I have set in DHCP if that helps.

[kennysarmy]

We had a similar issue here and it turns out that our UEFI machines were actually attempting to boot to the BIOS boot image, I've added the options into DHCP and now it works brilliantly.

 

I can send you over the options I have set in DHCP if that helps.

 

That would be really helpful if you could add them to this thread...

 

Cheers

[jonnykewell1]

We have some small form factor machines from Stone too. Go into the bios, turn off secure boot then restart into the bios then get to the option "boot option filter" and set that to legacy. You will see non UEFI boot options on your boot list.

[kennysarmy]

We have some small form factor machines from Stone too. Go into the bios, turn off secure boot then restart into the bios then get to the option "boot option filter" and set that to legacy. You will see non UEFI boot options on your boot list.

 

Sadly Secure Boot is already disabled...

 

System Overview:

 

AMIEFI BIOS

Version : H110D4P1-PEGA-0302

Edited September 26, 2016 by kennysarmy

[KibosJ]

So in our DHCP we have 2 Vendor Classes set up, one for UEFI and one for BIOS:

 

 

After setting up the Vendor classes I have policies set up, again, one for UEFI and one for DHCP

 

 

Just make sure options 066 and 067 are set correctly for each type of machine.

 

After creating these entries in our DHCP I have yet to have a machine fail to boot

[kennysarmy]

Thanks.

 

I'll try without the vendor classes first to just see if I can get this PC booted to WDS.

 

Cheers

[kennysarmy]

Thanks.

 

I tried without the vendor classes first so added option 66 and 67 to the VLAN scope that my PC is in.

 

10.107.80.*

 

The WDS is in 10.107.93.*

 

 

I still get as far as the Windows Boot Manager (Server IP 10.107.93.xx) screen

 

which shows the boot images on my WDS.

 

It's only after I choose the right boot image does it fail...

 

Do I need to upload a UEFI compatible boot file to my WDS - is that the issue?

 

Cheers

[KibosJ]

Thanks.

 

I tried without the vendor classes first so added option 66 and 67 to the VLAN scope that my PC is in.

 

10.107.80.*

 

The WDS is in 10.107.93.*

 

 

I still get as far as the Windows Boot Manager (Server IP 10.107.93.xx) screen

 

which shows the boot images on my WDS.

 

It's only after I choose the right boot image does it fail...

 

Do I need to upload a UEFI compatible boot file to my WDS - is that the issue?

 

Cheers

 

I think so, I am using SCCM so they are already there. The policies tell the machine if it is UEFI to boot to the EFI file and if BIOS boot to the BIOS file.

[kennysarmy]

OK - so had an update from STONE Support.

 

Enabling an option in the BIOS called Launch CSM gives an option called "Boot option filter" which I can choose between "UEFI and Legacy, Legacy only and UEFI only"

 

Choosing Legacy only and I can boot a bit further.

 

Now I'm getting to this screen before the keyboard stops working:

 

[jonnykewell1]

Sorry I forgot about that additional option in my post. We had all sorts of problems with USB drivers, luckily for us our cloning process with FOG runs a script to install drivers and gets to a point where it installs a network driver which allowed me to remote in and install USB drivers manually.

[sted]

iirc you need to add usb3 drivers to your boot file (or find some usb2 ports or if it has them ps2)

[kennysarmy]

iirc you need to add usb3 drivers to your boot file (or find some usb2 ports or if it has them ps2)

 

Yep - now that's done I've got a bit further!!

 

 

Hopefully it will now work!

 

I'll report back shortly.

 

Cheers

[kennysarmy]

All good