FOG server: Debian 12
FOG storage nodes (x5): Linux Mint 22.1
All on FOG Stable: 1.5.10.1667
Issue: Clients, seemingly at random (or I just haven’t pinned down the context) boot into Debug Mode instead of automatically deploying or capturing. In those cases, running fog.download or fog.upload works correctly, step-by-step, but obviously isn’t great for mass deployment.
I’m primarily working on deploying Windows 11 to Dell 3430 series PCs, but the Debug Menu problem also occurs with our older, stable Windows 10 / Dell 7010 images.
What I’ve done to get myself into this:
I inherited a network / system that was running FOG 1.5.9 on Debian 9. I used it as-was for several months until I saw a schedule break that made sense for upgrading.
I made new installs of Debian 12 (on the FOG server) and Linux Mint 22.1 (on the 5 storage nodes) on new(er) PCs. Then I copied the old /opt/fog and /images directories to the new PCs, as well as the existing mariadb database. Finally, I ran the 1.5.10.1667 install script on each, it using the pre-existing .fogsettings.
Coming at this upgrade from my oblique and ignorant angle, I did run into several problems with permissions, etc, but learned a fair bit about FOG in the process of head-banging. But now I’m stuck on this Debug Mode issue. I’m really sorry that I haven’t figured out what makes it (deploy/capture) work automatically (no Debug) sometimes and not others. My best guess so far is it might depend on which storage node gets selected for the task.
I think I’ll power down the 2 storage nodes that I know have been used when Debug Mode engaged and work from there. But I’m hoping someone here will immediately recognize this problem and say, “Hey Dummy, just do [this simple thing] right!”
Thanks in advance.
PS: yes, I know Mint isn’t supported, but other than one package install glitch, I’ve seen no obvious problems.