@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.
@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
@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.
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.
@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
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.
Is the affected group name somehow special? What happens if you do not configure computer filters? Can you alternatively try to install Veyon 4.5.1 and replace libldap-common.dll in the installation directory with https://github.com/veyon/veyon/releases/download/v4.5.1/libldap-common.dll (make sure to stop the Veyon Service and any Veyon-related programs such as Master or Configurator before). It contains a minor improvement which might change the behaviour.
If it does not help, please change the log level to "Debug", stop Veyon Configurator, remove C:\Windows\Temp\VeyonConfigurator.log, start Configurator again and click the List all entries of a location button and enter the name of the affected group/location. Afterwards paste the content of C:\Windows\Temp\VeyonConfigurator.log so we can have a look at the related debug messages.