I use veyon in some of our labs and it works well. You can install veyon master to the teachers machine and client to all student machines. It requires the users account and password in order to open veyon master (so that students can not open it). You basically configure a class on the configurator on the master version using machine name or IP address (we use machine name and it works well). We do use 2 screens at the teachers desk so one for them and one to watch students
Hello, yes BUT this is not powerfull when the master have 1 monitor and slave 2 monitors.
I've create a Github issue with more explications : https://github.com/veyon/veyon/issues/620
I guess the question is whether or not it matters which one of these I choose for the private and public keys. I'm trying Administrators for Private and Users for Public.
thanks for de clear information. Ik guess you'll have an idea of my next question now 馃檪 : is a chromeOS client on the roadmap (this should be an enormous added value for schools with 1:1 chromebook projects) and if so, will a chromeOS management licence be required?