The problem is a minor bug in Veyon Configurator which sometimes pre-populates the key name dialog with the key file name including the directory name (which of course contains (back)-slashes). Simply shorten the input to the actual key name (e.g. "teacher") and everything should work as usual. The issue will be fixed in 4.7.2.
in it. It is then able to launch the veyon server without problem, I am then able to see and control the machine when a LDAP user is logged in. It is not totally satisfying as as it is launched by the user itself, it can also be killed by them. Beside the fact that they don't nowadays know that they can kill the server and how they can kill it, I am sure that my pupils will one day know it. So I'd like to make them unable to stop the server.
Preceding the command by sudo (using the line "Exec=sudo veyon-server" instead of the one in the file) and making the users being able to sudo it in sudoers file does not work because the superuser cannot launch apps that deals with X11 session (surely I don't know how) ... Is there a way to launch veyon-server by root without problem ? I suppose that it is the veyon-service's job (but not working in my case).
You have to change the service configuration (on the target machine) so that it uses Active session mode. This will make the Veyon Service launch the Veyon Server for the currently active session, no matter if it's a console or an RDP session.
If you require support for multiple RDP sessions, consider activating the Multi session mode and using the NetworkDiscovery add-on to see all (even dynamically changing) sessions in Veyon Master.
@mscdaddy30EDIT: So I figured out how to solve this problem! I installed Veyon via the apt command from the repository and this version had the issue with the service not staying between login sessions. Once I downloaded the .deb file from the website and installed it, the problem went away! The only criticism I have is that there is not a way to remove the "master" portion of the install. Fortunately, the Master that shows up in the start menu requires elevated privileges so the kids cannot access it.
Il se base sur l'adresse MAC pour le démarrage des machines, mais à ma connaissance, après c'est le nom ou l'adresse IP.
Et chez moi sur un parc machine de 250 avec 600 profils utilisateurs qui tournent sur les postes, il y a des soucis avec les noms d'hôtes qui se mélangent même après un nettoyage du cache.
Je n'en sais pas plus sur les conditions techniques précises, si ce n'est que plusieurs prestataires de maintenance en sont arrivés à la même conclusion alors qu'ils auraient souhaité ne pas passer en resa d'IP... Le sujet m'intéresse grandement, ainsi que les possibilités de mettre en place un fonctionnement adapté à un emploi du temps des groupes d'utilisateurs de l'AD...
That's indeed a very special issue we've never seen before. First of all it looks like you're running Windows 7 which unfortunately is not supported by Veyon any longer. Does the issue appear with other Win10 computers as well? Does the affected computer have a special display configuration (color depth, resolution etc.?) Which version of Veyon is installed on the computer?
@tatanas Any chance you can test with the internal VNC server and disable the external UltraVNC server instance temporarily? That would allow us to figure out whether your issues are related to the external VNC server feature in Veyon.