Hi, Have you tried to turn off fast startup on Windows? https://www.howtogeek.com/856514/how-to-disable-fast-startup-on-windows-10/ Have you checked that in Bios you turn off all kinds of "deep sleep" mode or Ethernet power saving? Have you checked that on Windows settings / network screen, under network profile type, private mode is selected? Also, I remember that in some Lenovo PCs, if the system was shut down manually, it doesn't wake up by WOL anymore. It has to be shut down by Veyon command to have WOL to work. Hope this helps.

No...I guess you've updated cliens and server ? Now, knowing my own case, It's amazing that in a full micro$oft environment, you've also this problem.

Bonjour, Essayez de passer par là : [https://github.com/veyon/veyon/releases/](link url) Cela fonctionne de mon côté.

The issue has been fixed with Veyon 4.8.1

Hi, we also have implemented GCPW in our labs. At the moment we have no preblems on clients, but we are missing the login feature becuse windows is set up to try the login with GCPW while our needs would be to login on pcs through Veyon with a local user account. This seems to be impossible right now.

Hello, J'ai le même soucis ! Préviens quand tu as une solution s'il te plait !

Bonjour, Je suis un simple utilisateur comme vous. Voici ce qui est marqué sur la page de download du site : "Veyon 4.8 requires Windows 10 or newer. If you still rely on unsupported EOL versions of Windows, you can continue using Veyon 4.7.5" Donc je vous suggère d'essayer avec l'ancienne version 4.7.5 (https://github.com/veyon/veyon/releases/tag/v4.7.5)

Hi. I have the same issu as 153ht. I need , from a server 172.16.100.2, to wake up machines that are in others vlan 172.16.10.x, 172.16.11.x.... What should I do ? Is there commands to implement the broadcast address in veyon ? thanks