I do not yet know this product so all I can suggest is to try building Veyon from source on this platform and see how it works. In general compatibility with recent versions of all major Linux distributions is quite good.
Welcome to our forum! You should try to install the Veyon package from our PPA: https://launchpad.net/~veyon/+archive/ubuntu/stable/ After installing you can run Veyon Configurator to configure the local installation. If you're running X11-based sessions the Veyon Server should be started automatically for user sessions.
I have the 'Show notification on remote connection' option selected but do not see any obvious notification displayed at the remote computer.
Hovering over the Veyon icon will reveal active connections (two connections listed for the master computer) but there is no context option to list active connections and no icon color change that would signal the presence of an active connection.
You could create a Windows scheduled task (taskschd.msc) at each master computer.
The idea would be to maintain a master configuration file in a shared network folder having read access for the EVERYONE group. The scheduled task would be configured to use the NT AUTHORITY\SYSTEM account (SYSTEM) and run as a batch file from within the same shared network folder at user log on.
First, create a global master computer containing all room and computer information. This could be done through importing various room level .csv data files.
veyon-cli networkobjects import \\servername\sharename\foldername\Room_A.csv format "%type%;%name%;%host%;%mac%"
veyon-cli networkobjects import \\servername\sharename\foldername\Room_B.csv format "%type%;%name%;%host%;%mac%"
veyon-cli networkobjects import \\servername\sharename\foldername\Room_C.csv format "%type%;%name%;%host%;%mac%"
veyon-cli networkobjects import \\servername\sharename\foldername\Room_D.csv format "%type%;%name%;%host%;%mac%"
Next, export the global master computer configuration.
veyon-cli config export \\servername\sharename\foldername\mstrcnfg.txt
Thank you for sharing your obvervations! It looks like there's indeed a setup-specific memory leak caused by some kind of erroneous loop inside the server. My first try would be to disable the VNC server option "Use Desktop duplication" engine since this already solved issues in other RDP environments. Alternatively you could try installing an external VNC server, make it listen on localhost only, configure a password and configure Veyon to use that external VNC server instead of the builtin one. Last but not least: try the latest 4.5.0 release since there have been updates to all components, including the builtin UltraVNC server.