Its working now as I had to use AD-Credentials from Windows in Directory Server. DOMAIN\User solved the problem.

I also have this problem with Veyon 4.10.0.0. First time I run into this one (v4.9.7.0 and older versions did not show this problem). Btw, we are currently under Windows 11 24H2 in our organization.

Same with docs[.]veyon[.]io/es/latest/

Found a solution! All you have to do is to make a security policy that disables showing the last signed-in user. This defaults the sign-in screen to "Other user" and allows Veyon to correctly enter the login details. This is also better for privacy because you don't see the info of the last person that used the PC (Admins can still see in azure or some other admin panel, it just makes a visual change to the login screen.)

We see the exact same behavior. Win11 25H2, wired network, no firewall between master and client. Veyon-Version 4.9.8. The image on the master-pc freezes, not on the client-side (the headline is misleading).

hello Mona, Provide your email, i can help you on this.

I have sent you an email, check email so we can connect,

Hello We found the solution with the support of PC Sheriff service. Both are using the same VNC for remote access to the Client PCs. PC Sheriff blocks Veyon Service. Solution: user defined installation of PC Sherrif and deselect the installation of UltraVNC Software from PC Sheriff!

Thank you! I will try that over the holiday break and see what happens when the students return. Upon troubleshooting since I made the post, I noticed the "Veyon Server" and "Veyon Worker" are the 2 processes that would continuously restart. The "Veyon service" stayed in the processes list. Based on that is there anything else I should try or do you think this will still do it? Thank You!!