Meraki DHCP pxe boot options

[J_Donegan]

Our clients connect to the data vlan three times. We need to use this network to image Windows laptops.

These devices need to contact the production vlan, which is where the SCCM server sits on a different vlan.

These are the DHCP options I have chosen, but when my devices that need to be imaged connect to the data network, they are unable to contact the SCCM server via pxe boot to pull down the image.

Any advice would be very much appreciated.

[GreenMan]

Did you check that the boot server is reachable from the LAN in question?   (incl. appropriate FW rules etc ?)

Have you run any packet captures on the MX or switches to see what's going on?

[J_Donegan]

I can ping the SCCM server on the production network when I'm on the data network. I can also RDP to the SCCM server.

[IvanJukic]

Hi @J_Donegan ,

As @GreenMan has mentioned. Packet captures are the way to go to confirm issues or unexpected behavior. Do you know if the SCCM is using Multicast instead of Unicast traffic to communicate. This could explain the behvaior. If so, see below guide to ensure the set up is correct.

https://documentation.meraki.com/MS/Layer_3_Switching/MS_Multicast_Routing_Overview

[J_Donegan]

Yes when the user device is on the same vlan it’s works with no issues. 
Packet capture is my next test. 

[PhilipDAth]

I'm not familiar with SCCM, but this is what we are using for PXE booting and imaging.

What you could do is use a tftp client, and try and retrieve the file from the server you have specified and see if it can download the file.

[PhilipDAth]

Does this work on any other VLAN?  It is a bit suspicious to see a *.com file in the days of UEFI BIOSs.

[Brash]

Take some captures to work out where the communication is failing.

One thing specific to SCCM PXE boot that might apply is the following:

• Don't use DHCP options 60, 66, or 67. It isn't supported.

Advanced troubleshooting for PXE boot issues - Configuration Manager | Microsoft Learn

[DanielWahlsten]

Good to know 😊