Tranquil IT Forum

Hello,

migrating to WAPT, and I'm still having trouble with a few packages, including Veyon.
Veyon is working on my machines, but it's not managed by WAPT. I'd like to switch to tis-veyon, but the tis-veyon-config package seems to be missing. I saw that it was showing an error on LUTI,
so I'm stuck. I'd like to test it before rolling it out across the network.
Thanks.

Hello,

could someone tell me why the tis-veyon-config package isn't available on the store?
Thanks

, Pierre

Hello,

we're currently looking into this.

Our question is how to implement it in a way that appeals to the widest possible audience.

Should we only request the configuration file, request the key pair, and generate the rooms on the fly?

What operating mode are you using? LDAP connector? How are the rooms declared? Are you using a key-based system?

Hi Simon,

thanks for your reply.
At the very beginning, I was manually configuring the keys and rooms. It worked fairly well. The drawback was having to manage all the rooms manually.
Then, I tested (and am currently using) the LDAP connector. I have to admit that I'm experiencing significant slowdowns and even crashes with Veyon.
I had created machine groups on Active Directory, and that's what was showing up in Veyon.
Veyon is my primary tool for maintenance. But Veyon is also used by some teachers in a few computer labs (like the library or the BTS labs).
So I'm considering using it via LDAP; I even suspect it's causing the Samba domain controller to crash at times...