Nevermind, there's a problem in the LDAP subsystem causing certificate settings not being applied properly when using SSL/LDAPS. TLS should work fine though. We're working on a fix for the next release.

There's no builtin auto updater but if your Veyon deployment is automated properly you simply have to exchange the installer file. See https://docs.veyon.io/en/latest/admin/installation.html#automated-silent-installation for details.

Unfortunately this is a 3rdparty issue which still requires a fix. Once the Interception driver has been fixed we'll incorporate the new version.

Do you mean 100 megabit/s, i.e. 12 MB/s? If so, that's IMHO an acceptable amount of traffic for monitoring 45 clients. Besides increasing the update interval there's currently no possibility to further reduce the traffic. Increasing the update interval will not decrease the traffic linearly since less frequent updates might cause bigger updates (i.e. fullscreen updates of partial updates). We plan to add lossy compression methods witin the Veyon 5 release series (2021) which will further reduce the required traffic.

Yes, you can use the veyon-cli tool: veyon-cli config set ExternalVncServer/Password 12345 See https://docs.veyon.io/en/latest/admin/cli.html#configuration-management for further details.

Hello I know that Win7 is no longer updated .. but I am a teacher and administrator of a high school. until last year the delivery of computers was still in win7 (license W10 downgrade to W7) I have about 1300 computers including about 1000 under W7 .. I paid a few hours to maintain the network (this is not my main job, since I am a teacher). the objective is to pass to W10 the whole computer park but it will be done in time ... because I do not have that to do ... (creation of accounts, software update, WSUS, server anti-virus ... impossible to migrate 1000 computers in a short time ... because I have some licensed software, the installation time is 2 / 3H per computer and in some sectors it is 2 or 3 software to install by machine ... I found a solution that suits me for the moment Fred

Same issue here. Seems to have started in version 4.3.4.

Regards, I have exactly the same problem, There is no way for user authentication to work. I always get the error message. I want to use this authentication method without generating Keys. I am using Linux Mint 19.

@tobydox said in Room configuration with Active Directory: Once the rooms get listed properly switching to the room automatically should be working as well. An important requirement for this to work is that Veyon is able resolve the local computer to an AD/LDAP computer object (by performing reverse DNS lookup and searching for the computer name in AD/LDAP) and find the corresponding room. Hello Tobias! Is this limitation with Veyon still current or is version 4.3.3.0 now able to use sub OUs of an active directory? Right now our Active Directory is configured with sub OUs to splitt between notebooks and pcs. If it´s still current: What about the subscriber edition? Can you show where i can get more informations about it? Best regards from germany Norbert

Hey Laura! Are we talking about Windows Computers? Are they member of an Active Directory? If can answer both with yes it´s really easy: Veyon can be installed by using a script which can be used as a startup script. By default (you can change this too if you want) Veyon is installed under C:\Program Files\Veyon so it´s a simple if exist query in your startup script: if not exist "%Program Files%\Veyon" \server\share\installer.exe /S Important! For a silent installation you must use the /S switch with UPPER letter, otherwise it´s not installing. There are some more usefull switches /NoMaster Just install the client /ApplyConfig="\server\share\current.json" allows to specify your configuration I hope that´s usefull for you! Norbert

Assuming it's a problem with the built-in VNC server malfunctioning I installed UltraVNC on my master machine. Installed the service. Configured password and started service. Set Veyon to use External VNC server on port 5900 with the same password. Et voila - it works now. Somethings just not right with the built-in UltraVNC server.

As far as I can tell Veyon just uses local authentication by default. So any local username and password will work.

@mpschwe said in Using two screens and a Beamer as a Teacher: not sure on windows It uses a build in version of uvnc.com on windows