I have the same problem. I tried everything. I asked for professional support. The problem still remains. I think the last upgrates of Windows 10 don't support Veyon 4.4.2 version 64 bit.

Finally got it to work with 4.2.2. Setup is the following: lab with a Master. The Master will not be used by students, logon auth is unneeded and causes other issues. First install Veyon with the master on a machine and generate a key pair (I just name it "teacher"). Export them to another folder (I put them on the file share for distribution later). Generate locations and computers in Location & Computers. You'll have to install the clients with either a config file included or utilize veyon-wcli to change authentication mode. The config will not set the key access control group, you'll need to set it with veyon-wcli. By default it pulls the highest privilege group available when the key pair is created (Administrators), but you'll actually want to have it for the lowest (Users). //Config for Master/Client General Authentication Method: Key file authentication Computer Access Control x Grant access to every authenticated user (default) Authentication keys Set Access group to "Users" //Imports public key "C:\Program Files\Veyon\veyon-wcli.exe" authkeys import teacher/public \\fileserver\share$\folder\teacher_public_key.pem //Imports private key (Master Only) "C:\Program Files\Veyon\veyon-wcli.exe" authkeys import teacher/private \\fileserver\share$\folder\teacher_private_key.pem //Sets access group to Users (works with domain login as well) "C:\Program Files\Veyon\veyon-wcli.exe" authkeys setaccessgroup teacher/public Users //Sets access group to Users (works with domain login as well) (Master Only) "C:\Program Files\Veyon\veyon-wcli.exe" authkeys setaccessgroup teacher/private Users One gotcha I learned is that the Veyon uninstaller will not remove keys. If you generated new keys for a new version but with the same name, the old ones will have to be deleted first because the import will not work if a file with the same name exists. //Remove the Veyon folder from ProgramData rmdir /s /q "C:\ProgramData\Veyon" When you import the keys with veyon-wcli the folder structure will be created. Now you've Veyon running with key authentication.

Hi, I have the same issue, but it is our school setup thats blocking it. I believe the Power On uses Wake-On-Lan which is often blocked in organizations. It uses a "magic" packet that is sent to the machine to wake it up. Firewalls/Network Switches often block the port (UDP 7 and 9). You also have to ensure the Wake-On-Lan feature is enabled in the BIOS of the PC. Third thing is to remember that Wake-On-Lan uses MAC Address so I suspect you need to add them all into the config file (Locations/PC Names bit) Good luck

no one? can get this to work, keep saying log in as admin. And that is whats i am doing

I have the same issue, when I'm not launching Master without admin rights, I'm told that I don't have access to this network. Launch with administrator rights - just fine. Using LDAP and LDAP tests for access are all OK.

Simply pick a computer (yours maybe) that will be the lead "Master" and install the appropriate version per your OS (32bit/64bit) using all the default settings. Run the same installer on every client/student computer but uncheck the box Veyon Master box during install. Take not of the computer's name and the MAC number. They all need to be able to communicate so it's ideal if they're all on the same domain. On the Master computer, open Veyon Configurator and click Locations & Computers. If you have multiple locations, like many buildings on a college campus, you create locations on the left side, like you may use folders in File Explorer. On the right side you add the client computers for each location. Click apply and you're done. There are other security settings, LDAP settings and things you can adjust as needed for your environment.