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.
veyon-config
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
pierre.briec
- Messages: 7
- Registration: June 2, 2025 - 10:42
Hello,
could someone tell me why the tis-veyon-config package isn't available on the store?
Thanks
, Pierre
could someone tell me why the tis-veyon-config package isn't available on the store?
Thanks
, Pierre
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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?
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?
-
pierre.briec
- Messages: 7
- Registration: June 2, 2025 - 10:42
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...
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...
