Jump to content

Recommended Posts

Posted

What am I doing wrong.

 

I can’t get UEFI laptops to PXE boot. There are legacy setting in the BIOS.

 

Other devices with legacy PXE all working as they should, I can images them from SCCM.

 

I have IP helper address set pointing to my SCCM server.

 

I have set the DHCP options 60, 66, 67 as shown.

Capture.JPG

 

If I boot a UEFI laptop it gets to the screen ‘checking media’, ‘media present’ and then stops.

 

Is there someting else i need to change in SCCM

 

Cheers

Posted (edited)
I have IP helper address set pointing to my SCCM server.

 

I have set the DHCP options 60, 66, 67 as shown.

The IP Helper address is meant to be used instead of DHCP options, not in addition to.

 

If you remove the three DHCP options you will probably find it starts working. :)

Edited by Arthur
  • Thanks 1
Posted

On your deployment server (10.80.1.34) open event viewer on go to Applications and Services Logs\Microsoft\Windows\Deployment-Services-Diagnostics, I have each log in this location enabled when troubleshooting. Admin and Operational are the most useful logs to troubleshoot.

 

On another note what manufacturer/model laptops do you use?

  • Thanks 1
Posted
The IP Helper address is meant to be used instead of DHCP options, not in addition to.

 

If you remove the three DHCP options you will probably find it starts working. :)

 

Cheers

I have removed all the DHCP options still get this, but did see PXE-E16 error flash up

pxe.jpg

Posted
If I boot a UEFI laptop it gets to the screen ‘checking media’, ‘media present’ and then stops.

Are you deploying your OS Task Sequence to 'All Unknown Computers' and making it available to "Only Media and PXE"?

 

CTdeZA.png

  • Thanks 1
Posted

What OS is your SCCM server on? I think you have to be on 2012 or 2012 R2 to support UEFI PXE boot.

 

Are you also using the Windows 10 PE image?

Posted

Have you got UEFI booting working on any other device?

 

I had problems on a new server until I imported an older windows 10 iso that had the efi files that 1803 appeared to be missing

Posted

Have you both x64 and x86 Boot Images set up on WDS? Some older kit uses 32-bit UEFI despite having 64-bit CPU.

 

Also check BIOS for a setting within Integrated Peripherals that the full PXE IPv4 stack is enabled (PXE itself will be on but not the network options)

 

Check BIOS version, is there an update available if this only affects one particular brand of laptop. Can you boot from a standard desktop machine, especially so if you have any Dells etc. that tend to have better built BIOS than the white box OEMs such as Clevo.

 

Sent from my VFD 610 using EduGeek mobile app

Posted

Update,

 

I put this new UEFI only laptop on the same VLAN as the SCCM server, it booted, TS loaded and run, laptop now sitting happily with win 10 on it.

This VLAN does have an IP helper address on it pointing to the SCCM server.

So far so good.

Teacher VLAN has IP helper address on pointing to the SCCM server, no extra DHCP settings.

If I now put the laptop on this VLAN, it doesn’t work, I’m back to the image I posted before (above).

If I now add in DHCP scope option 60,66 & 67. It now seems to work.

 

I’ve compared the switch config and there is no difference between the way the two VLANs are setup

 

Anyhow things seem to be working now, so thanks for the help

Posted
Update,

 

I put this new UEFI only laptop on the same VLAN as the SCCM server, it booted, TS loaded and run, laptop now sitting happily with win 10 on it.

This VLAN does have an IP helper address on it pointing to the SCCM server.

So far so good.

Teacher VLAN has IP helper address on pointing to the SCCM server, no extra DHCP settings.

If I now put the laptop on this VLAN, it doesn’t work, I’m back to the image I posted before (above).

If I now add in DHCP scope option 60,66 & 67. It now seems to work.

 

I’ve compared the switch config and there is no difference between the way the two VLANs are setup

 

Anyhow things seem to be working now, so thanks for the help

 

 

Check BIOS booting on the teacher VLAN now. You may have broken it specifying options needed for UEFI booting. The way around this is to use Policies in the DHCP configuration. The client identifies which mode it's booting in when it sends its request and the DHCP server can then hand out the appropriate options.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...