@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
