Room configuration with Active Directory
-
Hi,
I'm using Veyon 4.1.4, with Win10.
I'm trying to configure veyon master to automatically open the room corresponding to the master at veyon-master start.
Computers are stored in an Active directory. Users auth with Active Directory is OK.For computers, in LDAP -> environment settings -> computers tree, I put : ou=computers (test button returns "ok").
My rooms correspond to OU in our AD. For example :
Ou=computers contains Organizational Units, like : building1, building2, ...
Each ou=buildingx contains new OUs : room1, room2, ...
And you can guess, each OU "roomx" contains the computers.In env. settings, if I put ou=room1,ou=building1, test button returns the right number of PCs placed in this OU
But I can't find out what I got to do then to make veyon understand, it has to use this OU as the room
In advanced settings, in the "rooms" frame, I choosed "computers containers or OU", but it has no effect : veyon master starts, but no room available.
Of course, I selected "At start, change automatically change for current room", in master conf panel.I tried a lot of different filters and conf, but without more chance.
Where do I make a mistake ?Thanks
E.T. -
Hi @zeltron80
what you encounter here is a limitation of the current LDAP/AD integration plugin. It currently doesn't support multi-level hierarchies, i.e. only rooms below a specific node/OU can be used. If you use "ou=building1,ou=computers" Veyon uses all rooms in building1. The subscriber edition of Veyon 4.2 will have support for multi-level hierarchies.
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.
Best regards
Tobias -
@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
