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

OK, that was a problem with my comprehension of veyon. The port 11400 is listening on master only when you start demo mode. So i found my error, it was in access control on the master. The user i which i was tested was not authorized. I wa able to supervise the clients but only the demo mode was bugging because of access control. Thanks to lyc_appert for his help

@Badbug Yes, restarting the Master machine solve the problem (for a while), but I don't want to restart my Master PC every day, because it's like a server machine in our network

Hi, Have you tried with the fullpath name of the program ? If the program is in the environnement PATH, it should work. I tested with "notepad" and it launch on the client. So you can try with notepad to see if it work also.

Bonjour Là : https://docs.veyon.io/fr/latest/admin/index.html