solved

I disabled Windows 11 fast startup and the image could be captured.

Thank you for your answers

@bsedash You are going to have two areas where you will have difficulty here.

You re using an older version of FOG and FOS kernels. Newer hardware support will be missing. FOG is primarly focused on desktop imaging and you are trying to image a server class hardware. I’m not saying its impossible to use fog for this, you might just need a custom kernel that has the qlogic network driver enabled.

Where the booting process is failing is where iPXE tries to get an IP address. This is where ipxe boots and then tries to get an ip address, none is received. FIrst make sure you are using nic1 on the server since this ipxe build is configured for workstation class computers and it will stop looking after the 3rd found network interface. Also since you are using fog 1.5.9 the version of delivered ipxe is quite old. Lets recompile and install the latest version of iPXE. If that gets you to the fog iPXE menu then that will solve the first problem. https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe

For the next problem, update the fos linux kernel (bzImage) but going to the webui and fog configuration -> kernel update. Update to the latest 6.x kernel to get the latest hardware support.

@kylian001 Yeah I am thanks for the help. How do I mark this as solved?

@Tauric I don’t think any amount of rollback is necessary, but you’re more than welcome to. Pretty sure there weren’t any schema updates or major component changes between 1.5.10 and 1.5.10.34

that said, this looks more like a problem with the kernel, not a problem with FOG and its ability to capture/deploy images.

You could download the kernels from the FOG GUI Kernel Updates

@EuroEnglish I haven’t been able to recreate the issue. I would suggest maybe trying an update to the kernel and init, if you’re on the latest dev-branch version there should be a July 5th dated bzImage and Init available from the fog configuration kernel update and init update menus.
The only other things I can think of might be your Windows 11 partition layout being non standard or something? It should all be booted into RAM at that point though, so that doesn’t make much sense, but it’s possible that the efi partition is too small or something, that’s just a hairbrained theory though. Other thing could be a custom background image? Maybe it stops liking the size of it?

Hopefully trying the newer kernel just solves the problem though.

@maximefog said in Deploy Image:

it is mandatory to register the workstation

This is not a requirement under certain conditions. There is a method I call “load and go”. It is a process that system builders use where once they load the OS on the target computer they never see the computer again. In this method you can not use the FOG Client for any of its function. The install process must be self contained or use a FOG post install script to make the install time adjustments to the target computer. Using this method you do not need to register the computer with FOG. Once the image is deployed to the target computer FOG forgets it ever saw this target computer. Once you have the master image setup as needed you deploy the image from the FOG iPXE menu “Deploy Image” menu. You never have to touch the FOG web ui for image deployment.

@Bhav Just for clarity, do you have an isolated imaging network or are you trying to image on your business network?

If you have an isolated imaging network then you should have configured FOG to setup a dhcp server. The configuration will work for both bios and uefi computers.

If you plan to image on an existing business network, then your primary dhcp server needs to be configured to support pxe booting.

So lets start with how do you plan on imaging?
Second if you are planning on imaging using your business network, what device is your current dhcp server?

@Tom-Elliott I had to reinstall my ubuntu server and installed the fogproject as you suggested. However, the installation still wasn’t able to run to the end. I have attached the error log. I do appreciate your assistance.fogserver error log.txt

Finaly i have reinstalled my server again and just take exports from all sections (snapins, images etc…)

only gruops not working. nevermind ill setup again.

the problem was about the whole configuration with ISCSI disk attach, now i use an NFS and directly mount my image storage on /image.

works like a charm.

see yann

yann

@george1421
I resolved the issue by testing 1.5.10 on a laptop after trial and error I am able to have the same setup as our desktop environment. I will most likely upgrade our desktop server to 1.5.10 and recapture a new golden image.

@processor You set the replicator sleep time (and sleep time for all services.)

FOG Configuration -> FOG Settings -> FOG_IMAGEREPSLEEPTIME

It’s defaulted to 600 (10 minute cycles.)
If you set it to 86400, that should do the checks once per day.

@professorb24 said in How to use fog with two different VLANs:

Yes, I can ping the 192.168.54.X network.

This is positive. OK hopefully last question, what is device the dhcp server on the 54.x subnet? Is it the fog server on the 52.x subnet or something else?

@Tom-Elliott @george1421 I’ve done it, Winscp’d the files from my PC build lab FOG and added them to the directory on the SRV build lab FOG… PXE now working!!! woop

