We've kept the default Configurator path even though the redirected H:\Pictures folder would be the more practical. The original Windows 10 default profile folders should still exist so setting the Screenshots path to C:\Users\username\Pictures would save the files locally. You might try mapping a P: drive directly to the roaming profile share \\<servername>\<fileshare>\<username>.V6\Pictures then set Configurator to use P:\ drive for storing screenshots. No way for me to test here.

@tobydox Request logins using accounts with blank passwords be allowed as a configurable option. We use Active Directory to assign generic accounts to particular workstations by MAC address. In this way accounts without passwords are limited to logins at specific sets of computers where security is controlled at the machine level. Our library uses the limited PATRON account for public catalog and database access and for general browsing of our collection. It would be convenient to log in our public computers en masse using this password-less account. Students and faculty requiring broader access also have the option to log in using their assigned domain account.

@jrpfahl Try turning off the Windows Defender Firewall (Domain Network) for one of the Windows 10 computers and try again.

Use the Veyon ‘Run program’ feature for running either a Devcon or PnPUtil script to disable (and enable) the device’s HID-compliant touch screen drivers using the specific HID\VID device instance path(s) and without the need to restart Windows. devcon enable "@HID\VID_056A&PID_00E6&MI_01&COL05\8&27A6CAE3&0&0004" devcon enable "@HID\VID_056A&PID_00E6&MI_01&COL01\8&27A6CAE3&0&0000" devcon disable "@HID\VID_056A&PID_00E6&MI_01&COL05\8&27A6CAE3&0&0004" devcon disable "@HID\VID_056A&PID_00E6&MI_01&COL01\8&27A6CAE3&0&0000" Disabling touch in this manner should still allow pen input.

@cns-saintes Try updating to Veyon version 4.4.2.

Click the 'User custom computer arrangement' button located in the lower-right hand corner of the Veyon Master window then drag the computer icons to your preferred locations. The 'Align computers to grid' button found nearby is also useful for this purpose.

What is the brand and model of the gigabit switch? Is the switch configured within a stack?

Hi, Fixed the issue by adding 'dNSHostName' to the 'Computer hostname attribute', in Environment settings, under LDAP Basic. Andy

I have the same problem. I tried everything. I asked for professional support. The problem still remains. I think the last upgrates of Windows 10 don't support Veyon 4.4.2 version 64 bit.

Finally got it to work with 4.2.2. Setup is the following: lab with a Master. The Master will not be used by students, logon auth is unneeded and causes other issues. First install Veyon with the master on a machine and generate a key pair (I just name it "teacher"). Export them to another folder (I put them on the file share for distribution later). Generate locations and computers in Location & Computers. You'll have to install the clients with either a config file included or utilize veyon-wcli to change authentication mode. The config will not set the key access control group, you'll need to set it with veyon-wcli. By default it pulls the highest privilege group available when the key pair is created (Administrators), but you'll actually want to have it for the lowest (Users). //Config for Master/Client General Authentication Method: Key file authentication Computer Access Control x Grant access to every authenticated user (default) Authentication keys Set Access group to "Users" //Imports public key "C:\Program Files\Veyon\veyon-wcli.exe" authkeys import teacher/public \\fileserver\share$\folder\teacher_public_key.pem //Imports private key (Master Only) "C:\Program Files\Veyon\veyon-wcli.exe" authkeys import teacher/private \\fileserver\share$\folder\teacher_private_key.pem //Sets access group to Users (works with domain login as well) "C:\Program Files\Veyon\veyon-wcli.exe" authkeys setaccessgroup teacher/public Users //Sets access group to Users (works with domain login as well) (Master Only) "C:\Program Files\Veyon\veyon-wcli.exe" authkeys setaccessgroup teacher/private Users One gotcha I learned is that the Veyon uninstaller will not remove keys. If you generated new keys for a new version but with the same name, the old ones will have to be deleted first because the import will not work if a file with the same name exists. //Remove the Veyon folder from ProgramData rmdir /s /q "C:\ProgramData\Veyon" When you import the keys with veyon-wcli the folder structure will be created. Now you've Veyon running with key authentication.