Fails to PXE boot to FOG

[tvrkey]

I have a machine that has been inventoried and I literally just deployed an image to it via FOG. I installed some software and then ran sysprep again to upload my final image to our FOG server and now when I PXE boot, it just goes straight into Windows…does anyone have any ideas?

[ianabc]

Check the task list in fog to make sure that the task has actually be scheduled and is waiting.

[tvrkey]

[quote=“ianabc, post: 33369, member: 24548”]Check the task list in fog to make sure that the task has actually be scheduled and is waiting.[/quote]

It is

[ianabc]

What do you see in the PXEboot process, can you see it getting a DHCP entry?

[nhomburg]

I have the same problem. It goes straight TFTP boot and won’t connect.

[ianabc]

nhomberg: It should flash up the DHCP process, if it doesn’t then you have an issue with DHCP, does it get that far?

[tvrkey]

[quote=“ianabc, post: 33372, member: 24548”]What do you see in the PXEboot process, can you see it getting a DHCP entry?[/quote]

Yeah, it gets to DHCP and sits for a few moments, then proceeds to Windows.

[ianabc]

Do you see the iPXE setup screen appear? It should, since you were able to deploy an image earlier, but can you confirm that you see it saying something like (N.B. This is for a system without a task scheduled)
[CODE]
net0: 52:54:00:27:7a:dd using virtio-net on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 52:54:00:27:7a:dd)… ok
net0: 192.168.222.102/255.255.255.0 gw 192.168.222.1
Next server: 192.168.222.100
Filename: undionly.kpxe
tftp://192.168.222.100/undionly.kpxe… ok
PXE->EB: !PXE at 9C3B:06D0, entry point at 9C3B:030C
UNDI code segment 9C3B:076C, data segment 9CB2:2CD8 (624-638kB)
UNDI device is PCI 00:03.0, type DIX+802.3
624kB free base memory after PXE unload
iPXE initialising devices…ok

iPXE 1.0.0+ (8a380) – Open Source Network Boot Firmware – http://ipxe.org
Menures: NFS FTP HTTP HTTPS iSCSI DNS TFTP VLAN AoE bzImage ELF MBOOT PXE PXEXT
Configuring (net0 52:54:00:27:7a:dd)… ok
/default.ipxe… ok
http://192.168.222.100/fog/service/ipxe/boot.php… ok

http://192.168.222.100/fog/service/ipxe/bg.png… ok
[/CODE]
Depending on how much or little of this you see we might be able to narrow down where the problem is.