Hi,
If you're talking about tests in veyon-configurator : no, they don't.
But the conf is exactly the same as in previous version (I used the same file, imported with veyon-cli).
That's why I asked about what could have changed in veyon's way to interact with Active Directory between the two versions.
That's an interesting observation! Which version have you used before? It's likely caused by too much data being fetched from the LDAP/AD server, caused by either non-optimal LDAP settings in Veyon or too many computers in your directory which Veyon tries to load. Can you try to drop the settings for the MAC and/or hostname attribute?
As indicated correctly you don't need AD or LDAP for Veyon to work. Using key files is the right solution here. Is the private key file readable by the user of the Veyon Master application? Maybe https://docs.veyon.io/en/latest/admin/troubleshooting.html#authentication-settings contains some additional hints for you. Are the key pair IDs identical on all computers?
We recently completed the documentation (https://docs.veyon.io/en/latest/user/features.html#run-program) to include the information that you can simply move the mouse over the according item and press the Del key.
Please make sure the input Interception driver is installed properly. In doubt try to run "install.bat" from the "interception" subdirectory in the Veyon installation directory manually with administrative privileges.
Thanks for sharing the details which should help us solving your issue. Have you followed the troubleshooting guide at https://docs.veyon.io/en/latest/admin/troubleshooting.html#computers-can-t-be-accessed ? Is the port 11100 on a client device accessible from the master computer?
Please check the Wake-on-LAN settings on the affected computers. If power on does not work, the computers are either in a different subnet where the Wake-on-LAN broadcasts are not received or Wake-on-LAN is not configured properly.
Hi @dpoeriksen
you have to enter the name and the password of a user which exists on every computer, i.e. a domain user. Alternatively set up key file documentation. See the manual at https://docs.veyon.io/en/latest/admin/configuration.html#authentication for details
@tobydox Hi again. Of course i did it but this is not the reason.
Just now i found the solution. For anyone who will meet the same problem with Windows Server 2016, just disable Smart Screen. That's all.
Thank you very much.
Yes, you can use the Network Discovery add-on, see https://veyon.io/en/addons/#networkdiscovery for more information. You
can simply download install the add-ons package matching your Veyon version and test the add-on.