PXE Boot for Windows 10 with UEFI giving E16 No Offers Received on new Stone laptops

[kennysarmy]

We've recently started rolling out Windows 10 using WDS/MDT and have been configuring BIOS on PC's for UEFI prior to imaging.

 

All is working fine across all our subnets.

 

I've just taken delivery of a new STONE laptop which is failing to boot to the network with the BIOS set for UEFI.

 

The laptop gets an IP address then fails with the error :

 

I'm using IPV4

 

As it's working fine on the PC's, is this an issue with this laptop?

[free780]

I had this with 8th generation Intel CPUs and UEFI PXE Boot. Does it legacy PXE boot?

[kennysarmy]

I had this with 8th generation Intel CPUs and UEFI PXE Boot. Does it legacy PXE boot?

 

Yes, legacy boot is fine.

[Steve21]

Whats the error? not sure if there was meant to be a pic above Or was it just the normal e16 as title?

 

If you try it on the same subnet as the WDS server does it work? there were a few fair bugs with PXE and some BIOSs for newer gen machines, but mainly using the same subnet bypasses a lot of them. (Not a fix for sure, but would narrow down the issue fast if it does work!)

 

Steve

[kennysarmy]

Whats the error? not sure if there was meant to be a pic above Or was it just the normal e16 as title?

 

If you try it on the same subnet as the WDS server does it work? there were a few fair bugs with PXE and some BIOSs for newer gen machines, but mainly using the same subnet bypasses a lot of them. (Not a fix for sure, but would narrow down the issue fast if it does work!)

 

Steve

 

Erm, so I'd have to allocate a network socket in my office on the switch and tag it as part of the server vLAN?

[free780]

Same issue. I found the UEFI firmware doesn't pass the information correctly to the PXE server. You can use DHCP options as a work around. However you may not be able to legacy boot on the subnet. Really updated firmware is needed such as when lenevo laptops had the issues. I think Stone laptops are a re-badge so it's up to the original vendor. I hit the same issues with Stone NUCs.

[kennysarmy]

Whats the error? not sure if there was meant to be a pic above Or was it just the normal e16 as title?

 

If you try it on the same subnet as the WDS server does it work? there were a few fair bugs with PXE and some BIOSs for newer gen machines, but mainly using the same subnet bypasses a lot of them. (Not a fix for sure, but would narrow down the issue fast if it does work!)

 

Steve

 

IT WORKED! With the laptop on the same vLAN as the WDS Server - so we have to wait for the vendor to fix the BIOS?

[Steve21]

What options are you using in DHCP etc for giving out the subnet settings? There are some work arounds to make it work across subnets, but depends on the machines.

 

Some of the stone ones are already fixed bios wise, not sure what you're using:

https://kb.stonegroup.co.uk/uefi-pxe-boot-issue-when-ip-helpers-are-used-to-reach-a-remote-subnet-pxe-server_692.html

Stone Group | Support Portal

 

If not there are other workarounds you can do server/network side, but easier if it is just a bios flash

 

Steve

[kennysarmy]

What options are you using in DHCP etc for giving out the subnet settings? There are some work arounds to make it work across subnets, but depends on the machines.

 

Some of the stone ones are already fixed bios wise, not sure what you're using:

https://kb.stonegroup.co.uk/uefi-pxe-boot-issue-when-ip-helpers-are-used-to-reach-a-remote-subnet-pxe-server_692.html

Stone Group | Support Portal

 

If not there are other workarounds you can do server/network side, but easier if it is just a bios flash

 

Steve

 

None, all done with IP-Helpers I believe.

[kennysarmy]

Is this issue likely to be quite isolated...

 

ie. if I buy some new Toshiba laptops (Toshiba Satellite Pro R50-C-179) are they likely to be OK?

[Steve21]

I think it was mainly Lenovo that got a lot hit, but honestly it depends on each model and bios setups etc. I think most companies have updated bioses etc to fix them by now, but obviously depends when it was built/imaged in first place really.

 

In reality though if it's laptops does it matter much? Just build them up on the other port Or are these getting flashed often?

 

Steve

[kennysarmy]

I think it was mainly Lenovo that got a lot hit, but honestly it depends on each model and bios setups etc. I think most companies have updated bioses etc to fix them by now, but obviously depends when it was built/imaged in first place really.

 

In reality though if it's laptops does it matter much? Just build them up on the other port Or are these getting flashed often?

 

Steve

 

Yes, I suppose it's not that much of a problem to edit the switch config. when we do image these laptops....