Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

NEW UEFI PXE Boot doesnt work

  • Thread starter Thread starter Magic
  • Start date Start date
  • Replies Replies 0
  • Views Views 740

Magic

New Member
Messages
1
Reaction score
0
Points
1
Hello, our UEFI CLients need about 1 minute with PXE until they boot the OS via the hard drive. Legacy clients do not have this problem.There are UEFi clients of different models.With DHCP option 66+67 set, everything works.Boot order: network boot, local HDDAs soon as the DHCP 66+67 are not set (IP Helper is active), it takes approx. 1 minute until the computer uses its local boot drive. If there is a provision/deployment and the PXE flag of the client on the MECM is deleted, the computer runs into the installation without waiting.As long as it waits, no IP address of the client is listed in the SMSPXE log. It only gets this as soon as Windows boots up. Legacy clients get an IP immediately.Ports 67+68+69 and 4011 are open on the MECM firewall.DHCP, MECM are different servers.If all servers and clients are in the same network, then it is the same error pattern. This eliminates the IPHelper as the cause.I read in the Microsoft forum that there are no abort pixels with UEFI. This only works with legacy. Therefore the behavior described is normal. I can't believe this because why does it work with DHCP options.Does anyone have an idea for a solution
 
Back
Top