@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.

@whiteb

Welp, I feel dumb. The password that needed to be entered in Veyon for the external VNC server was our local admin password. Tried that, working great now.

I think you should be able to start Veyon Master inside the Windows VM but you won't be able to access the MacOS desktop.

It turned out to be a hostname reverse lookup issue. If NetBIOS is still enabled, on each scan Windows performs the reverse lookups randomly either via NetBIOS or DNS, causing different hostnames (NetBIOS: uppercase letters only) to be resolved, making Veyon reconnect to the computers each time the hostname (format) changes.

We got the similar problem, however we are Chinese character user, and we have deployed 12 student computers and start test login by teacher computer.
We only got 4 of them can login successfully and other 8 got stucked either in the input method or login box.
We are using 4.7.2 teacher master (upgraded from 4.7 after got stucked) and mixed 4.7(8)/4.7.2(4) student, and the result is irregularly got stucked on login.
We are trying to find solution in here and anywhere we can go.

Please update to 4.7.2 where screen resolution issues have been improved.

In this forum, everybody is advised to write in English so more users can help you and participate from solutions found together 🙂

After uninstalling, there may be leftovers in C:\ProgramData\Veyon as well as the user's AppData directory (folder "Veyon" in Local or Roaming). The computer list is stored in the registry, so make sure to remove HKLM\Software\Veyon Solutions.