What firmware version are you running ?

You need to upgrade your firmware.

The “set next-server” option was added to the DHCP configuration options with a firware release but I am not sure which one.

Finally Working !!!

edit 2
set auto-configuration disable
set default-gateway 192.168.111.1
set interface “dmz”
config ip-range
edit 1
set end-ip 192.168.111.250
set start-ip 192.168.111.100
next
end
set lease-time 1209600
set netmask 255.255.255.0
set next-server 192.168.111.7
set option1 67 ‘7078656c696e75782e30’
set dns-server1 8.8.8.8
set dns-server2 4.2.2.2
next

[quote=“PeterDoobes, post: 3161, member: 1024”]You need to set the next-server for the DHCP through the CLI in fortigate.

From the CLI:

FORT-310B # config vdom
FORT-310B (vdom) # edit <vdom name>
FORT-310B (<vdom name>) # config system dhcp server
FORT-310B (server) # edit 1 //Replace 1 with the number of the DHCP server id on the fortigate if more than one configured
FORT-310B (1) # [COLOR=#ff0000][B]set next-server 192.168.X.X[/B][/COLOR]
FORT-310B (1) # end[/quote]

Peter -

How are you setting the filename – pxelinix.0 ??

I just put FOG onto a netbook that dual boots Ubuntu and Win7 and have the admin people at my small offices do reimaging.

[quote=“PeterDoobes, post: 3161, member: 1024”]You need to set the next-server for the DHCP through the CLI in fortigate.

From the CLI:

FORT-310B # config vdom
FORT-310B (vdom) # edit <vdom name>
FORT-310B (<vdom name>) # config system dhcp server
FORT-310B (server) # edit 1 //Replace 1 with the number of the DHCP server id on the fortigate if more than one configured
FORT-310B (1) # [COLOR=#ff0000][B]set next-server 192.168.X.X[/B][/COLOR]
FORT-310B (1) # end[/quote]

I really hope this works. In the past I have tried to get this working with my Fortinet units and have not had any luck. The support people at Fortinet were also not able to help me despite opening multiple tickets.