@hugo_alva
You can generate UUIDs on your own. Take care to use identical UUIDs for ParentUUID. Besides that I recommend to manage everything through Veyon Configurator. Starting with Veyon 4.1 you can also modify computer and room information at the command line, see https://veyon.io/blog/2018/04/24/network-object-management-cli/ for details

Thanks for the feedback! We'll do more testing with Ubuntu 16.04 in preparation of the final 4.1 release. I'll let you know once we have bug fixes for the problems mentioned.

Welcome to Veyon! I suggest to watch a video on Veyon such as https://www.youtube.com/watch?v=0YimKRncnuw - afterwards you should have an idea of how to get get Veyon running. Feel free to ask specific questions if you're stuck at a certain step.

@bcorn02
Veyon only runs on Windows 7 or higher. XP is not supported any longer, sorry

@dwhitespire
You will need to either add computers manually through the Veyon Configurator or set up LDAP/AD integration to make Veyon fetch classroom and computer information from your LDAP/AD. See our manual at docs.veyon.io for more information

@Micky219
thanks for testing the pre-releases!
@ulrick
did you manage to get LDAP integration up and running?

It usually doesn't harm to have the Veyon Master installed on clients as a properly set up installation won't allow non-teachers to use it anyway. However you can manually delete /usr/bin/veyon-master and /usr/share/applications/veyon-master.desktop in order to remove Veyon Master completely.

You should be able to see other master computers if authentication is set up properly Are you using key file authentication or logon authentication?

@Micky219 thanks for your response. I have tried computer address/IP indicating hostname (without IP and MAC) and it seems to be working...

Hi Tobydox

Thank you very much for your reply, that makes sense I see what you mean.

That sounds good! Many thanks for the great software!

@tobydox thank you!

Which version of Veyon are you running? Which VNC software do you have installed? Can you take a look at the log files in C:\Windows\Temp\Veyon*log ?

Hi @Ben-Ronlund
you're right that in Veyon 4.1 all passwords (also including the LDAP bind password) are stored encrypted in the local configuration. Once you upgrade to Veyon 4.1 and modify the configuration they get encrypted automatically (besides other configuration updates). This means you should save your configuration before upgrading to 4.1 as reverting back to 4.0 will make problems.

Unfortunately Veyon currently is not available for Raspberry Pi (armel/armhf/arm64). You can however build packages on your RPI on your own as described in our README file. We might provide binary packages for RPI in the future as well.

Hi @SamGreff

theoretically you can omit the master computer from the configuration with the drawback that auto-discovery of current room will not work. In your case you can enable the setting "Hide local computer" in the Master configuration page in Veyon Configurator. This should hide the master computer while functioning regularly.

OK I'll have a look whether we can improve the connection timeout settings.

Problem #1.
If they are on the same network, then try disabling your firewall.
If the connection is successful, try to open ports
Problem #2.
Check energy settings to try to solve the sleep mode, it could be an option

Thanks for fixing that in a future release.

The message box shouldn't be a problem (and could be a indicator that it works). Custom positions is not that important - to fix the zoom level will be enough.