@fritoss007 I can give you a hackers approach at doing what you want with the registration process. FOG calls fog.man.reg to invoke the registration process. You can find the source of this program here: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.man.reg

If you understand bash shell programming you can make modifications to this program to alter it registration. I will give you a hint to use notepad++ to edit this file because windows notepad add extra windows junk into the file that will cause error messages during execution.

So now you have this file how can you inject it into the FOS Linux booting process?

You can do the recommended method to unpack and repack the inits as Sebastian outlined. Take a bit of the hacker approach and use a FOG pre-startup script (i.e. post init script) to copy the fog.man.reg from the FOG server to the FOS Linux disk as FOS Linux boots. If you look at this tutorial: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg in the section called fog.patch.customhostname you can see how to “patch” FOS Linux as it boots.

@fritoss007 This may help too, as I believe @Sebastian-Roth has made this script native to the github fogproject code, and can be run at any time:
https://github.com/FOGProject/fogproject/blob/master/utils/FOGiPXE/buildipxe.sh

@fritoss007 said in LDAP authentication with userPrincipalName fill with email address:

Should I report it somewhere else

In this tread is good enough. Both Tom and Sebastian are in this thread so its the right place at the right time.

@fritoss007 Then you might be better doing the fixparts methodology. Now I’ve added postinitscripts to the working branch data so things should be able to be automated much more nicely for those 18 or so systems you’re seeing with this issue. (You can add checks to get things working how you need it).

@fritoss007 No I did, but that doesn’t matter.