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 No problem, you can't be on dev and forum at the same time Your job is really helpful for a lot of people, thanks for that. I'd like to be more useful here on the forum, but not "good" enough yet with veyon to help much people. Regards ET

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

@tobydox said in Veyon for Raspbian?: this is an interesting use case! Building packages for Debian (no matter which platform/architecture) isn't that complicated, just have a look at our README file. Besides that we recognized the growing demand for armel/armhf/arm64 binary packages so we might provide them in the future as well. Be aware that Raspbian has its own non-standard ABI. In standard Debian armhf means ARMv7 instructions with hardware floating point. In Raspbian all Debian packages have been rebuild with ARMv6 instructions, for compatibility with older Pi that do not understand the newer instructions. They do are compiled with hardware floating point, so it is not armel either. Any chance you will be maintaining an official Debian package submitted to Debian at some point instead of the current situation? That would simplify things. Let the Debian derivatives do the compiling, and allow users to just apt-get it.

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

Thank you very much for your feedback!

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

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...

@DrewLoker this is already possible - simply enable the "Show confirmation dialog for potentially unsafe actions" option in the master configuration page in Veyon Configurator - see https://docs.veyon.io/en/latest/admin/reference.html#behaviour for details.

@Tuisku there was indeed an old bug which always made the Veyon Server crash with language set to Hebrew. This has been fixed in the code and a temporary test release is available at https://github.com/veyon/veyon/releases/download/v4.2.1/veyon-4.2.1.26-win64-setup.exe - feel free to test and report back! @CeoSoares Please do not hijack threads with different topics You can open a new thread or create a detailled bug report in our bug tracker at https://github.com/veyon/veyon/issues

Hello everyone, finally started to deploy Veyon, we come from Netsupport. We have about 1400 students, 170 teachers, 50 in the administration, linux servers and about 300 Windows computers. Jens

@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.