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.

I am having this same issue. I used Veyon 4.4.1 and now I get the C++ Runtime error. The master PC is Windows 7.

Hi.. Apologies for the delay in getting back to you. I'm afraid that I don't use the group member aspect, so can't really help with that one. Here are grabs of my config: [image: 1594980838069-access04.png] [image: 1594980837973-access03.png] [image: 1594980837862-access02.png] [image: 1594980837753-access01.png]

The line ending issue has been fixed in 4.4.1 (no more duplicate line endings + proper CRLF line endings on Windows). Thank you for sharing your findings here!

In fact, it seems commands like C:\Program Files\Veyon\veyon-service.exe restart have absolutly no effect. I tried with service stop (and server too) on the client, and it changes anything in veyon master : the client is still here and responding. It can explain why my tests don't work... What am I missing ?... E.T.

Stranger and stranger The connection notification goes away if the end user clicks the OK/close button. On the previous version of Veyon which I did my initial tests on - the connection notification would reappear if the pupil clicked the OK/close button on the notification.