Okidoki. => https://github.com/veyon/veyon/issues/448

Hi again, I slept on it, as one says, and I realized there was no problem with UIDs : I just got to generate and include them in the conf. Very often, network based softwares work with agents on clients, that sends its information on server, to be "recognized". I realised there is no such process in veyon, and that a computer's UID is only present on master, the client doesn't even know it. Sorry for that "stupid" question. You can mark as "resolved" For the record : I'm discovering Veyon, and I'm really impressed by its possibilities and its fast evolution. Thanks for your great job E.T.

Does Wake-on-LAN work in general on your computers, i.e. enabled in BIOS / NIC setup? Have you already tried a separate Wake-on-LAN tool? Can you try to disable your firewall temporarily?

Yes I double checked that. I also telnet the port and its not active thats how I concluded it was blocked. Is there another port that it might work on or is that the only port the service runs on?

@tobydox I just updated to version 4.1.4. indeed the problem was solved. Thank you!!

@yasser WOL needs the MAC addresses of the PCs to work. So, you have to supply that info in the configuration.

Which version of Veyon are you using? You can try to disable capturing of layered windows in the configurator in the VNC server settings (select builtin VNC server if not selected) within the Service page.

Welcome to the Veyon forum! If users have admin privileges they usually can change any setting of any application so of course this applies to Veyon too Without admin privileges you can neither run Veyon Configurator nor change the settings in the registry.

Today I worked on improving this so in upcoming 4.1.5 release the toolbar only appears after a delay of about 500 ms and the animation for appearing/disappearing is much faster now so everything should be much more usable now. A test build (4.1.4.10) is available at https://github.com/veyon/veyon/releases/download/v4.1.4/veyon-4.1.4.10-win64-setup.exe If you like the improvements please consider to make a donation to the Veyon project, see https://veyon.io/get-involved/ for details

Today I worked on improving this so in upcoming 4.1.5 release the toolbar only appears after a delay of about 500 ms and the animation for appearing/disappearing is much faster now so everything should be much more usable now. A test build (4.1.4.10) is available at https://github.com/veyon/veyon/releases/download/v4.1.4/veyon-4.1.4.10-win64-setup.exe If you like the improvements please consider to make a donation to the Veyon project, see https://veyon.io/get-involved/ for details

Hello I launched a test in a room of my school and it seems to be OK thank you for your work some suggestions for devolppement: features of italc that were useful: when several rooms were set up, we could choose directly a room to display in one click, [image: 1539350203310-a7f416af-7c9f-4785-af01-d8aca106576a-image.png] When a click held on a thumbnail image of a computer, an enlarged vision of the screen was proposed. Good luck and keep it up Fred

Tested 4.1.4 still the same problem, when I click the test access button and type "asdf" so not a valid user I still get user has access to control master...

Can you please try version 4.1.4?

@tobydox In fullscreen Demo mode. Thnks for reply.

It could be an issue with the builtin VNC server. You can try to disable the Enable capturing of layered windows option in the service / VNC server options. Altering the other options could be worth a try as well. Which update interval have you configured on the master side?

Yes there should be no limit if you have enough RAM, see http://docs.veyon.io/en/latest/admin/installation.html#hardware-and-software-requirements for details. If you encounter CPU usage issues you can increase the thumbnail update interval in the configuration.

So, to make sure I understand correctly, an incremental upgrade is ok? Like, I can install 4.1.3 to the master, but not to the clients and it will be ok? Does 4.1.3 need to ever be installed to the clients for any improvement? Thanks!

Hi everyone, It a painful, but i manage to get my keyboard back. It wasn't working in safe mode, I try the repair option, it took some times but my laptop is working again. I haven't get the chance to re-install Veyon on it because it start working just in time for class. I'll try to "clean" the laptop before trying to re-install Veyon. Thanks again for the help. 3 hours later I can confirm that the laptop is working as a charm and I was able to install Veyon on it.

Hi Toby, Thanks for your reply, but I feel stupid, I was using the veyon-ctl command to reset config within a regular Command Prompt window ... (I still don't get why I need admin privilege when I'm already admin). Opening a Command Prompt as Administrator was what I've miss earlier to reset the config and push the new one. All your suggestion were done it was Windows that trick me (again) Sorry for the useless noise. and thanks again for your reply.