Gah! Ignore me.. That didn't work. I'd mistakenly unticked the "show notification when an unathorized.." box I'm just going to roll with it for now. I'd still like to know how to stop it remembering my previously connected clients, though. At the moment, it looks like I'm going to have to replace the shortcut for Master with a script which deletes the per-user settings file and then runs Master.. Not ideal.

I'm not currently seeing this with a new install of 4.4.0. Is it perhaps worth trying to wipe your settings on a pupil PC, and then re-import settings/key exported from a newly installed 4.4.0? Disclaimer - I haven't upgraded from any previous versions, and my testing is still very recent and limited. Cheers, Gerard

Sounds like a perfect solution!

And that is realy frustrating Any fix for that ?

@tobydox Hello tobydox I have created an environment variable in the operating system with a value equal to 2 SET VEYON_SESSION_ID = 2 And also in the veyon-client environment. veyon-cli config set Service/VEYON_SESSION_ID 2 My session ID is two QUERY SESSION SESSION NAME USER NAME ID STATE services 0 Desc rdp-tcp # 2 administrator 2 Active console 3 Conn rdp-tcp 65536 Listen And in no case have I managed to make the screen that shows to the students the session in which the teacher works. I have also test with the new version of Veyon 4.4.0 I would like to remind you that both the students and the teacher are working on their own virtual desktop connected by RDP, that is, they are all in session 2 of their own virtual desktop.

Are you running Windows 10? 32 or 64 bit?

The documentation on multi session mode at https://docs.veyon.io/en/latest/admin/reference.html#refmultisessionmode has been improved to reflect information on how to access RDP sessions in general. Also the (currently very basic) RDP support will be further improved in future Veyon releases.

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.