@rocksoft duplicate post. ref: https://forums.fogproject.org/topic/16485/can-fogproject-be-used-to-deploy-bios-uefi-servers-like-a-deployment-server

@danibashkov I too was having issues capturing an image and then I used these settings and it captured an image successfully From a Dell Latitude 3410.

The problem I have now is that the device that that I deployed the image to (also a Dell Latitude 3410) does not boot into Chrome OS Flex. It is stuck in a loop of it trying to boot from HD or network.

@sourceminer said in After Adding Storage for Images / deploy image mounting failed:

I lost all my settings from prior. I had to append the file.

Yes I saw this too when I was developing NFSv4 for FOG. That uses a really different exports file. So now I keep a exportfs.sav file with the correct settings in case I forget in the future.

@sourceminer said in UEFI - Dell Precision 5760:

Turns out someone had added option 60 to the global Options

Yeah that’s not a good option to have. That tells the pxe booting computer that it needs to come back after the dhcp process and talk to the proxydhcp server on port 4011 for the boot info. You would only do this if you had microsoft wds server on the same server as your dhcp server. Or if you were running dnsmasq in the linux world to do the same thing.

@astrugatch So I enabled the plugin system in FOG Settings, but the actual webpage for Plugins does not load. Do I have to enable anything else?

@fabritrento said in what tftp image is right to use?:

PXEClient:Arch:00007

FWIW there are 3 or 4 uefi arch classes. I would at least create arch 7 and arch 9 classes, the others are for 32 bit processors.

@werner I see two different issues here and one is dependent of the other.

So lets start with do you ever get to the FOG iPXE menu? This is the menu where you would pick to register a host or test hardware compatibility?

If no, then what is your dhcp server? Have you configured dhcp options 66 and 67? If yes, what exactly did you enter for dhcp option 66 and 67?

Just load a WIM file, no. That is a microsoft imaging solution.

@Greg-Plamondon Try these queries:

Get a list of (unique) host IDs where username logged in to:

SELECT DISTINCT utHostID FROM userTracking WHERE utUserName LIKE '%username%';

Now combine this query to get the list of hostnames as well:

SELECT hostID,hostName FROM hosts WHERE hostID IN (SELECT DISTINCT utHostID FROM userTracking WHERE utUserName LIKE '%username%');

Be aware that the first query might return more results than the later one because older user tracking entries will still exist even if you delete a host from your database. In that case the later query won’t return this host.

it does not work when I unicast to it either

@manuel-guerrero question - why are you trying to image AWS instances with fog? Are you aware AWS has built-in image capture as well as built-in snapshots you can utilize?

@george1421, ok, agradeço pela resposta.
É que na verdade eu queria colocar a imagem em uma partição de um pendrive bootável em que na outra partição contém um VENTOY com o Clonezilla, e pelo pendrive instalar esta imagem do pendrive em um computador diretamente.
Já realizei uma cópia (via RSync) para um pendrive com o Ventoy em uma partição e o espaço para imagem em outra (NTFS). Desta forma consigo consigo tudo via clonezilla para a máquina, porém quando inicio a máquina apóa a formatação na tela só é exibido as letras VT e não carrega o sistema. Poderia me ajudar neste sentido?

@gjo on the host itself, you can look in the fog client log. You can also look at the “PC properties” and see it’s domain status. in Active Directory Users and Computers, you should see the new computer object. A note on this you might not be aware of, FOG will rename the system to whatever name you have set in the FOG Server for that host, it does this just before domain joining.

When I was doing a lot of imaging, we would set the hostname during Host Registration.

@george1421

This is helpful, thanks.

Maybe I am doing something wrong.

Where do I take the access token from the webhook.

I tried with the bot access token and It gives me that:

e82be1b4-26d8-462b-8d90-2722c71cfb70-image.png

Is there any guide or someone who has it working that could help me?

Thank you in advance

@ocomas I am not exactly sure but sounds you run into the same issue described here: https://forums.fogproject.org/topic/14389/no-configuration-methods-succeeded-dhcp-failed

Simply changing the DHCP config helps in this case.

@dgux Will be interesing to see if you can get this to work. Though iPXE is just the starting point. You will need to set Linux kernel parameters for serial console as well. That’s pretty easy within the specific host settings. But I am not exactly sure if we have serial console driver compiled into the official kernel yet. Not a big deal though. See how far you get and keep us posted.

@sebastian-roth Thank you, I’ll do that 👍

@sebastian-roth I will search another solution. Thanks for your reply 🙂

@sebastian-roth Also, when we changed the subnet of the FOG server we didn’t create a new Server. I changed the IP values inside our original FOG server and reran the FOG Installer for the IP addresses to be changed throughout. After I ran the installer, I didn’t do anything with the certs inside the FOG server.