I just switched in General from "use system language" to English US... My local language GUI was really annoying in both Configurator and Master, and in older versions there was no English option for some reason.

In 4.1.0 I just noticed there is English. The moment I switched to English and reopened Configurator, clicking "Start service" worked right away 😮

The line
[WARN] WindowsServiceControl: 'VeyonService' could not be started.
is not showing anymore in .log

So far no errors, everything looks fine. Going to install it on few class PCs and see if Master works without issues.

@tobydox windows 10 64bit visual studio 2017 community edition

Can you try again with Veyon 4.1.0?

Does upgrading to Veyon 4.1.0 help?

@joki issue is fixed in Veyon 4.1 final - thanks for reporting and discussing in our issue tracker!

You can find old downloads the the official release page at https://github.com/iTALC/italc/releases - however we strongly advise against using it due to potential security issues. If there's something which is stopping you from using Veyon, please tell us! We'll try to find a solution 🙂

Hello @Technikus
as this is an international English speaking forum I'll reply in English - I hope this is fine to you! 😉

It's correct that our packages are not signed yet but you should still be able to use them. The final 4.1 release also has a few fixes related to RPM packaging - I invite you to test this release.

@tobydox That is fantastic thanks for the update!!!

Any other ideas ?

Thanks

Hi @Joel
thank you for your feedback! We indeed had a bug in the wake-on-lan module which could lead to application crashes. It has been fixed in 4.1 RC (4.0.92) and will be fixed in upcoming 4.0.8 release as well.

Hi @ulrick
which version of Veyon are you using? Which operating system and version is running on master and client computers? Do your keyboards have special function buttons?

@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...