Veyon Community Forum

use VPN, i think its better

@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

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

Hi. I have the same issu as 153ht. I need , from a server 172.16.100.2, to wake up machines that are in others vlan 172.16.10.x, 172.16.11.x....
What should I do ? Is there commands to implement the broadcast address in veyon ?
thanks

Hi,

me , too, i have problems to view logged in users in RDP-Sessions on win 2019 and win2012R2 Servers. I'm using default config. Veyon Master is showing computernames and the Name of logged in user at console, but not of the RDP-Users, not on 2012 R2, 2019 and not on Win10. On the Clients / Terminalservers the VeyonClient shows the ports e.g. 11102 but only the client-session of the console shoes "connected to ....". In the other RDP-Sessions the clients shows a different port (e.g. 11102) but not wether it is connected or not. On the Master-PC a telnet to the specific port of the clients works.
All antivirus and firewall settings are deactivated for testing but no positive result.

What else can be the problems in connecting from ussersessions to the master?

(veyon 4.3.5 on windows 2019, 2012 and win10)

Thanks in advance

Salut
Suis vraiment ravis de savoir qu'un poste pareille existai déjà car j'ai fait un post lors de la migration de italc mais qui est resté sas réponse, je reviens à la charge car la demande est de plus en plus important pour les sales de classe qui migre vers des solutions client légé, et zéro client. Donc je vai effectué des testes à partir de demain et je vous revien mais déjà y'a t'il une documentation pour la config en terminal services?

Does upgrading to Veyon 4.1.0 help?

@tobydox That is fantastic thanks for the update!!!

Hi, great news! It's working VEYON + ASTER !!!

I made a video with english speaking and portuguese as well, here follows the link:
https://www.youtube.com/watch?v=V0Dj6mj1ico (English)
https://www.youtube.com/watch?v=R8myaZpd444 (Portuguese with captions corrected)

Enjoy it!

The "Perform Access control at program start" option makes the Master application check whether the teacher is allowed to access computers at all. It's an additional check for convenience (which can lead to false positives, that's why you should try to disable it for the time being) but not strictly necessary as the actual access control is performed on client computers so that only authorized users will be granted access. If the option is disabled, anybody can start the Master but still will only be able to access clients he's really allowed to access.

Hello
I launched a test in a room of my school and it seems to be OK
thank you for your work
some suggestions for devolppement: features of italc that were useful:
when several rooms were set up, we could choose directly a room to display in one click,
0_1539350202001_a7f416af-7c9f-4785-af01-d8aca106576a-image.png

When a click held on a thumbnail image of a computer, an enlarged vision of the screen was proposed.
Good luck and keep it up
Fred

@glew_ Monitoring/controlling student's computers at home is not possible. You would need to use VPN solutions to make the computers accessible in general and then also have the students install the Veyon Service – likely not feasible 😉 All I can suggest for the moment is to use meeting tools which allow students to share their screens.

Are you linking to Active Directory via LDAP or using the Authentication Keys?

Sorry for the confusion. Even though the figures at http://docs.veyon.io/en/latest/admin/introduction.html#components are outdated the information below are up to date and should give you an idea of the involved processes. Do you still have questions regarding the processes?

Finally I've foud:
(!(&(memberOf=CN=GroupMaster,OU=Ordinateurs,OU=Groupes,DC=my,DC=network,DC=local)(!(comment=ThisClassroom))))

@niyas
If you have an Active Directory domain you can use Group Policy Object to automatically update Veyon with script.
If you don't have a domain but you have Windows Pro you can edit the local GPO with gpedit.msc to use a script on a network hard drive, edit your script on update to update your clients:
text alternatif

Does it help you?

Hi,
It is possible that the italk service in not uninstalled (conflict with veyon service) or another old vnc still running.

@javisky said in I can't open websites from the teacher's computer:

there are only two possibilities of path

That's really true 😉

Hi..

Apologies for the delay in getting back to you.

I'm afraid that I don't use the group member aspect, so can't really help with that one.

Here are grabs of my config:

Access04.png Access03.png Access02.png Access01.png

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.