Yes, was able to confirm it is working. Thank you for your help!

@boombasstic This is known and will be fixed automatically on the 15th, but please if you need to switch to the dev-branch and install it. Then you should be able to export reports.

@phant0mbot said in Dell OptiPlex 3000 Thin Client:

have tried both SAN and GRUB exit options

boot loader == snponly.efi

These are in contradiction with each other. SAN boot and Grub are bios boot methods. snponly.efi is a uefi boot loader. Since you are getting into the fog iPXE menu we can assume the hardware IS uefi based since it is booting snp.efi. Try a uefi exit mode of rEFInd (refind) to see if that will boot from the hard drive. The default value can be set globally in the fog configuration->fog settings page. Don’t force a bios attempted boot from a uefi booted computer, that never works.

Not sure if anybody has actually had a chance to look at my docker image yet. I’m throwing my hat in the ring for maintaining an official image, but I’d need some help with it.

@Tom-Elliott I figured it out.

I was getting confused by the similar language between the installation process and storage group setup.

A normal installation is just a fog storage node that has a web server and UI on it. A FOG network requires atleast one to work. However a Storage node can be set as the master of a storage group no matter the installation type.

My problem was that because the storage node in the “Bris” storage group did not have a master node setup, the default group could not replicate any images or snapins over. All storage groups must have a master for it to work effectively.

@Tom-Elliott feel free to clarify any of the above rant.

Thank you for the information. I used a bare metal machine. I started with a VM but then just used a old pc. I tried it with Fedora then Ubuntu but did not have any luck. I did not get any errors when installing with the install script.

I will take a look at the information you gave me and see if I can get anything working.

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

@Jchinn412 The answer is it depends on how you have your disk structure setup

Post the results of these two commands.

lsblk
df -h

It maybe easy or harder (but not impossible) depending on how you have the disk created.

@Fog_Newb Yep, it’s as I suspected:

The Line:

Subsystem sftp /usr/lib/openssh/sftp-server

should be changed to:

Subsystem sftp internal-sftp

Then restart ssh services: systemctl restart sshd

Then your Storage Node testing should succeed!

@george1421 I see now and you’re right as my clients are all legacy boot/BIOS boot non UEFI and would not benefit from the client-arch examination.

I’ve already declarations set for each host in my dhcpd.conf file in terms if MAC to IP and so adding another field of filename “some boot loader file” won’t be impossible.

Thanks you for this exercise as I’ve learned some very important things here.

Because I’m not affiliated with FOG in any official capacity and I’ve never actually contributed to it in any way before, I completely avoided making any actual changes to the source. I have noticed that there could be a couple of things that could make the docker implementation a little easier though, specifically around the FOG services themselves. I’m not entirely sure they are completely container friendly, but I really need more hands on this to test it out thoroughly.

Also, I used Debian 13 as the base image for this and it ends up being pretty large (2.5GB). It might be possible to shrink this with alpine-linux but I didn’t want to break a bunch of stuff and then have to spend more time chasing those bugs. Anybody that wants to work that angle, please feel free.

@Frode-Woldsund

I created an image. Give it a go and let me know

https://forums.fogproject.org/topic/18000/unofficial-docker-image-beta

@tchavei2

check out my image! Let me know if it works for you

https://forums.fogproject.org/topic/18000/unofficial-docker-image-beta

My RP address was not pointing to my FOG server 🤦

Once this was adjusted, multicast is functional. Definitely a good reminder to start small.

Hi

In fact, I really want to use those third party package because they do things very well
My snapin configuration are not tied to a specific version of a package, it’s the upstream repo who take care of that

But I have found how to install my install.bat file

Here is the solution

Snapin Name: 7zip Snapin Description: Installation de 7zip Snapin Type: Snapin Pack Template Snapin Pack Template : PowerShell x64 script Snapin Pack File: "%SYSTEMROOT%\sysnative\windowspowershell\v1.0\powershell.exe" # autofilled Snapin Pack Arguments: -ExecutionPolicy Bypass Set-Location "$env:ProgramFiles\FOG\tmp\7zip"; & ".\install.bat" Snapin File (exists): 7-Zip_25.01-1_x64.zip Snapin Enabled : x Snapin Arguments Hidden: Snapin Timeout (seconds): 0 Replicate?: x Reboot after install: Shutdown after install: Snapin Command read-only: "%SYSTEMROOT%\sysnative\windowspowershell\v1.0\powershell.exe" -ExecutionPolicy Bypass Set-Location "$env:ProgramFiles\FOG\tmp\7zip"; & ".\install.bat" # autofilled

It works like a charm

Maybe it should go in FOG documentation as an example

The third party repo I mentioned is there https://gricad-gitlab.univ-grenoble-alpes.fr/legi/soft/trokata/winsoft-main/

LEGI is a French research lab, and the repo is under MIT Licence. I am not the owner, but it’s a great work. I will explain more about that later.

I found the issue!

The udpsender path on my system was “/usr/sbin/udp-sender”

The path that is set within config.class.php is:

define('UDPSENDERPATH', '/usr/local/sbin/udp-sender');

I ran the following and restarted the FOGMulticastManager to resolve:

sudo ln -s /usr/sbin/udp-sender /usr/local/sbin/udp-sender

And we have logs now! Time to begin multicast testing 🥳

@Tom-Elliott thanks for the quick response. No joy though.

I’ve been and tried an Ubuntu live iso with a 6.14 kernel from the Ubuntu Concept Snapdragon Elite branch (https://discourse.ubuntu.com/t/faq-ubuntu-25-04-on-snapdragon-x-elite/61016) and even that doesn’t boot - though it gets as far as telling me it can’t create a device tree. So I guess I’m just going to have to be patient while upstream gets this whole SoC working.

@Tom-Elliott Yes this did work. Thank you for your quick action.

@BrightPipe Can you post the snapin?

This isn’t something FOG is doing, though you already suspect that as well.

So seeing the snapin file, I’m guessing it’s using some method that’s effectively saying “set all the things” and the snapin is set to only set “specific” things.

Since the action is effectively “setting all the things” it’s resetting the other things you didn’t intend.

Seeing the snapin and the actions involved will be most beneficial at least to understand what’s happening. We may not be able to fix the issue but at least we could all better understand the problem and maybe think of ways to troubleshoot and hopefully narrow down whats wrong.

At cursory glance, it feels like the snapin is misconfigured in someway. Thought you did say it worked in Windows 10, but not in Windows 11, so it’s also just as possible there’s some functional difference that needs to be adjusted for in the Windows 11 side of things.

@rhysb92 We need more information.

i ask because I have just built a new VM, and installed dev-branch/stable and it completed and I was indeed able to login with the fog/password combination where i then changed the PW.

So I feel like we’re missing some key information.