Windows 11 | 65x HP Z2 Tower G1i | UPDATE -
-
@Tom-Elliott
In my workflow, it would be really cool if I could assign a single snap-in directly from the Basic Tasks…
-
@kratkale You can, but it falls under “Advanced Tasks”.
-
@Tom-Elliott
Yeah, that’s how I do it—but it always takes so many clicks—I think it would be great as a basic feature. -
@kratkale The problem is Snapins are not a basic feature:
They require the FOG Client + knowledge of what a snapin is and does (at a base level)
The “basic” for FOG is imaging at its core.
Snapins are a way of getting the machine to do additional things: install software, run a script (or set of scripts) etc… - Please note I’m not saying it’s not a useful feature, just saying that it’s more than a “Basic” thing.
You can do a curl request to schedule a snapin task which might be better, though you would need to know what MAC Address to use for the host in question.
-
@kratkale said in Windows 11 | 65x HP Z2 Tower G1i | UPDATE -:
I mean, why do I need to connect to the web interface? I don’t have to do anything there during the update, do I?
The URL you see is because the installer doesn’t know if (or not) there’s a Schema Update.
It always shows that on every install. If you don’t want to see that, now that FOG is installed, you can just run your installer with:
sudo ./installfog.sh -yIf there is a schema update, this will do the update for you automatically, if not, the doesn’t matter, the main update just goes through the normal process.
-
@Tom-Elliott
Automatic snap-ins (connected to the group or the PC) don’t always work well, e.g., when the PC is busy with itself and the Microsoft ecosystem after cloning. For example: the PC isn’t ready for the snap-in yet because it’s currently installing an update, isn’t in the domain yet, etc.
That’s why, over the years, I’ve gotten into the habit of first checking whether the PC is in the domain, letting it boot up completely, and only then running my “one” snap-in per PC. In that single Snap-in, I gather everything I need to set up the PC: for example, a student PC needs a Veyon client, the student proxy server, etc. => Student Snap-in; a teacher PC needs the Veyon Master and the fast teacher proxy => a separate Snap-in for teacher PCs -
@Tom-Elliott
I think sorting by name would be better than sorting by ID
-
@kratkale I’m having it do a sort on “name” then by start time (newest first) if there’s a tie.
I think it is because the snapinLink is what you see as the name, and that link built by sorting by the IDs rather than the names.
For the active tasks table I figured sorting by the time adds a level of understanding so you always know who was the newest one to the party (so to speak).
-
@kratkale This has now been pushed.
-
Sometimes I come across these “ghost” tasks—I have no idea how I end up with them.
-
@Tom-Elliott
Unfortunately, the “Reset Encryption Data” feature doesn’t work very well for me. Right now, it seems like I have to press the “Reset” button during the cloning process every time I clone a PC. If I don’t, the Fog Client doesn’t work, and I have to go to the PC in person.
To make sure the PCs are still usable, I’ve moved the steps for renaming the PC, connecting it to the domain, and installing the Veyon Client to c:\windows\Setup\Scripts\SetupComplete.cmd. This makes the cloning process go more smoothly for me. I also install the Fog Client at the same time.Despite all these efforts, I’m not getting anywhere:
01.07.2026 18:34:53 Middleware::Communication Download: http://192.168.0.196/fog/management/other/ssl/srvpublic.crt
01.07.2026 18:34:53 Middleware::Authentication Cert OK
01.07.2026 18:34:53 Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before
01.07.2026 18:34:53 Middleware::Authentication ERROR: Could not get security token
01.07.2026 18:34:53 Middleware::Authentication ERROR: Die Datei “C:\Program Files (x86)\FOG\token.dat” konnte nicht gefunden werden.
01.07.2026 18:34:53 Middleware::Communication POST URL: http://192.168.0.196/fog/management/index.php?sub=requestClientInfo&authorize&newService
01.07.2026 18:34:53 Middleware::Communication ERROR: Failed to POST data
01.07.2026 18:34:53 Middleware::Communication ERROR: Der Remoteserver hat einen Fehler zurückgegeben: (401) Nicht autorisiert.
01.07.2026 18:34:53 Middleware::Response Success01.07.2026 18:34:53 Client-Info ERROR: Failed to authenticate, will not run Module Looper.
