I tried this again with the new version 4.8.0.4 and ran into the same problem, so I had a deeper look and finally found the problem: starting with version 4.7.5.0, the Veyon setup program is incompatible with mandatory ASLR.

Mandatory ASLR is an additional exploit protection you can enable in the Windows Security app under "App & browser control", or through group policy like I did.

To work around the problem, I included an exception for tthe Veyon installer in the MitigationPolicy.xml I am distributing through group policy. It looks like this:

<?xml version="1.0" encoding="UTF-8"?> <MitigationPolicy> <SystemConfig> <ASLR ForceRelocateImages="true" RequireInfo="false" /> </SystemConfig> <AppConfig Executable="veyon-4.8.0.4-win64-setup.exe"> <ASLR ForceRelocateImages="false" /> </AppConfig> </MitigationPolicy>

Bump. Help please

On Windows 11:
%APPDATA%\Veyon\Config\VeyonMaster.json

The folder on Windows is:
%APPDATA%\Veyon\Config
the file:
%APPDATA%\Veyon\Config\VeyonMaster.json

I have one room with 16 student-PC which I updated to Win11. Bulk-Login works on three student-pcs (always the same three). All Clients are installed exactly the same.

I have built myself the following solution:
(Rollout via GPO)

New task in task scheduling Trigger on login + repeat every hour Start program

Script: C:\Program Files\Veyon\veyon-cli.exe
Arguments: config import "\network-share\veyon-config.json".

Works wonderfully 🙂

@Andrea-Pessina - You most likely need to allow TCP port 11100 inbound/outbound on both the master and client servers. That helped me at least.

@TonyPSchaefer Yes this is exactly what im trying to figure out too. We have multiple Windows servers that students RDP into. My instructor wants to be able to remote view all of the machines with the students logged in. I actually installed the veyon master in the classroom environment and now all I get is a black screen even though its connected. I get the lock screen on different install in a separate subnet so two things to figure out now.