@foguser said in Client doesn't boot from FOG:
Please stick with me with these (many) questions. I’m trying to draw a picture in my mind of your setup by using your words.
We have a set of clients provided with the service of the pxe citrix server. Notebooks are not part of this (locally installed, no need for pxe-boot until now). I plan to configure them on the dhcp once and leave the options as they are, no switching after that. So every device just needs one service, fog or citrix.
Lets come back to this since you have a windows 2012 dhcp server you can create filters to send the right boot file if needed. We use this technique for sending the right boot file for uefi vs bios type computers. I’m pretty sure we can make this all automatic once we get the pxe booting worked out
The Citrix server provides the client with a streamed image. The dhcp Option 11 is set for this and have been a few years untill i installed fog some days ago.
The options 11, 66 and 67 are configured on the scope of the client network to use the citrix pxe. No individual options until fog
FOG doesn’t care about dhcp option 11 so we can ignore that for now. For testing dhcp option 66 should be the IP address of your fog server (not the fqdn name of your fog server). The reason is some pxe booting roms are pretty dumb where they don’t do a dns lookup for dhcp option 66. For dhcp option 67 it should be either ipxe.efi for a uefi computer or undionly.kpxe for a bios computer.
The main Problem i still have is, the Notebook boots and gets the address and file of the citrix server.
OK to debug this we will need a second computer on the same vlan/subnet as the pxe booting computer. On this second computer install wireshark with the capture filter of
port 67 and port 68. Start wireshark and then pxe boot the target computer. Once the target computer errors out stop wireshark. Please post the pcap so I can review it. I am interested in the DHCP OFFERS (not show in your initial picture). I’m interested in the OFFERS to see what the dhcp server is telling the target computer for boot-server and boot-file.
The DHCP-Server is Windows Server 2012 R2.
This wiki page will help when you get things working to automatically manage uefi and bios boot files: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy
Lets get the pcap from the target computer’s perspective. In my tutorial you will only see the FOG server’s side of the conversation because your target computers are on a different subnet from the fog server. If the target computer is on the same subnet as the fog and dhcp server you can get a complete picture of the booting process. In you case we will need to look at each side to understand what is going wrong.