@Nicolas-Bricet This really sounds like a spanning tree issue vs dot1x authentication (unless your authentication process is taking a really long time to authenticate the port). Make sure the port is configured for port-fast, fast-stp, rstp or whatever your switch manufacturer calls it.

Secondly if TIME is the resolution then this can probably be addressed too.

First of all we have the ability to update the iPXE boot loader from a fog install. This tutorial is intended to solve a different problem but you will need this in your solution: https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe

So at this point you know that you can rebuild iPXE right from your fog server. Now we need to adjust iPXE to wait 30 seconds before requesting an IP address (FWIW, by default spanning tree it take 27 seconds to start forwarding data, so the timing is suspiciously similar).
When iPXE boots up it runs a FOG custom script file that tells iPXE how to configure itself. If you can remember back to the DOS days, this was the autoexec.bat files function. iPXE has a similar script. Within the iPXE source directory the file is call ipxescript (a look on github) https://github.com/FOGProject/fogproject/blob/a4bb1bf39ac53c3cbe623576915fbc3b5c80a00f/src/ipxe/src-efi/ipxescript#L1 This is the script that runs inside iPXE to configure the network.

To take this concept one step more, the FOG developers have already created a version of the iPXE that has a 10 second boot delay (remember you need a 30 second delay). An example of this 10 second delay startup is here: https://github.com/FOGProject/fogproject/blob/a4bb1bf39ac53c3cbe623576915fbc3b5c80a00f/src/ipxe/src-efi/ipxescript10sec#L3 All you need to do is either update that 10 to a 30 or copy that line over to the ipxescript main script and change it to 30. Once that is done recompile ipxe using the instructions above.

The FOG delivered 10second delay versions of iPXE are located in the /tftpboot/10seconds directory. So you have two paths to get this done, but I would surely look into spanning tree first to make sure port fast is enabled and make the above second way unnecessary.

I quickly read about your issue, could this be related with your problem ? :

https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy?page=1

@RogerBrownTDL I believe the 24.04.3 LTS is supported by FOG in the Dev-branch.

If wanting to stick strictly to the 1.5.10 “latest official” release, I believe Ubuntu 22.04 is the latest supported.

@Tom-Elliott I think this post helps fix the issues:
https://forums.fogproject.org/post/154920

@Tom-Elliott Thank you so much for your verification. I was a little panicked haha. Have a good day!

@Tom-Elliott

@Tom-Elliott said in Multicast timeout:

You created a table in FOG called hostsIP?

Yes, in our environment hosts, have ip reservations and I did not found in FOG tables last used ip by hosts (may be I missed something) so I created a table associating ip to hosts names.

@Tom-Elliott said in Multicast timeout:

Note: This isn’t a bad thing, I’m just trying to reference the information.

No worries.

@Tom-Elliott said in Multicast timeout:

The way I understand this, you’re looking at the mutlicastSessions table, getting a group, and getting the name of the hosts.

First I get all running mutlicast sessions. foreach sessoin I guess the group associated. I get max number of machine in the group I get the current current associated machines to the session As if a machine is finished, it is removed from the sesssion machine list, I compare the group machine number and the current machine running for this session. If the two differ it means that at least one went to the end but not the others. Now you make me talk on it I understand the specificity of our setup, all of our machines names start with group name (ex : all machines in rooms 1 will have such a name pattern : R1-P1, R1-P2…R1-P10), So as I have group name and I know that hosts which belong to it have it in their name, I get all machines with name starting with the group name we are working on. The same way I get machines IDs If not already done I get image ID Same for task ID (one client is enough as in mulitcast if I kill on client it kills all multicast) For each remaining hosts, I store ID, and Name in an array. I kill the task and do a 1 sec sleep loop till the mutlicast session disappear. (It can take few seconds for the multicast to be removed and without this loop some clients can’t be reinstalled because they are still part of another process. and finally for each hosts in created array, I create a unicast session (using host id) and reboot the pc using host ip.

@Tom-Elliott said in Multicast timeout:

You’re at least aware of the IPs which most others will not be, but just trying to think this through.

I searched for a more elegant way to get hosts ip and which could be universal, but the lack of time lead me to this rude behaviour 😉

But if someone has an idea on how to do it I would be very please to update this.
To be honest I thought to modify more the init.xz to populate automatically the hostsIP table when it loads but I have a working solution and it’s not even a priority for us but something more comfortable, if I had spent more time on this, someone would have come to break my fingers 😉

Sorry for the long post.