[MECM] PXE booting in UEFI mode

[Garacesh]

The MECM woes continue!

 

So I've had PXE booting in Legacy mode by setting options 66/67 in DHCP but we have some devices that, so far as I can see anyway, don't actually have a BIOS/Legacy mode.

 

I've removed option 66/67, and added an ip helper-address on the core switch, but devices still don't PXE boot.

Core switch IP Helper table looks like this:

The 2 entries for the DC/DHCP server were added by the previous IT support, but Google tells me there's no problem with having multiple ip helper addresses.

 

I've checked the firewall on the server, UDP 67, 68, 69 and 4011 are enabled (which are allegedly used by PXE?), as well as UDP 64001 to 65000 (multicast), TCP 1433 and 4022 (SQL), and TCP 80, 443, 8530 and 8531 (WSUS) although even with the firewall disabled it doesn't boot.

 

I've tried plugging the laptop I want to image directly into the core switch, as is the Hyper-V host the MECM server runs on. Still nada.

 

The distribution point has Enable unknown computer support ticked (as well as Allow this distribution point to respond to incoming PXE requests and Enable PXE support for clients), and Respond to PXE requests on all network interfaces enabled.

 

The task sequence is deployed to my custom All end-user computers collection, as well as the All Unknown Computers collection, so it should be seeing the advertisement.

Edited March 25, 2021 by Garacesh

[themightymrp]

I know this is an old post but did you ever crack this? We are having the same issue with MECM. PXE boot is fine on legacy BIOS but naff all happens on UEFI mode

[Garacesh]

Kinda-but-not-really.

 

I ended up doing the DNS kludge as documented here

[themightymrp]

Eugh :-/ OK thanks. I'll have a read through and test things out. Thanks for this