Veyon Community Forum

@DCteacher
You are very welcome!
So it was the public key, good to know.
I'm happy you have solved the issue!

Have a good day!
Carlo

@Luigi-Capp I have fixed it with the command "sudo apt-get -f install /home/luigicapp/Scaricati/Temp/veyon_4.7.5.0-ubuntu.jammy_amd64.deb"
Luigi Cappellazzo

The version 4.8.0.4 have resolved the problem of black screen. But I realised that we can not login a session for multiple computers. Is there a bug for this function too?

Update:
My mistake. I was trying to configure this on the main console / instructor computer. Didn't realize I have to change the destination file transfer path in the configuration on each separate client. That being said it still gives an error that the public desktop folder is not writeable. But I can work around that. Just wanted to provide an update in case anyone else has the same brain fart that I did.

Hey Toby,

thanks for de clear information. Ik guess you'll have an idea of my next question now 🙂 : is a chromeOS client on the roadmap (this should be an enormous added value for schools with 1:1 chromebook projects) and if so, will a chromeOS management licence be required?

thanks!
Mark

@tobydox

Hello tobydox

I have created an environment variable in the operating system with a value equal to 2

SET VEYON_SESSION_ID = 2

And also in the veyon-client environment.

veyon-cli config set Service/VEYON_SESSION_ID 2

My session ID is two

QUERY SESSION

SESSION NAME USER NAME ID STATE
services 0 Desc
rdp-tcp # 2 administrator 2 Active
console 3 Conn
rdp-tcp 65536 Listen

And in no case have I managed to make the screen that shows to the students the session in which the teacher works.

I have also test with the new version of Veyon 4.4.0

I would like to remind you that both the students and the teacher are working on their own virtual desktop connected by RDP, that is, they are all in session 2 of their own virtual desktop.

Figured it go to registry Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Add a DWORD 32 BIT VALUE name it DisableTaskMgr and the value is 1. Windows 10. Do the same here to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. It works on all verison of Window 10. Even Home.

@tobydox said in Windows 10: upgrade to latest version, control problem:

The problem has been fixed in version 4.5.2 - if possible please upgrade and give us some feedback.

I confirm, thank you.

@hobo-sapiens

There isn’t a way in Windows 7 or Windows 10 to intercept a pending sleep state to run code before entering sleep mode. You can configure a scheduled task to run on the detection of a sleep event but the action to perform (Veyon update) happens not prior to entering a sleep state but actually occurs immediately after the computer wakes. So there could be a significant time delay between when the update is queued and when the update is actually performed.

I’ve not attempted to update Veyon with the master open but once the master computer exits sleep mode veyon-master.exe would likely still be in memory so it might be necessary to end the process. You could do this by the scheduled task I mentioned or as part of another update procedure.

The command would be:

"C:\Windows\System32\taskkill.exe" /f /im veyon-master.exe

Or remotely,

"C:\Windows\System32\taskkill.exe" /S computername /f /im veyon-master.exe

@tobydox said in Windows 10: log in function does not work:

@erotavlas how does your Windows login screen look like? Do users have to enter their usernames? We have some information at https://docs.veyon.io/en/latest/admin/platform-notes.html#user-login

Right, thank you.

Are the student sessions virtual/remote desktop sessions? If so try enabling multi session mode (https://docs.veyon.io/en/latest/admin/reference.html#refmultisessionmode) and try the NetworkDiscovery add-on with session scanning enabled so it will access the Veyon Server instances at ports 111XX instead of 11100 only (which is the console session). BTW we'll publish a tutorial on how to work with remote/virtual desktop sessions in a few weeks.

I suggest to update to version 4.5.2 (or newer) which contains important bug fixes concerning Windows 10 support 🙂

@itguy

You could instead copy the wakemon.bat file to a shared network folder then use 'Run program' to run the batch file from the shared folder:

\\servername\sharename\veyon\wakemon.bat

It seems that the slowness and freezes disappear after adjusting the LDAP update interval to 999 instead of 60 seconds .