Hi Justin,

yes this is probably a problem with your browser or has been a temporary issue. The download links work well here.

Best regards
Tobias

I have this exact same issue as well.
All searching for solutions have come up dry.
Let's hope we get an answer soon, otherwise I need to force the students to install this on their PC and get me their IP

Is this project dead?

Hi,

me , too, i have problems to view logged in users in RDP-Sessions on win 2019 and win2012R2 Servers. I'm using default config. Veyon Master is showing computernames and the Name of logged in user at console, but not of the RDP-Users, not on 2012 R2, 2019 and not on Win10. On the Clients / Terminalservers the VeyonClient shows the ports e.g. 11102 but only the client-session of the console shoes "connected to ....". In the other RDP-Sessions the clients shows a different port (e.g. 11102) but not wether it is connected or not. On the Master-PC a telnet to the specific port of the clients works.
All antivirus and firewall settings are deactivated for testing but no positive result.

What else can be the problems in connecting from ussersessions to the master?

(veyon 4.3.5 on windows 2019, 2012 and win10)

Thanks in advance

Hi, As it seemds this isnt possible given lack of responses, is there a feature request area i could request this feature?

Thanks

@tobydox thanks !

pi@pishare:~ $ gpg --keyserver keyserver.ubuntu.com --recv 49ABD150D5D0DCC6
gpg: keybox '/home/pi/.gnupg/pubring.kbx' created
gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory
gpg: connecting dirmngr at '/run/user/1000/gnupg/S.dirmngr' failed: No such file or directory
gpg: keyserver receive failed: No dirmngr
pi@pishare:~ $ sudo apt-key add 49ABD150D5D0DCC6
gpg: can't open '49ABD150D5D0DCC6': No such file or directory
pi@pishare:~ $ sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys 49ABD150D5D0DCC6
Executing: /tmp/apt-key-gpghome.S0DQJqUJie/gpg.1.sh --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys 49ABD150D5D0DCC6
gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory
gpg: connecting dirmngr at '/tmp/apt-key-gpghome.S0DQJqUJie/S.dirmngr' failed: No such file or directory
gpg: keyserver receive failed: No dirmngr
pi@pishare:~ $ sudo apt update
Get:2 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Hit:3 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Get:1 http://ppa.launchpad.net/veyon/stable/ubuntu xenial InRelease [18.0 kB]
Hit:4 https://apt.syncthing.net syncthing InRelease
Err:1 http://ppa.launchpad.net/veyon/stable/ubuntu xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 49ABD150D5D0DCC6
Reading package lists... Done
W: GPG error: http://ppa.launchpad.net/veyon/stable/ubuntu xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 49ABD150D5D0DCC6
E: The repository 'http://ppa.launchpad.net/veyon/stable/ubuntu xenial InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
pi@pishare:~ $ sudo apt update 2>&1 1>/dev/null | sed -ne 's/.NO_PUBKEY //p' | while read key; do if ! [[ ${keys[]} =~ "$key" ]]; then sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys "$key"; keys+=("$key"); fi; done
Executing: /tmp/apt-key-gpghome.t7YjvuNZwF/gpg.1.sh --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys 49ABD150D5D0DCC6
gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory
gpg: connecting dirmngr at '/tmp/apt-key-gpghome.t7YjvuNZwF/S.dirmngr' failed: No such file or directory
gpg: keyserver receive failed: No dirmngr

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.