@besa said in [Solved] FOGProject Tecnical Info:

Its not for a paper, but for recommendation. My brothers supervisor wanted to take a look to the {Company}… and they use old fog system[1.2.0].

Just be aware that FOG 1.2.0 is really old. It doesn’t support win10, uefi, gpt disks, and current hardware. If you are imaging older stuff then it will work OK for you. But if you are going to need anything I mentioned, you will need a more current release of FOG. FOG versions newer don’t need fogcrypt since its all built in now.

lets start out by understanding why you are usb booting into the iPXE menu. What problem are you trying to get around?

which is a MUST for me since I have the option to type in my fog server IP

This tells me it working, but your dhcp server isn’t sending out the right information to go to the next step.

FOGCrypto is and old program used to encrypt password so they could be saved in fog. Not really of value for a cyber security student to write a paper on.

On a whole fog is not very secure because it uses many older protocols like NFS v3 and http (vs https). There is still some very old code in FOG that was written when security wasn’t really a topic. In the context of cyber security there are many reasons to not use FOG in vulnerable environments (if you were looking for a different entry point to discuss). Understand I’m not saying anything bad about FOG, but it was originally written in different time and space.

The developers are slowly working on FOG 2.0 code base that was built from the beginning with cyber security in mind. That release is still a while off at the moment from being realized. But the baseline stuff that has been done so far looks really great.

@AndrewG78 said in Tablet with WINDOWS 10 and USB-LAN SMC 7500 adapter:

Are there any news regarding refind_ia32.efi?

@Sebastian-Roth if refind_ai32.efi is included (I think it should be), then the ipxe menu will need to be reworked a bit to take that into account. Right now everything calls refind.efi. I think a simple test using the arch parameter could redirect the call to refind_ai32.efi vs refind.efi. I had it worked out a bit ago, but that fell off the table too.

@AsGF2MX said in Compatibility check for X1 Carbon 2018:

Well I’m now at the USB method and @george1421 thanks for the img. I got the usb to work. However I can’t remember the cli for the fog command. and the wiki page has the deploy section empty.

Not sure why you need the debug command. You should schedule the task in the FOG server then usb boot the flash drive. Pick option 1 and it should boot into fos doing what ever the FOG server told it to do (capture/deploy).

@AsGF2MX Well where we have seen this issue before is in then hand off between iPXE mode and the uefi firmware to launch the kernel. You could try newer iPXE kernels that may have a workaround for buggy firmware. Typically a firmware update fixes the issue. But if you have the latest firmware we need to look elsewhere.

As an alternative, you could switch the device back to bios (legacy) mode for capture and deploying. I know its a bit of a pain, but that method works too. You can capture and deploy a uefi image in bios mode no problem. You just have to be in the right firmware mode to boot the OS.

While this isn’t a solution (and not sure if it worked in 1.3) we have been able to usb boot right into FOS bypassing PXE loading altogether. There are some caveats with this approach but it does work (for sure) with the 1.4.x branch. https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image Look at the FOG forum chat for an example image file. You will want to install the kernels and inits from 1.3.x series on the usb flash drive as well as update grub.cfg according to the tutorial to see if it works for you.

One last thing I thought of, make sure secure boot is disabled. The FOS kernels are not signed by microsoft so secure booting is not viable right now.

Is there any chance to spin up a FOG 1.5.5 environment to see if the issue has already been resolved. 1.3.0 is somewhat old with old kernels and inits. Updating the kernel is not sufficient since you need the later inits too which are linked to the updated FOG server code.

X1 Carbons (i7-vPro) 2018 and right after the ram disk downloads
Can you explain this? is the ram disk you are talking about is the FOS init.xz file? Ensure that the firmware is up to date on the carbon devices. We’ve seen some pretty buggy firmware on early release systems that are addressed with firmware (BIOS) updates.

@Sebastian-Roth Well done. If we can filter these issue out at the beginning it will make support easier trying to figure out why this isn’t working… ;-)

@george1421 Just wondering is this fog client computer you are trying to USB boot registered in FOG? If so delete the registration and see if it throws the same error.

@hancocza OK that tells us that boot.php code is working on the fog server. That is the complete iPXE boot menu. So we know its not the fog server causing you pain.

So you haven’t changed the fog default.ipxe, boot.php is working because the menu is created when you call it from a browser.

so the question is what is being passed that is causing boot.php to return an invalid ipxe menu.

The next step is to usb boot again and get the error. Then inspect the apache access log, error log, and php-fpm error log files. These are typically in /var/log directory.