How can I prevent users from using RustDesk between themselves?
I want to use RustDesk with IDEAL Administration for IT administration and support.
However, I do not want users to use RustDesk between themselves, and above all I do not want a user to let someone outside the company take control of their computer. How can I restrict RustDesk to administrators?
To connect to a computer with RustDesk, you need the computer's ID and either a password or the user's approval with a single click. The main risk is therefore a user who gives out their ID and the one-time password displayed by RustDesk, or who accepts an unknown connection, for example during a tech support scam.
Starting with version 27.0, IDEAL Administration closes both doors: only the permanent password, known to administrators, allows a connection.
1. Restrict RustDesk to administrators
- Open the Remote Desktop > RustDesk Settings menu and edit the configuration used by your computers.
- In the Security frame, check Enable permanent password and enter a strong password (or click Generate). Do not give it to users.
- In the Remote computer options frame, check Allow only administrators to use RustDesk. The window displays Valid password. Only this password allows a connection. and the Allow the remote user to accept the connection box is cleared and greyed out.
- Confirm, then take control of the computers (including one-click) or use Mass deployment...: IDEAL Administration applies the settings to each computer.
On the computers, the result is as follows:
- the RustDesk window no longer displays a one-time password: the user has no code to give out;
- the user can no longer accept a connection with a click;
- only the permanent password allows a connection: users do not know it, so they cannot connect to each other either;
- an administrator account is required to change the RustDesk security settings on the computer;
- only administrators can modify the RustDesk installation folder.
The user still sees that a remote session is in progress and can interrupt it: remote control remains transparent for them, without letting anyone in.
Good to know
- The settings are applied during a remote control session on the local network and during mass deployment. A computer reached only by its ID, outside the network, receives them at its next local remote control session.
- Without a permanent password, nothing is locked, otherwise no one could connect any more. The window says so: Administrators only: enable a permanent password.
- If you clear the option, the one-time password is restored on the computers at their next remote control session.
2. Do not block the execution of rustdesk.exe
Do not remove the users' right to run rustdesk.exe (NTFS permissions, AppLocker...). During a connection, the RustDesk service starts the connection manager (rustdesk.exe --cm) under the account of the logged-on user. If it cannot run, the connection is cut after a few seconds ("terminated by the remote device"), on the local network as well as by ID.
If you had applied this restriction, restore read and execute permissions for the Users group. IDEAL Administration 27.0 does it automatically at the next local remote control session; you can also run the following command as administrator on the computer:
icacls "C:\Program Files\RustDesk" /grant *S-1-5-32-545:(OI)(CI)RX
3. Add the connection server and company rules
- Connection server with a key: with the secure Pointdev server (included in the license) or your private server, your computers can only be reached through this server. Someone using RustDesk with the public servers cannot find them. See Why and how should I use the secure Pointdev RustDesk server?
- Unauthorized software: a user could download a portable version of RustDesk or another remote control tool. No setting of the installed RustDesk can prevent this: use AppLocker or App Control for Business (WDAC) to allow standard users to run only programs from C:\Program Files and C:\Windows. Programs started from the Downloads folder or the temporary folder are then blocked, and the installed RustDesk remains allowed.
- Firewall or web filtering: block the public RustDesk servers (*.rustdesk.com) and unapproved remote control services, and allow rustdesk.pointdev.net or your server. See Which ports and domains should be allowed to use RustDesk with IDEAL ADMINISTRATION?
- User rights: do not give users administrator rights on their computer, otherwise they can bypass all these measures.
- The Remove RustDesk icon from desktop option of the settings avoids exposing RustDesk to users unnecessarily.

