I feel that there is something to do with Windows 10 compatibility. I have just purchased 45 Dell Computers with Windows 10 Education 1709. Not a single one running 4.2 will reveal the desktop in the Thumbnail. All the Windows 7 machines with an identical setup are working perfectly.

@tobydox I just updated to version 4.1.4. indeed the problem was solved. Thank you!!

@tobydox I just upgraded but won't have students to try it out for another week. Fingers crossed! Thank you.

Thank you for your investigations! I opened an issue at https://github.com/veyon/veyon/issues/420 so we can do further investigations and finally fix the issue.

Hi Tobias, I just described a similar issue here: [https://github.com/veyon/veyon/issues/455](link url) Thanks in advance, Julius

I had the same problem. Curtis says true but you need to check another setting in the DHCP. In windows server, in your DHCP, select your scope and go to the properties. Select the DNS tab and activate the dynamic update DNS with this setting: Always update PTR and A DNS. On Veyon, you can use the computer's names without IP address. (i don't use DNS suffix) (Same thing in french) J'ai eu le même problème, Curtis dit vrai mais tu auras besoin de vérifier les paramètres du DHCP. Sur Windows server, dans la console DHCP, sélectionne ton étendue et va sur les propriétés. Choisis l'onglet DNS et active les mises à jour dynamiques DNS avec les paramètres: Toujours mettre à jour dynamiquement les enregistrements PTR et A DNS. Sur Veyon, tu peux utiliser les noms des ordinateurs sans les adresses IP (je n'utilise pas le suffixe DNS) Yohann

Hi How's the testing going? Any chance of uploading your test build as it's something I am very interested to try out too. Thanks طراحی سایت

I just switched in General from "use system language" to English US... My local language GUI was really annoying in both Configurator and Master, and in older versions there was no English option for some reason. In 4.1.0 I just noticed there is English. The moment I switched to English and reopened Configurator, clicking "Start service" worked right away The line [WARN] WindowsServiceControl: 'VeyonService' could not be started. is not showing anymore in .log So far no errors, everything looks fine. Going to install it on few class PCs and see if Master works without issues.

Tested 4.1.4 still the same problem, when I click the test access button and type "asdf" so not a valid user I still get user has access to control master...

@joki issue is fixed in Veyon 4.1 final - thanks for reporting and discussing in our issue tracker!

Can you try again with Veyon 4.1.0?

Perfect, thanks for the feedback!

Not sure it is the same problem as the one I reported, but try to use IP address instead of computer name. I was able to fix all my connexion problems, even if I do not like depending on fixed ip addesses Nicolas

Thanks for reporting this issue. We'll add the missing code for disabling power saving mechanisms.

@fred Sorry for the late answer. I was on vacation the last days. Yes that´s it. The Veyon Master should be able to lock or unlock a Computer (Veyon Client) without being able to see what the connected user ist doing.

@tobydox , thanks Toby, a big improvement with usability now

Any other ideas ? Thanks

So, to make sure I understand correctly, an incremental upgrade is ok? Like, I can install 4.1.3 to the master, but not to the clients and it will be ok? Does 4.1.3 need to ever be installed to the clients for any improvement? Thanks!

Good to know, thanks for that info

Hi everyone, It a painful, but i manage to get my keyboard back. It wasn't working in safe mode, I try the repair option, it took some times but my laptop is working again. I haven't get the chance to re-install Veyon on it because it start working just in time for class. I'll try to "clean" the laptop before trying to re-install Veyon. Thanks again for the help. 3 hours later I can confirm that the laptop is working as a charm and I was able to install Veyon on it.