After several tests, I have verified that the service does not start only on the first logon of an AD user on the computer. If someone else has this problem, the solution is to edit the /etc/pam.d/systemd-user file and add the line: @include common-session just below the line @include common-session-nonintercative. Because it is in the "common-session" file that the creation of directories for AD users via PAM is usually configured.

Hi,
I've already connected the six other PCs via their IP-address. The problem is that the other four computers are connected to the network via another router/ access point. This puts them in another IP-address range (192.168.x.x) while all other computer are on the 10.18.x.x range. I've already tried to ping them but that doesn't work.

I think a little setting inside the router is prohibiting this connection but I can't find out which one. If I could I would just use a switch instead of router/ access point but my IT-department can't give me this because the access point is essential for other teachers their classroom.

Ask your IT if he have installed the interception driver? Without them Veyon can't lock keyboard and mouse.
Demandez à votre informaticien si il a installé le pilote interception? Sans ça Veyon ne peut pas bloquer le clavier et la souris.

@niyas
If you have an Active Directory domain you can use Group Policy Object to automatically update Veyon with script.
If you don't have a domain but you have Windows Pro you can edit the local GPO with gpedit.msc to use a script on a network hard drive, edit your script on update to update your clients:
text alternatif

Does it help you?

Hi, fisrt of all sorry, I haven't read this post until today.
I send you a screenshot of the veyon-server running. I really can't know what's going on as it works perfectly in any windows machine.Screenshot from 2019-05-28 08-49-09_LI.jpg

Thanks in advance

Thank you very much for your feedback!

Do I need to uninstall on student computers? or just uninstall and update the master?

Hi @muneutrino
the computer objects probably have been created in the root folder i.e. Parent UUID is "00000000-0000-0000-0000-000000000000". This happens if you do not specify a parent for a computer when creating it (parent=room - can be specified by either UUID or name). Please specify all arguments as shown by the example printed by veyon-cli networkobjects help add. If you do not want to set a MAC address simply specify "" as 3rd argument. Afterwards dump should show

You can remove the orphaned objects via veyon-cli networkobjecty remove UUID.

Yo también hablo español, ojalá, podamos hacer un hilo en español...

Yo no puedo abrir sitios web, o mandar archivos a mis clientes... necesito abrir el firewall o qué me sugieren revisar?

Hello Sebastián,
How do you configure your Master? Do you use LDAP, xml or you enter clients directly on each Master?

That would be all and good if we had the ability to edit any of the attributes in our AD, for you see, I am in an Education Queensland school, and no-one gets permission to edit AD attributes manually.

So I have quite the predicament on my hands...

Hi @Sparrendal
the LDAP Basic plugin only supports one server/domain/DC. We have a commercial LDAP Pro plugin (still in beta stage) which allows to use multiple servers/domains/DCs with Veyon. Contact us via support@veyon.io to request a trial version.

Hi @patdu59
this function is not available but there's a workaround: start the demo for all computers, stop it individually using the context menu on one student computer and open a remote view window on this computer. This way your screen with the remote view will be broadcasted to all other students.

Hello,
You are right, the access control rules were the problem. Thanks!

Hi @iktAni
simply enable the advanced view using the "View" menu 😉