RustDesk (https://rustdesk.com/) has clients for most operating systems which have a GUI (Graphical User Interface). This includes Microsoft Windows, Apple MacOS, several flavors of Linux, and even Android and IOS. The latter has limited functionality at the time of this writing.

The configuration files appear to be located in the

 ~/.config/rustdesk 

directory of the current user, while the log files are located in

~/.local/share/logs/RustDesk/

Note that the commands to update the configuration must be run as the root user, with the result that they only modify the contects of

/root/.config/rustdesk

It is possible to manually edit these files (RustDesk.toml and RustDesk2.toml), but always make a backup because the structure is not well documented, as far as I can tell so far. Copying the config files from one machine to another reportedly works well. I think you only need to copy RustDesk2.toml.

The config files for Windows are located in

C:\Users\username\AppData\Roaming\RustDesk\config\

and the log files are in

C:\Users\username\AppData\Roaming\RustDesk\log\

I have to find this . . . .

Various client installers have been built and can be run with varying usefulness. You can find the list at https://rustdesk.com/docs/en/self-host/client-deployment/

In our case, since our Linux machines use something called SysVInit instead of SystemD, we were not able to use the installer there.

For Windows, we had a problem with the automatic configuration, but that was probably due to me not understanding the value to put into the line near the top

$rustdesk_cfg="configstring"

It is documented, but my eyes were glazing over. Get one machine up and configured, then

1. open the RustDesk client interface
2. select the configuration option (next to ID, the three dots)
3. Select Network
4. Unlock the Network (blue bar at top)
5. Select ID/Relay Server
6. Assuming this is filled out correctly, click the Copy icon (upper right, two pages)

This will copy the configuration file in an encoded string to your clipboard. Paste that into the “configstring” in the correct line of the installer script.