@Sanny Thank you very much, this is the solution I was looking for!

This is what I have setup for OpenLDAP, if it helps. In OpenLDAP it uses multiple memberUid's for members of groups. [image: 1580553913022-ldap-group-membership.png] These setting seem to work with my limited testing and knowledge. [image: 1580553913353-veyon-env-settings.png] I changed the group member identification and filtered objects on the different OU's and then used the test to ensure I got back the right objects. [image: 1580553913172-veyon-advanced-settings.png]

You'd have to build binary packages on/for the according system. Please follow the instructions at https://github.com/veyon/veyon#veyon-on-linux to generate an RPM. I'm however not sure if all the dependencies (especially GCC 6 or newer and Qt 5.5 or newer) can be satisfied on CentOS 6.

It's ok, the link for Veyon 4.3.2 works now

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.

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