Tablet Can't PXE Boot Win 10 Tablet

[cyannella]

This post is deleted!

[cyannella]

@george1421

It is a new install using Ubuntu 20.04 LTS running in a VM.

I do not have anything setup for dhcp 66 and 67 on the Windows side.

Did I miss that in the docs?

[george1421]

@cyannella What device is your dhcp server?

Also did you have another netboot device (server) setup in your environment like a WDS server or such?

[cyannella]

@george1421

I setup the fog server on 66
and the boot file undionly.kpxe on 67

When I pxe boot now, it just sits there for a second then goes back to the bios boot menu.

If there is a message it goes by too quick to see what it says.

[cyannella]

@george1421
There are no other WDS servers on site that I know of.

Asked the other admins and they said No as well.

[cyannella]

@george1421

DHCP is running on a Server 2016 Standard VM on Hyper V

[george1421]

@cyannella said in Tablet Can't PXE Boot Win 10 Tablet:

I setup the fog server on 66
and the boot file undionly.kpxe on 67

Ok this is the first issue if the target tablet is a uefi system, this file name needs to be ipxe.efi.

Since you have a windows 2012 or later dhcp server then you can/should follow this guide on setting up policies in the dhcp server to automatically supply the correct boot file name based on the target computer. https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

[george1421]

@cyannella said in Tablet Can't PXE Boot Win 10 Tablet:

There are no other WDS servers on site that I know of.

If after you correct your dhcp setting and you are still getting that strange boot file name, I will give you instructions on how to use wireshark to find a quick answer to the above question. But lets not go there unless needed.

[cyannella]

@george1421
Changing the boot file was oh soooooo close.

iPXE Its booting.
Configures the Mac address
REceives the DHCP Answer on interface net0
tftp://10.71.24.139/default.ipxe… ok
http://10.0.2.15/fog/services/ipxe/boot.php… connecting

then hangs. The web server is on .139
I need both the tftp and http to be found on the same VM.
Where is it picking up the incorrect IP for .15?

[george1421]

@cyannella said in Tablet Can't PXE Boot Win 10 Tablet:

tftp://10.71.24.139/default.ipxe… ok
http://10.0.2.15/fog/services/ipxe/boot.php… connecting
then hangs. The web server is on .139
I need both the tftp and http to be found on the same VM.
Where is it picking up the incorrect IP for .15?

OK now we are getting somewhere. Did you change the IP address of the fog server after FOG was installed? Or do you have a second nic card in this server?

[george1421]

@cyannella I thought we had a tutorial on this but I can’t seem to find it at the moment so let me give you a quick what to change to fix it.

Edit the following files.
/opt/fog/.fogsettings
/tftpboot/default.ipxe

Replace the incorrect IP address with the right address for the fog server.

Then in the webui FOG Configuration->FOG Settings then hit the Expand All button. Search that page for the old address and replace with the correct address.

Look at Storage-> Default storage node and fix the IP address in there.

Lastly back in the FOG Server linux console, rerun the fog installer. That will pick up the address you saved in the .fogsettings file and fix up the reset of the install for you.

[cyannella]

@george1421
The boot menu worked for a hot second then stopped.

I edited the .fogsettings and default.ipxe files that stuff was working.

I reran the installer now nothing.

I get a >>Start PXEover IPV4 and the tablet just sits there and times out.

[george1421]

@cyannella Ok since it was once working we can get it going. It was so close.

1. Reboot the fog server just to be sure.
2. When the fog server comes back up access the linux console and key in ip a s and post the results here.
3. Now confirm what you have configured for dhcp options 66 and 67 (if you did not enable dhcp server profiles). Post screen shot of the dhcp server settings here, redact what you need but if you have internal (non-public) addresses leave them since no one can use that data against you.

If the above doesn’t line out, we’ll have you load wireshark on a witness computer (3rd computer connected to the same subnet as the target computer to listen to the dhcp process). If the fog server and target computer are on the same subnet then we can use the FOG server to collect this info.

[cyannella]

@george1421
Hi George!
I wanted to circle back and let you know that all is working now thanks to your help.

I have some other questions but I will open new tickets for those.
This crisis is complete and working now. I was able to boot one of the tablets
and gather an image off of it.

Thank you soooo much for the help.

Chris