Massive congratulations. Take the time you need to make the house a home. My wife and I have been working on building/buying a house for a year now, I have to admit we’re a bit jealous.

Try replacing ${fog-ip} with ${boot-url} . That is what I use.

Sadly there is no good Linux base UEFI PXE, and then on top of that right now you would have to have a UEFI compatible kernel to boot.

So for now, if you cannot put the device in legacy mode, then it cannot work with FOG.

Have you checked permissions?

Relevant steps for install should also be added for new distros of Debian.

Excellent guide. Thanks for sharing this.

It should also be noted that as of FOG 1.x.x, you no longer have to customize anything for even the newest release of Debian.

This should probably get Wiki’d.

Could also be your hardware. I have been fighting some TFTP Open Timeout errors on a couple of machines lately and I am trying to find a solution.

Have you… updated your kernels?

What revision were you updating from?

I would get the ClamAV info directly from their site and use them to update your init.gz . Personally though, I would not update or even use ClamAV. I have had very bad behavior from it as of late, and wouldn’t even take its scan results seriously.

I just avoid AVG like the plague.

And as to the UEFI issue, I agree it would be a great feature to have. For the time being though, you will have to switch any UEFI BIOS to Legacy mode to get any useful PXE utilities to work other than WDS, but WDS is for deployment only.

That is unrelated to my issue, which was fixed quite a while ago by Tom. If you don’t need your DB or settings, I would suggest doing a full wipe of your FOG install, followed by a reinstall. There is a bad DB password entry that gets left in a settings file, I just can’t recall what file it is right now.

I do not know whether it is a problem with ClamAV’s definitions database, or an issue with their current engine, but ClamAV currently identifies numerous false positives. Some of these false positives include detecting ‘trojans’ in clean Windows driver files, which it will quarantine, rendering the host unbootable.

As such, I strongly suggest against using the Virus Scan and Quarantine task until this problem is resolved on ClamAV’s side. This is not a FOG problem, and I do not know of anything that can be done to work around the issue.

Have you installed the newer version of the FOG Client?

My bot senses are tingling.

Disk Surface Test does not leave its console open on the host for your to see the results nor does it report back to the server at any place I could find.

If you are going to deploy to them then they need to be part of a domain, and you will need to have at least some sort of shared storage that groups of them will have access to. Otherwise there is no way to get the data from point A to point B.