@itguy
Hi,

the idea of a background task sounds good to me. I'll give this a try.

@kunneljose

https://github.com/veyon/veyon/blob/master/INSTALL

https://veyon.io/download/

@issam

Yes, just confirming Windows was set to not display last signed-in user.

I have no other ideas at the moment.

@ocrozat
Hello sir,
Do you found the solution for this probleme, I have the same probleme, And I don't know how to fix it.
When I try to connect with user name to an other PC , he refuse informations entred and message appear : tentative d'ouverture de session en utilisant des informations d'identification explicites

@marcus

There is a button to the right of the search field at the bottom of the master window. Its purpose is to toggle display of powered-off or otherwise unreachable computers chosen for monitoring.

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

@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

SOLUTION:
I created new set of keys and those worked. Old keys were from 09/2020, weird that those didn't work.

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

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

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

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 🙂

@josch I don't know exactly how VMware works in your environment. Does it provide remote desktop sessions? If so, you could try enabling the multi session mode (https://docs.veyon.io/en/latest/admin/reference.html#refmultisessionmode) so Veyon Service will start Veyon Server instancs for each user session. The sessions can then be accessed by appending the corresponding port number (111XX) to the host address.

@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

@antrax34

Students have Read access to Veyon$, but do the student computers have access to Veyon$?.

Using 4.5.1 I once noticed a delay in one computer appearing in the Master window. Connecting was unsuccessful but succeeded on a second attempt. The issue appeared transient and has not recurred.