Hello I launched a test in a room of my school and it seems to be OK thank you for your work some suggestions for devolppement: features of italc that were useful: when several rooms were set up, we could choose directly a room to display in one click, When a click held on a thumbnail image of a computer, an enlarged vision of the screen was proposed. Good luck and keep it up Fred

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

Hi Thomas, SSO is currently not supported so you'll either have to allow anonymous bind for read-only operations at your server or create a dedicated account for readonly access. As of Veyon 4.1 all passwords in the registry are not saved in plaintext any longer so at least they cannot be read out at first glance. Implementing SSO in general would be a quite huge task, especially when doing this for all supported platforms so if there's a sponsor we could possibly work on it. Best regards Tobias

Please update to 4.1.4 which fixes the issue. Try to uninstall Veyon before which should also restore the input devices.

Can you please try version 4.1.4?

FYI: the issue has been fixed in 4.1.4 which sends WOL packets to all available network interfaces / broadcast addresses

@tobydox In fullscreen Demo mode. Thnks for reply.

It could be an issue with the builtin VNC server. You can try to disable the Enable capturing of layered windows option in the service / VNC server options. Altering the other options could be worth a try as well. Which update interval have you configured on the master side?

Regarding logon authentication: it is not necessarily for local users only. It uses PAM so if your systems are configured to authenticate LDAP users via pam_ldap, pam_winbind or whatever Veyon should be able to authenticate any user in your network environment. I appreciate your suggestion to add native LDAP authentication support though. Currently LDAP is "only" used for determining group memberships as well as retrieving computer and room information. Once authentication works you can configure access control such that only members of special groups are allowed to access client computers. For this to work the LDAP module has to be set up to properly resolve groups and group memberships of a given user. Use the integration test for this. There's currently a bug in all versions including 4.1.3 which may return all groups for a user if a user can't be resolved in the directory properly. This will be fixed in 4.1.4. When enabling the Perform access control at program start option (https://docs.veyon.io/projects/admin-manual/en/latest/reference.html#behaviour) even the Master program can be started by authorized users only.

Yes there should be no limit if you have enough RAM, see http://docs.veyon.io/en/latest/admin/installation.html#hardware-and-software-requirements for details. If you encounter CPU usage issues you can increase the thumbnail update interval in the configuration.

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!

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.

Hi Toby, Thanks for your reply, but I feel stupid, I was using the veyon-ctl command to reset config within a regular Command Prompt window ... (I still don't get why I need admin privilege when I'm already admin). Opening a Command Prompt as Administrator was what I've miss earlier to reset the config and push the new one. All your suggestion were done it was Windows that trick me (again) Sorry for the useless noise. and thanks again for your reply.