Please note this is a draft and will be altered as necessaryIn this series of blogs I'm working through setting up and using Veyon. Later blog posts will include configuring Veyon from the CLI and integrating Veyon with LDAP.
From the website: Veyon is a free and Open Source software for computer monitoring and classroom management supporting Linux and Windows.
1. Veyon (Part 1) - Introduction and my system setup.
2. Veyon (Part 2) - Configure basic setup and authentication keys (this blog post).
3. Veyon (Part 3) - Using the CLI (coming soon).
4. Veyon (Part 4) - Using LDAP (coming soon).
I will update these blog posts as and when I learn more or realise that I assume too much or have just got it all plan wrong.
In part 1, the introduction, I went through setting up Veyon on both the master machine and client machines. In this blog I'm going to use the GUI to configure Veyon.
Configuration files, CLI or manually
The settings can be imported via configuration files using the CLI or running individual commands using the CLI. So you can configure Veyon for the master or client and then save and load different configuration files. I’d suggest that you create two configuration files, one for the clients and the other for the master especially if you are going to alter a number of settings and/or have a number of machines to configure or rebuild.
Configure Veyon on the master
Once Veyon is installed on the master machine you will need to configure Veyon. Here I’m planning on leaving most of the settings as their default. In fact I'm going to alter one setting and create the authentication keys.
Change Veyon settings
|Alter Key Authentication Method to key file authentication|
Create authentication keys
On the Authentication keys tab, click on Create key pair and enter the name of the user group or role you are creating the keys for. Most documentation suggests that you call it teacher and I think that at the moment it uses it for the file names it generates.
sudo groupadd veyon-master
sudo usermod -aG veyon-master $USER
Install and configure Veyon on the client
|Public authentication key imported into the client|
Most Linux machines use "ip address" to show the IP address, older clients used ifconfig. Windows uses ipconfig or "netsh interface ip show config" or probably even PowerShell.
Rooms, machines and IP addresses
Next we need to define or rooms and machines. As this software is designed schools and colleges it allows us to define rooms (class rooms) and computers in each room.
Now that you have the clients setup with the configuration and public key and the master configured correctly we can start up Veyon master and monitor our clients.
We can select client machines and see a thumbnail of the actual screen and then monitor, control or take over one or every machine using the buttons across the top of the master application.
You can see the user documentation here for using the master software.
So now you are good to go. Veyon master is configured and the clients are using the authentication key to communicate back to the master.
In the part 3 on this series I'm going to show how many of the tasks completed in the GUI can be achieved from the command line.