Hi, I've just read in the Add-ons section of Veyon's web site: "While the LDAP Basic plugin offers all functionalities required to integrate Veyon with LDAP/ActiveDirectory servers, it's however limited to a single server/domain and flat object hierarchies. The Veyon LDAP Pro add-on is able to fetch network objects from multiple servers/domains. Also location hierarchies in your LDAP directory (buildings, floors, rooms etc.) are represented 1:1 in Veyon Master. Especially central support teams for school districts love having all computers of all schools in one network tree." Maybe that's the answer, change to LDAP Pro.

OpenSUSE Tumbleweed is the first distribution which we build Qt6-based packages so there may still be some compatibility issues. Thank you for sharing the log file entries which allowed us to find and fix the issue quickly. Please find an updated package at https://github.com/veyon/veyon/releases/download/v4.7.3/veyon-4.7.3.6-opensuse.tumbleweed.x86_64.rpm Let us know if you encounte rany other issues.

@lyc-appert-44 Visiblement on est tout les deux en France donc je vais répondre en français Ce matin le problème a disparu. Je suis sur un serveur Sambaedu. Je n'ai pas fait le test de ping par le nom la semaine dernière. Il se peut donc que cela soit bien la cause. Certe je fais une réservation IP par PC, mais sambaedu lui derrière utilise des taches cron pour la synchronisation AD DNS etc, hors quand j'ai eu le problème je venais juste de faire l'intégration de ces postes. Merci pour ta réponse. Bon courage

@ctasd Do you have permission to write to the machine registry? Have you tried to right clic on cmd.exe and run as administrator?

@dvd123 have you tried refreshing it in the veyon master? maybe the units that got blank have its sleep mode enabled.

anyone???

@tobydox Do you think using a PCOIP card instead of regular remote desktop session on the computer would cause a problem?

@tobydox Thanks for your answer, I will take the opportunity to update the park Thanks again for your reply.

@achar74 There'll be various improvements for accessing the systemd session information via DBus in 4.7.3. It will be released next week so stay tuned (alternatively you can test the current test build packages available at https://github.com/veyon/veyon/releases/download/v4.7.2/veyon_4.7.2-31-ubuntu-bionic_amd64.deb and https://github.com/veyon/veyon/releases/download/v4.7.2/veyon_4.7.2-31-ubuntu-focal_amd64.deb). Possibly this also fixes your issues.

Even though there's no dedicated solution for VDI support at the moment, depending on your environment it could be possible to use the Network Discovery Add-on. It allows discovering and accessing arbitrary computers and (remote) desktop sessions in a network. In case you're running multiple sessions per server, make sure to enable the multi session mode in the Veyon Service configuration. This will start a Veyon Server instance for each user session. Network Discovery will help you discovering these sessions (also make sure to enable session scanning!). Like all add-ons, the Network Discovery add-on can be tested for a limited time also without a license. Let me know if you have more specific questions regarding the integration.