Hi @fra-sa @esaurel In one lab, I finished updating all my clients to Veyon 4.8.2, and for some students, the issue is still present. At this very moment, the lab is wired with both the Windows 10 x64 master and student computers connected at 1 GB/s. I opened an issue on github here: https://github.com/veyon/veyon/issues/895. In the meantime, hitting F5 refreshes the correct student status. Have a good day.

I have tryed to add the domain after the hostname but I still get the same error

Good morning, Thank you for your reply

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.