Windows 11 | 65x HP Z2 Tower G1i | UPDATE -
-
@Tom-Elliott
Yes—I can use the system again now. -
@Tom-Elliott
I do a update …
I take the url an copy it to my browser
The url changes automatic and I get this:
What is the sense of this ???
-
@kratkale what do you mean? The ui refactor is intentional. This is just progressing to make it more inline.
-
@Tom-Elliott
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? -
@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
