@DarkSwordsman About DHCP PXE boot you want to read this: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

Sure some hardware just does not want to play with the exit types. But give it another try. Make sure you play with the UEFI exit types for UEFI systems.

Do you have one batch of identical client hardware or is it all different systems? Please tell us what exactly you have and there might be other users around using the same hardware and might know which setting works.

@Dee I guess you have a a fair amount of clients and maybe also storage nodes. All talking to the FOG server and causing too much load so other requests time out.

We have adjusted some values and fixed other related things in version 1.5.5 so might want to update and see if that helps.

@AsGF2MX said in Compatibility check for X1 Carbon 2018:

However I can’t remember the cli for the fog command. and the wiki page has the deploy section empty.

Not sure if I get that right. In a debug shell you simply run command fog to run whichever task is scheduled for this client.

@hancocza I totally missunderstood this whole topic right from the start. It would have helped a lot of you’d clearly mentioned that you are using a custom SSL certificate. Might be obvious but I did not get it.

So what you describe here has nothing to do with FOG as far as I understand it. The password input stuff is something Ubuntu is doing when you start the apache webserver and you have a password protected private key. We as in the FOG installer does not add anything to that. So my guess is that Ubuntu changed things with one of the latest updates.

Probably you just need to install the correct extra package to make this work again…

@hancocza said in Not able to TFTP boot. Invalid Argument Error:

am I supposed to have two different certificates specified in the buildipxe.sh?

Yes! The one going in TRUST is the CA cert or possibly what you use in Chain parameter in the apache config. If it is a real chain of two or more certs in the chain I am not sure if iPXE can handle it this way. Give it a try. The CERT is just that, the webserver certificate.

By the way, keeping the certs in the home directory might not be a wise idea. Someone comes along and cleans up the home dir one day and boom all is gone.

@Quazz Yes, I think those are the two options we have. I tend to go the file based way because this is something that people/software can’t fiddle with. I am fairly sure that no one will ever change the boot loader binary path/name or Windows installation dir name. There is no reason to do this. Sure there is not much reason to change the flags either but I feel like this can happen more easily and the difference is, that Windows will still work perfectly fine with altered flags - so people won’t notice until they clone with FOG.

Our greatest advantage is that we only really need to think about NTFS partitions if we are simply replacing the old label system. This means we can work a lot more targetted regardless of the path taken.

I was hoping to improve the whole set and also make detection if Linux partitions work better. But that might just be another step.

Essentially I want to distinguish between partition only being fixed in size (e.g. recovery as we don’t want to expand that) and those that need to be fixed in position and size (e.g. boot partitions). But that’s the bigger picture. I might have the time to work this out over Christmas. Don’t think I will get there before.

@hancocza said in Not able to TFTP boot. Invalid Argument Error:

I do use a custom SSL cert for the web server.

Ah sorry, I missed that. Then you need to adjust the utils/FOGiPXE/buildipxe.sh Script to point to those custom certs as well. Edit that file and put in the correct paths for CA cert and server cert:

#!/bin/bash
BUILDOPTS="TRUST=/var/www/fog/management/other/ca.cert.pem CERT=/var/www/fog/management/other/ca.cert.pem"
IPXEGIT="https://git.ipxe.org/ipxe.git"
...

This is the default. Change to where you have your custom cert files and compile again! Then rerun the installer as well.

@hancocza Sure you don’t get any error from the iPXE build script?

Do you use a custom SSL certificate for the FOG web server?

@hancocza said in Not able to TFTP boot. Invalid Argument Error:

Should I be allowing it to go through the FOG installation again or does that basically reset the iPXE binaries again?

When you run the buidlipxe.sh Script it compiles new binaries including the correct SSL cert and puts them in the “installer directory”. From now on you can run the FOG installer as often as you want, it should always install those HTTPS-enabled iPXE binaries!

@federico The ACPI messages sure look dangerous but usually aren’t. THe machine seems to have a buggy ACPI implementation. If you register this client manually in the FOG web UI you can set Kernel Parameter acpi=off to get rid of the messages.

How long have you waited on that screen. It should eventually go ahead. Have you waited for 10 minutes to see if it proceeds?