@WT_101 As I mentioned, FOG doesn’t support imaging over wifi. The first roadblock that you will hit is iPXE because it needs the drivers and then your wifi settings to connect to. The second issue you will have is with FOS Linux, none of the wifi drivers are added into the kernel, nor is any of the wifi utilities compiled into the initrd file system. You would be better served with a usb ethernet adapter.

@RusinovAA

1.) When preparing Windows 10 for cloning (for capturing an image using FOG), is there a need to run and apply the Sysprep /oobe /generalize /shutdown utility. Or FOG, when capturing an image, performs procedures for decoupling Pts from binding to equipment and resets the OS identifier?
Sysprep (system preparation) prepares a Windows client or Windows Server for imaging. Sysprep can remove computer-specific information from a Windows installation (aggregate) so that it can be installed on different computers.

FOG does not react with the target system OS. It is Microsoft’s best practice to sysprep your golden image before image capture. I can tell you from experience if you want to make a neutral image that can be deployed to any hardware you should sysprep the golden image. If you capture from a Dell 5430 laptop and then restore to another Dell 5340 laptop you can image this way without sysprep. Understand that just because it works doesn’t mean this is the best choice. For me always sysprep the image if going to the same hardware or not. That way (for my campus) I have 1 golden image for 12 different hardware platforms both laptop and desktops. I install the required drivers using a FOG post install script, but that is a different discussion.

Quick answer, must sysprep? Yes to different hardware between golden image and target computer. Imaging between the same hardware you should sysprep but I’ve seen people no sysprep cloning and it works.

2.) Does the current version of FOG have the ability to automatically add computers running Ubuntu Server / Ubuntu Desktop to the Active Directory domain when distributing an image?

Quick answer is no, fog will not do this. A bit longer answer is that you can do this when ubuntu boots, and make a bash script to add the computer to AD.

@mattah_18 Is fast boot disabled on this machine? How do you shutdown the machine before capture?

@kamburta The basic steps are here: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

You will just need to get the right kernel parameters for booting ubuntu live. If you have a live boot CD you can get the parameters from either grub.cfg for the isolinux.cfg files. The steps for live boot are very close to the steps to boot the installer its just the kernel parameters that need to be adjusted.

Good morning,

Regarding our problem, we deployed an old ubuntu 20.04 image and it works. This seems to come from ubuntu version 22.04

Best regards,

Cédric

@zuchowra This often happens because of either the DHCP server isn’t presenting boot options, but more often it’s because you ahve multiple things responding with what server should be used. The system has no idea which one to use, so it requests you manually enter it.

Please check your dhcp server to ensure the boot option is sending option 66/boot server name

it appears to have fixed itself, i tried again on a whim today and im no longer having issues with the locations plugin. sooo problem solved i guess.

@capitald Let’s take a step back. Before we get into this any further we need to think about the whole connection between fog-client and the FOG server. The fog-client wouldn’t get as far as loading a snapin if there was a general problem with the SSL certs and trust.

So is must be very specific some issue at this stage. So you use the location plugin? Were both nodes setup with HTTPS (which is not the same encryption layer we are looking at here)?

@pacodijou You likely need to rethink how FOG operates.

The fact that you got into FOS itself (which is where you’re at) at least shows DHCP is working and passing the Options 66/67 appropriately, but it’s failing to get access to the fog server.

Based on what I can see, the DHCP items are working properly, assuming 192.168.75.10 is the fog server since that’s also where it’s trying to connect to look for access directly to the fog server.

Do you access the fog server at url:
http://192.168.75.10/fog/index.php?

@Wayne-Workman Hi Wayne, that was it - reb

@Mentaloid Confirmed a bug in 1.5.10. Will be fixed in the next version. Will keep you posted here.

Moving the topic to bug reports.

Code:
https://github.com/FOGProject/fogproject/blob/1.5.10/packages/web/lib/pages/snapinmanagementpage.class.php#L466
https://github.com/FOGProject/fogproject/blob/1.5.10/packages/web/lib/fog/storagenode.class.php#L200

@danibashkov said in Exec format error during network boot:

Could not boot image: Exec format error (http://ipxe.org/2e008001).

Most likely the kernel image is missing or corrupt. Please check using the following command: file /var/www/{html/,}fog/service/ipxe/bzImage

As well I may ask how your DHCP server is being setup? Did you say yes for FOG to install and setup DHCP for you on the FOG server or do you manage your own DHCP server in the network? Just asking because possibly this might be a 32/64bit issue as well.

@ITRecords Have been pretty busy with other things and forgot about this topic. Whoops.

Ok, so we have a plain disk drive here (sure virtual disk but no LVM or fake-RAID) which makes it pretty easy.

Make sure there is no FOG task (deploy or capture) running! Stop NFS daemon: systemctl stop nfs-kernel-server Unmount the partition: umount /dev/sdb1 Install an easy tool for expanding the patition: apt install cloud-guest-utils Test expanding the partition: growpart -N -v /dev/sdb 1 (note the space before the partition number) Expand partition: growpart -v /dev/sdb 1 (note the space before the partition number) Expand filesystem in partition: resize2fs /dev/sdb1 (no space before partition number) Mount partition: mount /dev/sdb1 /images Start NFS: systemctl start nfs-kernel-server

@tacOS updated main post, turning off notifications on this post.

@AlkarimJ You would likely want to set the primary disk to /dev/sda

It looks, at least from the image you provided, that it may be the nvme0n1p1-5 you have on “successful” machines may be 1TB (or at least large enough) to contain the raw image, but on the new machines these drives are smaller than the expected.

@cwufog Is there enough diskspace for this application to install? Assuming it is an installer package in teh first place…

It seems a windows based error code

@rivaldydwi Snapins are utilities to run a script, install a program, or what have you…

Generally, speaking, you would use the Snapin Run With of cmd /c with .bat scripts, but this isn’t strictly necessary.

.bat scripts ARE executable by nature and can be completely void ofr SRW/SRWA.

If your bat file is expecting its own arguments, this is what you would run Snapin Run With Argument.

@hammerc807 For me github.com resolves to a totally different subnet. Could either be fine or a pointer to your provider doing transparent proxying?!

Try openssl s_client -showcerts -connect github.com:443 -server github.com to show the whole certificate chain.