@george1421 said in new version e2fsck ?:

FOS Linux OS

Thanks for that tidbit. Using this guide in the FOG wiki:
https://wiki.fogproject.org/wiki/index.php/Modifying_the_Init_Image

I was able to replace initmountdir/sbin/e2fsck with the latest version.

I booted a fogclient into debug mode and ran “e2fsck -V” to verify the changes.

Thanks George!

Hello, i found a curious behavior. When I use a account who only serve to join domain : “djoin / djoin”, I can’t join the domain but it work with the GUI. But when I use my administrateur account and password, it work.
Fog 1.5.9
Julien

@Tom-Elliott Yeah, that’s about the only other thing I can think of too. It’s a brand new Dell PowerEdge Server with a new HD though, but maybe the HD is just a lemon. I’ll swap out the HD and reinstall FOG and see if that works.

Thanks again for all your input!

@george1421 Hello any ideas?

@Sebastian-Roth Thanks for the update! Again, this feature for us is more of a “nice to have” than an essential, so no immediate rush. I know all of y’all are busy!

@wass Since all of the boot loaders you mentioned are bios boot loaders and you are seeing the no configuration methods succeeded it sounds like the computer is in bios mode. Its strange that iPXE and bios mode computers are not able to configure the interface. For bios the boot loaders undionly.kpxe or ipxe.kpxe should work on 99.8% of all computers. Does this computer have multiple nic cards?

@kamburta Pretty sure this is known and fixed in the dev-branch versions of the FOG repository.

@smazzola We need more information to be able to help. Please provide what has been asked or we’ll close this topic.

@Tom-Elliott

It’s every device we’ve tired. We’ve tired both UEFI and MBR. iPXE booting is working with everything else we have and is able to utilize the NIC just fine.

Dropping down to the CLI, the OS can see and list the mac addresses just fine. It appears that it’s just however FOGs init/boot is looking at or for the MAC address is the issue.

@LulaHuel While we do have this “Windows Problems” forum, it’s not quite in the same boat.

We, in this community, have an imaging platform called FOG. Often these images might include Windows, and sometimes the imaging process might have issues with Windows, hence this naming mechanism for this topic.

I don’t think anyone would hesitate to help you, but we generally ask people discuss issues as it pertains to them, windows, and how or what FOG may have done that might have cause it. We aren’t a general MS Windows support forum.

Glad you were able to fix the issue and posted a solution, but how this was something FOG did I’m unsure.

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

@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 May I suggest looking at the BIOS . I see you captured an EFI image. Just check the boot settings on the Lenovo make sure it is booting to EFI and not the Auto setting . Also check if secure boot has been disabled.

Hi,

I just rebuilt two proxmox debian 11 containers with FOG 1.5.10

Master node > install HTTPS
Storage node > install HTTPS

Install plugin Location

Master node and storage node are in the default storage group
Master node > default’s Master node

Create new location > location_1
storage groupe > default
storage node > defaultmember
storage node protocol> HTTPS

Create new location > location_2
storage groupe > default
storage node > secondary node
storage node protocol> HTTPS

Create snapin in default storage group with replication enabled

Configure one host with location_1
Deploy snapin > OK, it works

Configure one host with location_2
Be sure the snapin is replicated into the storage node
Deploy snapin > it doesn’t work
What am i doing wrong ?

Here is the snapin log

---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 03/07/2023 12:39:24 Client-Info Client Version: 0.13.0 03/07/2023 12:39:24 Client-Info Client OS: Windows 03/07/2023 12:39:24 Client-Info Server Version: 1.5.10 03/07/2023 12:39:24 Middleware::Response Success 03/07/2023 12:39:24 SnapinClient Running snapin snapin_1 03/07/2023 12:39:24 Middleware::Communication Download: https://xxxxxxxx//fog/service/snapins.file.php?mac=00:23:24:19:46:64&taskid=2 03/07/2023 12:39:24 Data::RSA ERROR: Certificate validation failed 03/07/2023 12:39:24 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: La signature du certificat ne peut pas être vérifiée. (NotSignatureValid) 03/07/2023 12:39:24 Middleware::Communication SSL certificate chain error: Une chaîne de certificats a été traitée mais s’est terminée par un certificat racine qui n’est pas approuvé par le fournisseur d’approbation. 03/07/2023 12:39:24 Middleware::Communication ERROR: Could not download file 03/07/2023 12:39:24 Middleware::Communication ERROR: La connexion sous-jacente a été fermée : Impossible d'établir une relation de confiance pour le canal sécurisé SSL/TLS. 03/07/2023 12:39:24 SnapinClient C:\Program Files (x86)\FOG\tmp\file.zip 03/07/2023 12:39:24 Middleware::Communication URL: https://xxxxxxxxx/fog/service/snapins.checkin.php?taskid=2&exitcode=-1&mac=00:23:24:19:46:64&newService&json ------------------------------------------------------------------------------

@JJ-Fullmer I think I have determined this is a problem in an internal process with the api. Gonna try to narrow it down some more.

Hello everyone,

The problem continues to persist (and even during the creation of the image)

When I have to restart my PC (in OOBE mode) to: change domain, restart after name change, restart after update, etc…

This happens randomly during a reboot. I come across this error. It is therefore impossible for me to create an image.

I find solutions (change on regedit, etc) but my OOBE mode is lost and I have to start over each time.

A solution ?

@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.

@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.