Hi @moises-epia
unfortunately I don't speak Spanish so if possible please write in English so we can help you 😉

Hi @olivier,

have you figured out which processes are started? Does the problem disappear if you stop or disable the Veyon Service?

Hi @ap123

have you solved your issue in the meantime? If not, how are your computers and locations organized? Are you using computer groups, location attribute in computer objects or OUs/containers as locations?

Hi @nothingsmine

in order to solve your issue we'd need more information such as a detailled error message. Did you follow the instructions as given at https://launchpad.net/~veyon/+archive/ubuntu/stable i.e.

sudo add-apt-repository ppa:veyon/stable sudo apt-get update

Hi @pbolton
you can't select the monitor for demo mode but you can disable multi monitor support on the master computer through Veyon Configurator. Once disabled the demo server (which uses the screen data provided by the local Veyon Server) will broadcast the primary monitor only. May be this solves your second issue as well.

That's an interesting observation! Are you using the key file authentication? Can you try to change the update interval to a lower value? Is any kind of access control configured?

@tobydox That was it! But why? If I'm running a 64bit OS, shouldn't I be able to run 64 bit apps? I uninstalled the 64 bit Veyon and installed the 32 bit one and it now works correctly. Thanks Toby.

@FailedStorme Please try again with Veyon 4.2.3 which includes multi-session support which should also work for multiple RDP sessions. The Server instances will listen at the network ports 11101, 11102 etc.

Can you please update to Veyon 4.2.3? It may contain bug fixes related to your issue. Are you using access control or LDAP/AD integration?

Thank you very much for investigating this issue! Your analysis helped me to find the bug in the code quickly. I uploaded an intermediate build including the fix at https://github.com/veyon/veyon/releases/download/v4.2.3/veyon-4.2.3.5-win64-setup.exe - after updating you should be able to use description as location name attribute with computer groups.

Hi @mrpeel
have you tried using the context menu to activate features for individual computers? The buttons in the toolbar always activate features for all shown computers.

It seems that this is a limitation in 4.2.2 and will be fixed in 4.2.3. see this post on GitHub

Problem was caused by anonymous AD bind. Even though Veyon reported anonymous bind was successful, auth bind had to be used using domain\user + password syntax. All good. Case closed.

Thanks you. It's works.
My teachers are happy😁

After several tests, I have verified that the service does not start only on the first logon of an AD user on the computer. If someone else has this problem, the solution is to edit the /etc/pam.d/systemd-user file and add the line: @include common-session just below the line @include common-session-nonintercative. Because it is in the "common-session" file that the creation of directories for AD users via PAM is usually configured.

Hi,
I've already connected the six other PCs via their IP-address. The problem is that the other four computers are connected to the network via another router/ access point. This puts them in another IP-address range (192.168.x.x) while all other computer are on the 10.18.x.x range. I've already tried to ping them but that doesn't work.

I think a little setting inside the router is prohibiting this connection but I can't find out which one. If I could I would just use a switch instead of router/ access point but my IT-department can't give me this because the access point is essential for other teachers their classroom.

Ask your IT if he have installed the interception driver? Without them Veyon can't lock keyboard and mouse.
Demandez à votre informaticien si il a installé le pilote interception? Sans ça Veyon ne peut pas bloquer le clavier et la souris.