Veyon depends heavily on static addresses. There are options to make use of some weird techiques to make it work with dynamic addreses, not worth the headache though. Static is definitely the main solution.

https://silentinstallhq.com/veyon-silent-install-how-to-guide/

Hi,

Problem solved with version 4.8.2.0.

THANKS.

Hi, Yep. Literally all the computers are in the same groups / same OU / same tree.
They all were visible last major version, and after the update only about half are now visible within Veyon if I flag Veyon to use the AD as the backend for rooms. I've seen this before a few years ago, but it seemed to fix itself after they got updated at some point.

That is why I'm not sure if this is a Veyon caching or timeout issue, or something else entirely.
When starting veyon with AD as its room / backend the bootup does take quite a while, I am assuming its running through the LDAP/AD search.

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 🙂