Strategy for client only #6668
-
In Anydesk, we have the option to create a client only, where it can only receive connection requests, not make them.. and they cannot make config changes. Basically, if we want to make a config change, we have to create a new installer and reinstall to the workstation. The client only would look like the qs one that @rustdesk proposed in #5618 (comment). I know qs is low in the priority list, but figured when you get that working, you can add a tick box to the strategies for incoming connections only or something similar. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 10 replies
-
We'd also really like this feature for a migration to the rustdesk payed plans! |
Beta Was this translation helpful? Give feedback.
-
I start to work on this today, including custom client generator. You will see it in one or two weeks. Apologize for the delay because of our full todo list. some note:
|
Beta Was this translation helpful? Give feedback.
-
hello, can you give us an update on rustdesk quick support? |
Beta Was this translation helpful? Give feedback.
-
Update: https://twitter.com/rustdesk/status/1769171628426944539 |
Beta Was this translation helpful? Give feedback.
-
@rustdesk Trying to set a password and assign the client to a user on the custom client, using "--password " and "--assign --token --user_name " and it's not working like it does with the standalone client. Is it meant to work this way? |
Beta Was this translation helpful? Give feedback.
I start to work on this today, including custom client generator. You will see it in one or two weeks. Apologize for the delay because of our full todo list.
some note: