Regards, I have exactly the same problem,
There is no way for user authentication to work. I always get the error message. I want to use this authentication method without generating Keys. I am using Linux Mint 19.
@tobydox said in Room configuration with Active Directory:
Once the rooms get listed properly switching to the room automatically should be working as well. An important requirement for this to work is that Veyon is able resolve the local computer to an AD/LDAP computer object (by performing reverse DNS lookup and searching for the computer name in AD/LDAP) and find the corresponding room.
Hello Tobias!
Is this limitation with Veyon still current or is version 4.3.3.0 now able to use sub OUs of an active directory?
Right now our Active Directory is configured with sub OUs to splitt between notebooks and pcs. If it´s still current: What about the subscriber edition? Can you show where i can get more informations about it?
Best regards from germany
Norbert
Hey Laura!
Are we talking about Windows Computers? Are they member of an Active Directory?
If can answer both with yes it´s really easy: Veyon can be installed by using a script which can be used as a startup script. By default (you can change this too if you want) Veyon is installed under C:\Program Files\Veyon so it´s a simple if exist query in your startup script:
if not exist "%Program Files%\Veyon" \server\share\installer.exe /S
Important! For a silent installation you must use the /S switch with UPPER letter, otherwise it´s not installing.
There are some more usefull switches
/NoMaster Just install the client
/ApplyConfig="\server\share\current.json" allows to specify your configuration
I hope that´s usefull for you!
Norbert
Assuming it's a problem with the built-in VNC server malfunctioning I installed UltraVNC on my master machine.
Installed the service.
Configured password and started service.
Set Veyon to use External VNC server on port 5900 with the same password.
Et voila - it works now.
Somethings just not right with the built-in UltraVNC server.
I have the start of a blog on setting up Veyon that might help.
https://www.oraclelinux.dev/2020/02/veyon-part-1-introduction-and-my-system.html
I'm not good at this and it is a draft but any constructive comments would be welcome.
The service is really restartet... I tried several ways.
Restartet in services.msc
Restartet in the configurator in the service tab
Restartet with cmd
Everything is done with an administrator or also with the system account.
I also tested the access right in the configurator... By checking the username... Before press apply the user don't have the right to access, but the user group from AD is already set... After pressing apply and restart the configurator the same user can access.
This can be repoduced everytime the config will imported again.
