@NJJJCAustin said in Update veyon 4.1 to 4.3 problem displaying computer names on Veyon Master: If you are using LDAP to get your Room/Computers, there is a bug if the Computer Display Name field does not have a value. Pull request 599 fixes this bug by falling back to the CN field if the Computer Display Name field is empty. Hello Thanks; .. with your message I went to see the field in question ... and the problem came from the fact that it was written in capital letters ... CN I corrected by putting in minusucle and everything came back in order ... Fred

@Jimbaker for completeness, what was your solution. It may in the future help others with the same issue?

What access group is the public key set to in the configurator? I believe it defaults to root or administration group. Does the second user belong to the admin group on the 2nd pc?

Actually, I realised that I was using the defaults keyword and that was always showing me the defaults and not the actual values. Stupid mistake. Using veyon-cli config list I can see that the following key Authentication/Method changes from 0 (logon) to 1 (key file). So now I can run veyon-cli config set Authentication/Method 1.

In a Ubuntu 18.04LTS environment (Veyon 4.3) you can achieve that goal by means of scripts acting on the firewall (iptables) of the local machine. One script is used to create the desired rules to block/modulate internet access and the other to flush all the applied rules, thus giving full access to internet. You should also modify the sudoers file to give the client users the privileges to execute the scripts with root privileges without being prompted with a password request. Finally in the veyon master you must add both scripts in the list of the executable programs, so that you can remotely launch them in the clients. One limit of this approach is that an expert user could find the scripts and get internet access launching the unblock script in the terminal.

I have more Information regarding this problem: When I look in the VeyonConfigurator.log on the PC there is a line 2019-12-05T16:13:56.074: [WARN] WindowsUserFunctions: could not fetch domain groups for user "ludwig" Is it possible that sometimes veyon can not read the domain groups although it can read it during the configuration process? (I can see our domain-groups in the texbox "All Groups") Any help would be appreciated.

Just turned on LDAPS and enforced it on our DCs. Playing with the veyon settings I have found that the following still works LDAP server and port: DC works but Domain Name doesn't so have specified a DC. Port 389 works however 636 does not Encryption protocol: TLS TLS certificate verification: Custom Custom CA certificate file: Exported CA cert in CER format, changed extension to PEM and plonked onto a share Hope this helps somebody

@Lirik How it possible. Even Pressing Space Key will detect as a (password ) *