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

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