mirror of
https://github.com/rustdesk/rustdesk.git
synced 2026-03-02 19:26:56 -05:00
multiple concurrent users (multiple rdp sessions / terminals) #271
Labels
No labels
bug
documentation
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
question
unreproducible
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rustdesk-rustdesk#271
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @test2a on GitHub (Dec 5, 2021).
would it be possible to get multiple clients to hit a windows machine multiple user logins at once? i mean i understand this to be an anydesk/teamviewer alternative than a rdp alternative but still, can users be selected and can multiple people hit a single server at once and not get the same account
@fufesou commented on GitHub (Dec 5, 2021):
For now rustdesk captures picture of the displays.
This idea can be implemented, if multiple accounts login on different displays.
But there seems no way to do this?
Rustdesk can also start rdp client.
On the other way, you can use rdp connection to do this on windows.
https://github.com/anhkgg/SuperRDP
@test2a commented on GitHub (Dec 5, 2021):
@fufesou i currently use rdpwrap to avoid buying cals or whatever but i don;t know what superrdp does. anyways, i haone "this" via anydesk but its janky. maybe you can "automate" it.
i have multiple terminals on the "server" that i need to remote into. instead of initiating the connection from the remote>server, i do the opposite, i start a connection server>remote then reverse the connection.
i have only achieved this when the account on the server is on and someone can do this manually but i'm not sure if this is making much sense.
oh, i have also had the idea of " different anydesk IDs per user" on a machine so a remote user can join their own account remotely with password so that is something you can look into. Anydesk does not allow that, they have a per machine id which makes this a bummer but maybe you can try.
@fufesou commented on GitHub (Dec 5, 2021):
@test2a "SuperRDP is a new version rdpwarp base on the rdpwrap by stascorp." You can learn it very in few minutes.
As I know, SuperRDP may handle your request well.
As for integrated RDP protocal, it depends on the author's plans.
@Tapuzi commented on GitHub (Dec 13, 2021):
This discussion was useful for me - thank you all.
@rustdesk commented on GitHub (Jan 16, 2023):
anydesk below
@pata2004 commented on GitHub (May 23, 2023):
Thanks for the great work.
Can Rustdesk manage several virtual graphics desktops (different users) on a single remote server?
If yes, how can I set up that?
If not, do you plan to add this function?
@rustdesk commented on GitHub (May 23, 2023):
no plan yet
@pata2004 commented on GitHub (Jun 1, 2023):
Hi,
I use the Rustdesk to connect to my Centos machine with 4 users/desktops.
But I never know what user/desktops Rustdesk will go open.
Can I define what user/desktop to connect to?
Or, do I need to use Centos with only the root user?
@test2a commented on GitHub (Jun 2, 2023):
@pata2004 yes. same problem for me. we have a dozen users and its like a roulette which user you get. Not great ux. if we could only specific, like windows remote desktop connection does, which user to connect to, that would be awesome.
@tayvermtos commented on GitHub (Jun 13, 2023):
Hi
If I may add to the above the following:
I have a VM hosted on my physical Windows 11 machine using HyperV. The VM is also a Windows 11 machine. When I connect to the VM, it uses some kind of RDP to connect to it (it isn't a completely regular RDP session, as for example you can go into the BIOS of the VM which isn't really possible as it runs on OS level).
When the VM is running and I would try to login to this VM via RDP onto the same user, it obviously will terminate the other session, as by standard config more then one RDP session to the same user isn't allowed.
When using Teamviewer for example, this isn't an issue since it just shows on teamviewer the screen which the rdp session user sees.
BUT, when using RustDesk to remote into the VM mentioned above (hosted on HyperV) as soon as RustDesk connects, it does not allow you to stay connected via RDP. Or the vs versa when logged in via RustDesk and then logging in to the same VM via RDP the following error is displayed on RustDesk: "an existing connection was forcibly closed by the remote host 10054"
I'm unsure why this is happening but it's almost as if RustDesk is considered as another RDP session to the same machine.
@rustdesk I'm unsure if this is an issue or a limitation, but I'd certainly not be able to use RustDesk if it kicks users off their RDP sessions.
@zettrik commented on GitHub (Jun 19, 2023):
Hello, first thanks for this great piece of software. I stumbled across this issue, as we have a similar situation (rustdek from windows or linux machine a windows terminal servers with multiple users).
We really don't want to migrate to teamviewer und would rather like to support this FLOSS project. So is there any helpful support (not coding), to let this feature request find it's way into your next plans - idk e.g. a terminal server for development?
Or are there technical limitations that would make it impossible?
@vmiwouter commented on GitHub (Jun 26, 2023):
@rustdesk Like above, will there be an option that rdp sessions get unique ids?
@mstarostik commented on GitHub (Jul 25, 2023):
Similar here. I have a bunch of VMs and the console session isn't really visible anywhere. Everyone connects via RDP, but when I want to support the users, I'd like to keep their session open and use RustDesk to view the same session. This works, when the software is just started by the user without being installed, but when I install it to also get unattended capabilities, I can only connect to session 0.
@rustdesk commented on GitHub (Jul 25, 2023):
You can also elevate without installation now.
@jb-esselink commented on GitHub (Aug 3, 2023):
Same issue here, i am trying to connect to a user specific session. Current state of the application sends me to the windows login screen. Would be nice to have a session specific ID or have a session selection popup in the case of an RDP connection.
@technoicon commented on GitHub (Sep 20, 2023):
+1 we need this function to be able to use RustDesk.
We connect and support multiple users on one Remote Desktop Services Server.
Following to be able to move to rustdesk when functionality is avaliable.
@technoicon commented on GitHub (Sep 21, 2023):
How do these bounties work?
I'd be happy to pay for this or chuck in some monies to increase the bounty.
@rustdesk commented on GitHub (Sep 21, 2023):
If you wanna increase the bounty, please have a one-time sponsor on https://github.com/sponsors/rustdesk, I will increase this bounty per your sponsor. @technoicon
@zcesur commented on GitHub (Sep 21, 2023):
@rustdesk thanks for installing the app & trying out the bounty command! that's the best way for maintainers to use algora
your community can also fund bounties themselves here: https://algora.io/org/rustdesk/bounties/new
ex @technoicon could use this. if more folks add bounties on the same issue they get pooled
@subscribernamegoeshere commented on GitHub (Dec 5, 2023):
maybe this is the wrong bug entry but I will start commenting here, sorry to bother, I would like to know what that "remote desktop" checkbox does mean in the rustdesk 1.2.3 version (on windows) i couldnt really make sense of it when activating and triggering this kind of rdp something from a remote machine (windows as well) it would create kind of like a tcp tunnel or so and spawn an mstsc.exe (rdp client on windows, default microsoft) but then fail to deliver any kind of connection or pixels to whatever rdp session that would turn out. i didnt find documentation to this?
my actual question or feature? request would be allowing to connect into the single rdp-ish session there is on personal windows client editions (so not windows server), that windows pro/professional editions support.
is this feature realted to this ticket? i am not totally sure. Maybe terminal services and multiple such rdp sessions inside a machine (server) is then a extended upper set of this feature? would be very glad to see this happening. thanks.
also: how to donate best to this project without wasting funds to payment processors and all. is there a charity or foundation of some sorts that directly supports you, maybe GNU or free software foundation or any such thing? or is github sponsor and that bounty page the best to do so?
i am a paying user of anydesk but they are seriously degrading and deteriorating more and more and I would like to donate my yearly anydesk consts to this project to begin with or so if possible. thanks.
@strarsis commented on GitHub (Jan 23, 2024):
+1, at the moment only TightVNC (at least from knowledge) is able to use RDP-sessions.
It would be awesome if this VNC-alternative also supported RDP-sessions.
@rustdesk commented on GitHub (Feb 19, 2024):
Ready in nightly build now, https://twitter.com/rustdesk/status/1759445426267189273