Ok, thanks for the reply! One specific question: are you using access control together with the LDAP/AD integration?

If you are using Linux, you can install Xmacro. With Xmacro you can create macro files with keystroke sequences. Not only just regular keystrokes, but you can actually make keystroke combinations like Alt F4 etc. Then you call the macro files with a shell script. I use this a lot to manipulate the buttons on the active applications on the students screens. I really love my Alt F4 script, if a student opens a browser I can immediately close it!

To be able to do this you should be familiar with shell scripts, and study the documentation for Xmacro.

Hi @moises-epia
please see the documentation at https://docs.veyon.io/en/latest/admin/introduction.html#network-architecture and https://docs.veyon.io/en/latest/admin/reference.html#network for details on the network ports used by Veyon.

Hi @ekblu28

Veyon should work through VPN even though the internet connection can be a bottleneck. While the monitoring mode should work regularly the demo mode likely will be very slow.

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😁