Tranquil IT Forum

Wapt version: 2.6.0.16795 - Enterprise Edition
Server OS: Debian 12
Target operating systems: Windows 10
Os Machine administration: Win server 2022

Good morning,

I'm creating this forum post alongside our Discord discussions, in case it can help other users

We set up a Rustdesk server on a dedicated server. We validated its operation with a manual configuration of the workstations.

Having WAPT Enterprise, we wanted to industrialize the deployment; to do this, we imported the package: rustDesk-config-template
He warns us that he needs his dependency, namely the package rustdesk and he downloads it.

Note: the Rustdesk package version that is downloaded is an x86 version (which caused us problems when deploying it on our x64 machines), so we had to manually download the x64 version

The procedure followed:
in the "Private Repository" we right-clicked on the rustdesk-config-template package and launched the "update package". Then we selected "Run update-package for selected packages", after answering "yes" to the first question We have completed the requested information (sorry, the forum doesn't seem to allow me to add more screenshots):
{
"host": "YOUR_SERVER_IP",
"relay": "YOUR_SERVER_IP",
"key": "YOUR_PUB_KEY", (note that the key may end with an =)
"api": ""
}

We confirmed the order by clicking "OK" and then clicked "Upload selected packages". This created a package for us rustdesk-configThis package contains a rusdesk.cfg file with the previously saved configuration coded.

After discussing it with Simon on Discord, it appears that the coded configuration had an extra carriage return. We therefore repeated the entire procedure, and although the configuration seems correct this time, we see no change, namely:

Station 1: Manually configuring the Rustdesk client: Working OK
Station 2: Advanced configuration with Wapt: Not working
Station 1: Removal of manual configuration + advanced configuration with Wapt's: Not working

However, if I leave the configuration manual and push the configuration via Wapt, it still works. So I'm wondering if the package contents are actually being applied to the package...

When pushing a configuration with Wapt, on the RustDesk client in "Settings > Network > ID/Relay Server" the fields remain empty.

Hi Cédric,

After reviewing the code, I noticed there was indeed an issue when the configuration wasn't converted to cfg but to json.

I've made a fix in the store; please try it out.

Simon

Good morning,

I downloaded and tried to use v20 but there seems to be a small bug: Where can I find the "Audit data" file?

Edit: Found it, unlike the previous package, the JSON question should be answered with no

I confirm it works correctly, thank you.

Thanks for the feedback, I also made a small patch today for the Linux clients.

sfonteneau wrote: ↑Jan 27, 2025 - 4:26 PM Thanks for the feedback, I also made a small patch today for the Linux clients.

And for a MacOS client?

I tried here, but even with manual RustDesk configuration, it didn't work.

Security on Mac is "different," so you have to accept quite a bit of the GUI stuff; in the end, I don't know if it's even possible...

Ah...that's a shame,
but thank you.