@Tom-Elliott latest pull resolved the issue. Appreciate your help on this!

@Tom-Elliott no stress, with so many posts it’s normal to miss some 😉

@AlexisPHC said in Issues with Windows DHCP Server:

because we run them in HA mode

but there doesn’t seem to be another DHCP server present

My interpretation of these two statements sounds in opposition.

If you are running windows server in HA or failover mode, make sure that both dhcp servers have the dhcp boot options configured. If I remember right these settings are not copied over between the dhcp HA nodes. Understand this might have changed with later releases of dhcp server but with 2016 the pxe boot stuff needed to be set on each node individually.

@Tom-Elliott Thank you. Logging out with 1.5.10.1730 works properly.

@88fingerslukee Thank you, I promise I will try your project and leave a feedback.

@youzersef What if your router providing next server is pfsense.

What needs to be changed in pfsense? My current settings are that of fog.

Pfsense : 10.22.24.1 : (controls DHCP, next server, etc)
Fog 10.22.24.5 : (Working flawless)
iVentoy : 10.22.24.13

Everything I try is sending client back to pfsense, and then errors because it’s getting the boot file for fog, when it’s expecting iventoy_loader_16000

Thanks ! Time to get this project wrapped up 🙂