Posts made by Sebastian Roth

@Noseman The tools used within FOS (FOG OS doing all the hard work when capturing and deploying) are no official Microsoft certified software products but from open source community. They work in 99% of cases but I can imagine there can be special states of the filesystem or certain edge cases those tools simply cannot handle (yet).

Great you found a workaround!

@plegrand You are using FOG 1.5.10 already, right?

@C-Franklin Not sure I have ever seen this error message. Can you post a picture?

Would you be able to test with more different computer models?

@repier89 Nice you got that external NIC adapter to try and see if it’s a network issue or now. And yes, we have a winner.

Please schedule a debug deploy task for the HP Probook 450 G9 and boot into it. Run lspci -nn | grep -i net and post output here.

@UserBxl What does the partition layout look like? Please post the contents of the text file named d1.partitions found in /images/Img_Thinkbook14G3ACL_admin_TEST.

@Almeida I suggest you update to 1.5.10 or at least manually update the FOS kernel.

@repier89 said:

I tried to change different settings in the bios but my problem remains the same.

Which settings did you play with? Did you also check to see if you have settings on “Storage Controller for VMD” mentioned in https://forums.fogproject.org/topic/15132/hp-probook-640-g8-imaging-extremely-slowly

Please also read through that whole topic and post relevant information here, e.g. output from commands like lspci -nn | grep -i net

Then do a network speed test using iperf3 (also mentioned in this topic) and post results here.

@Tedamp Just to add to this topic: FOG does not mess with the EFI boot loader entries. You have to do this yourself. You might wanna read this topic as well: https://forums.fogproject.org/topic/16703/dual-boot-2-disks-unable-to-boot-grub/2

@mass said in NFS error:

… set up my Fog server (version 1.5) …

Hope you mean 1.5.10 and not 1.5.0?!?!?

@glequeau Great hint on this!

@Zourous said in Dell Latitude 3540:

I’m on 1.5.5

Well then you might want to upgrade to 1.5.10 or manually download newer iPXE binaries here: https://github.com/FOGProject/fogproject/tree/master/packages/tftp

@KaiHerlemann Yes, @JJ-Fullmer is right there. The installer is not made to handle custom certificates properly yet. We never found the time to make this work reliably. But if you are good with managing this yourself you can still do it.

The whole topic is a bit complex due to the different tools and layers involved.

• Basic web access to the web UI - just adjust Apache config as you like
• But along with that the iPXE boot loader is using HTTP/HTTPS to load the menu items. So if you switch to HTTPS you also need to compile your own iPXE binaries - not very hard: https://docs.fogproject.org/en/latest/development/fog-release/#ipxe (but use ./buildipxe.sh /path/to/your/CAcert.pem and skip the armsupport=1 if you don’t have ARM CPUs)
• Now this was the easy part. I started to write about the fog-client here but then realized I did so in the wiki already: https://wiki.fogproject.org/wiki/index.php?title=HTTPS#Custom_CA_and_certificates

I know, this is not ideal having to stich together the pieces from various sources and make up the rest yourself. So if you are keen we would appreciate if you document exactly what you do and we’ll add it to the official documents. That would be really great!

@KaiHerlemann said:

Usually we use ACME to create certificates.

I would not setup a FOG server open to the public. There are ways to get certificates through ACME without facing it to the web, e.g. opening ports only for the time of cert renewal on the firewall, doing cert renewal on a separate machine and copy those over and so on. Please consider wisely because FOG is not made to run on a public IP/hostname safely.

@JJ-Fullmer said:

I would suggest at install time NOT selecting ssl and then altering the config to use your custom certificate.

In the one hand I agree. Doing it this way you can go step by step. On the other hand if you do a fresh install (don’t if you have a running server) then I tend to suggest you enable SSL straight away because it will generate a SSL enabled Apache config for you and save you some time.

@danieln Now, @rodluz is spot on! There was no schema change between 1.5.9-RC2 and 1.5.10. The installer does no check it just prints out the message in case there was a schema update.

@Noseman said in could not map attribute 0x80 in inode FOG 1.5.9:

I have exactly the same problem in FOG 1.5.0.

I hope you mean 1.5.10!?

Now on your issue, made sure fast boot is disabled??

@jgibson60 @Zourous As for a quick test you can rename the files. Make sure you remember the correct names to restore those later on.

May I ask which version of FOG you two use?

@LLamaPie Thanks for testing and letting me know.

@jeremyvdv Maybe this is going to help you: https://wiki.fogproject.org/wiki/index.php/Windows_DHCP_Server

@Tom-Elliott said in “Deploy Image” Not Working for HP Probook 450 G9:

I can check, but can you provide the github link for the changes you made?

Sorry I did not check the forums any faster. Seems like you found it. Thanks!

@Richarizard504 Then I may suggest you provide the full fog.log file from that client having the issue. We might find out what’s wrong with some more context.

@ariederer26 Is the image type set to resizable or non-resizable? Default is resizable in FOG but I suggest you use non-resizable if the laptops all have the same disk size.

@mosi This issue is fixed in the latest dev-branch version. Please update.