@kalafina Hi, DISM’s error code 87 is often because of an incorrectly formatted command.
The issues could be because you are trying to run this command with a relative path of the xml file instead of the absolute path.

You can try changing the Snapin Run With Argument to “/c dism.exe /online /import-defaultappassociations:C:\Program Files(x86)\FOG\tmp\”
I’m not sure how the command will react to the space in the file path.

This is what I do for my default app associations snapins. I create a snapin pack with the xml file and a batch file that moves the xml file to the C drive then runs the dism command with the absolute path (dism.exe /online /import-defaultappassociations:c:\appassoc.xml)

Hope this helps!

@westcustom I had this issue with some of my HP workstations. I had to change the DHCP bootfile setting from ipxe.efi to snp.efi and that fixed it.

I know this thread is old, but I am adding onto it with my research and findings.

My experience with this issue is only with HP computers, so no idea how other manufacturers do this.
HP’s firmware is written in a way that MAC address passthrough only works using HP thunderbolt docks, on Windows, using the correct dock drivers. MAC address passthrough also does not work with USB-C to Ethernet adapters because the adapters are not thunderbolt. Given this information, FOS out of the box would not be able to access the MAC address passthrough.
Judging by the Linux kernel patches I have seen online, adding this support to FOS would be pretty difficult since it seems like it depends on the network controller of each dock. This means that each dock needs to be programmed into the kernel and changes to that network controller driver need to be made as well.

The other part of the issue is that iPXE gets the MAC address of the device in a different way than FOS. In my experience, iPXE gets the system MAC address (the same address that should get passthrough), while FOS gets the address that Linux gives through the ip addr command.
I have read other threads where iPXE gives a different MAC address, but it wasn’t HP so I can’t check on that.

I have a workaround that I did for HP computers which I have been testing for a couple weeks. The workaround is working for me, but I would rather do some more testing before putting out a tutorial.

@dvorak Just as @george1421 said, e2fsck needs to be updated on the FOG Operating System (FOS), specifically the inits. The FOS inits haven’t been updated in a bit over a year but I can build new ones for you so you could test it out, just let me know.

@Tom-Elliott I am working on newer inits with the updated e2fsck package to resolve this issue.

@VegaFlash I will update you when the new inits are available, for you to try it out.

@george1421 Thanks so much! So what fixed it for me was just removing all the other iPXE commands. So now my parameters are:

login
kernel bzImage loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10..../fog/ consoleblank=0 nvme_core.default_ps_max_latency_us=0 rootfstype=ext4 mac=${net0/mac} ftp=10.... storage=10....:/images/ storageip=10.... irqpoll chkdsk=0 capone=1 type=down img=1909GoldenImage imgType=n imgPartitionType=all imgid=43 osid=9 imgFormat=0 auditMode=1
imgfetch init.xz
boot || menu

This works perfectly for what I need.

@DARUN974 I’m not sure what you are referring to by “reconfigure”.

How did you update the kernel?
I would recommend you update the kernel using this guide.

@chasteencs That’s strange, not sure why they wouldn’t be there. You could get them from https://github.com/FOGProject/fog-client/releases/tag/0.12.2 and place the files in the /var/www/fog/client directory.

@george1421 Okay so I found it in /proc/devices and I was able to get the HP program working!!
I had to add the program files to the init.xz filesystem and modify parts of the program to not use the modprobe & rmmod commands.
I also had to create the directories needed for dynamically loaded modules and add the compiled module into it so that the program can look for it there.

I now have to do the third part which is custom postinit scripts to use the system MAC address instead of the dongle address. This should be pretty easy.

Once I have that working, I am going to do a full write-up of it for reference for myself in the future and anyone else that comes across this.

@JJ-Fullmer I’m currently working on new kernels and inits. Having issues with building partclone for the inits, but I’ll hopefully have some time this weekend to get it done.
I will include the ufs changes for the kernels.

@mrowand I consider Rocky (and other RHEL derivatives) a bit of an advanced distro. SELinux and the firewall are on by default and that makes things a bit more complicated.
In the FOG installer there is a check if SELinux is enabled and it’s recommended and the default option is to set it to permissive. There is also a check if the firewall is enabled but by default we don’t disable it, this means that you then have to go and modify the firewall rules for everything to work correctly.

I just re-created the VM and installed FOG, this time I didn’t set SELinux to permissive and didn’t disable the firewall and I am having some issues like you. This is not something that we need to/will “fix” since there are checks and recommend to set SELinux to permissive and disable the firewall.

If you have everything working now, we can set this post as resolved.

@collegestjoseph Can you try out this testing kernel and let us know if it works? https://github.com/rluzuriaga/fos/releases/tag/EXP_20250927

@mrowand I just created a Rocky 9.6 VM and installed FOG stable and didn’t have any issues. The install skipped php-json since it didn’t find that package. I didn’t need to install anything else manually.

Can you post an image of the error that you are getting?

Few things to check:
Is this a new Rocky Linux server? (I ask because if you are reusing a Linux install, it may have had some settings that could give you this issue)
Are you behind a proxy?
Is the Rocky install pulling the packages from the BaseOS/AppStream of the install ISO or from the web? (I ask this because this happened to me once)

@rurap Not sure what that patch would have been, but our last kernel release includes the Realtek R8168 driver. This kernel has fixed that same issue for other users.

@Afif I have seen this happen before due to a bad RAM module. Please run a memtest on the NUC.

@Clebboii It is now a general release (not in experimental phase). You can update to the latest kernel and init from the FOG settings pages or using this link: https://github.com/FOGProject/fos/releases/tag/20250715

@punch07 Everything there seems right to me.
Did you disable secure boot on the VM? Is the VM set to UEFI? ipxe.efi requires UEFI so make sure that the VM is changed from BIOS to UEFI.

@Clebboii I just noticed an error in how FOG displays the experimental kernel/init releases. For now, please get it from here: https://github.com/FOGProject/fos/releases/tag/EXP_20250630

@Eazis I created an experimental kernel that includes the drivers to fix this issue. Would you be willing to test it and let us know how it goes?

@Clebboii @olivier-bonnici I created an experimental kernel that includes the drivers to fix this issue. Would you be willing to test it and let us know how it goes?