@SBodager That seems to have fixed the issue for the physical machines that were having issues but not the vm’s

@Tom-Elliott Thank you. Are the 10-second delay files the .kkpxe files? I’m new to all this, since the guys who set it up are no longer with the company I’m being pressed into learning it on my own.

@george1421

Thank you for the info. I am looking into this but the machine is in another location so it is taking me some time to get the time to get out there.

@Wayne-Workman

authoritative;
ddns-updates on;
ddns-domainname “wooster.net”;
ddns-update-style interim;
default-lease-time 28800;
max-lease-time 43200;
option domain-name-servers 192.168.10.14, 192.168.10.20;
option domain-name “wooster.net”;
option ntp-servers 192.168.10.16;
option netbios-name-servers 192.168.10.20;

subnet 172.16.0.0 netmask 255.255.0.0 {
option routers 172.16.1.200;
'# range 172.16.5.1 172.16.5.11;
}

subnet 172.17.0.0 netmask 255.255.0.0 {
option routers 172.17.1.200;
range 172.17.1.110 172.17.1.190;
}

subnet 192.168.101.0 netmask 255.255.255.0 {
option routers 192.168.101.200;
range 192.168.101.101 192.168.101.118;
}

subnet 192.168.102.0 netmask 255.255.255.0 {
option routers 192.168.102.200;
range 192.168.102.101 192.168.102.122;
}

subnet 192.168.103.0 netmask 255.255.255.0 {
option routers 192.168.103.200;
range 192.168.103.101 192.168.103.125;
}

subnet 192.168.104.0 netmask 255.255.255.0 {
option routers 192.168.104.200;
range 192.168.104.101 192.168.104.115;
}

subnet 192.168.105.0 netmask 255.255.255.0 {
option routers 192.168.105.200;
range 192.168.105.101 192.168.105.105;
}

subnet 192.168.106.0 netmask 255.255.255.0 {
option routers 192.168.106.200;
range 192.168.106.101 192.168.106.140;
}

subnet 192.168.107.0 netmask 255.255.255.0 {
option routers 192.168.107.200;
range 192.168.107.101 192.168.107.120;
}

subnet 192.168.108.0 netmask 255.255.255.0 {
option routers 192.168.108.200;
range 192.168.108.101 192.168.108.151;
}

subnet 192.168.109.0 netmask 255.255.255.0 {
option routers 192.168.109.200;
range 192.168.109.101 192.168.109.118;
}

subnet 192.168.110.0 netmask 255.255.255.0 {
option routers 192.168.110.200;
range 192.168.110.101 192.168.110.121;
}

subnet 192.168.111.0 netmask 255.255.255.0 {
option routers 192.168.111.200;
range 192.168.111.101 192.168.111.125;
}

subnet 192.168.112.0 netmask 255.255.255.0 {
option routers 192.168.112.200;
range 192.168.112.101 192.168.112.121;
}

'# Addressing for computers being “FOG” imaged
if substring (option vendor-class-identifier, 0, 9) = “PXEClient” {
'# next-server 172.16.1.99;
'# filename “pxelinux.0”;
next-server 172.16.1.98;
filename “undionly.kpxe”;
}

We have a seperate DHCP server, and it is the only one.

Server

• FOG Version: 1.3.5-RC-10
• OS: CentOS 7

Client

• Service Version: 6066
• OS:

Description

I have added a new fog server on CentOS 7 using the latest version of fog. I am able to get some of our machines to boot fine but others get stuck in a reboot loop during iPxe. I am very new to this program and am trying to copy the setup from a prior install done before I starting working here. I have changed our linux DHCP server to undionly.kpxe but have noi idea what else to do to get it working. We have a mix of hardware and are running mostly Windows 7 and a few 8.1 and 10 machines. Thank you for any help you may be able to provide. I have included a pic of the error we get.