We've frequently ran into the need to be able to have different technicians connect to different "guest" sessions on the same terminal server at the same time. Currently we fight over whose already in a machine.
Currently if a user is logged in and I try to connect to the same server I jump into his session. It would be nice to have the option to connect to his session or start my own.
Currently only one unattended access sessions is possible to a windows server. We would like to have 2 and possibly more access sessions on a single server. This way we wouldn't have to have multiple servers to this purpose on a single customer.
This is a big one for us as well. We get requests from our vendors on a regular basis to be able to access independent sessions on a terminal server. The only work around currently is to provide them an RDP session, but we would like to control all the access through Control.
On another note, restricting certain users form accessing other user's session would be a great feature (proabably should add that as a second feature request)
In most cases, we want the vendors to be able to login via Control, and only to their own independent sessions, without the ability to sneak up on any other logged in session on the server.
Possibly related issue: unable to see console-user gui-desktop-session in some cases on MacOS. Details below.
Suppose you have a mac with logged on User-A on console, that is, running the usual local desktop-GUI session. On macos, starting around 2015 with 10.7 or so, the "Screen Sharing" app from apple gives remote person a choice: do you want to ask to connect to the logged-on console-user's current existing session (user A), or connect to some other users account ( let us call that user B). User B may or may not have an existing gui-session. If not, then another desktop-GUI session begins for user B. Note that unlike remote-desktop for windows, the existing console user A is not kicked out but can continue to use their mac, even while the other user B is connected to a simultaneously running desktop-gui-session, accessed remotely with Screen Sharing. The userB session remains running even when the remote mac disconnects, and stays running until user B logs out (or mac is rebooted).
In this scenario, screenconnect version 6.6 lets me choose to view the other user B, or login screen, but not the console user A. (I'll test further and give step-by-step how to recreate this scenario: it may require fast-user-switching be enabled. I'd like to be able to use screenconnect to see console user's session but it is not listed under View-> Select Logon Session: the only 2 options are "Login screen" and the "other user B".
Yes I agree. This funktion would be goot improvement. I would like to install a Ubuntu-LTSD Server. Serveral users should be able to use the system at the same time. Is the any possibility to realise a screenconnect session for multiple users to the LTSD system. Each of the users should connect with own login to own display at the same time.
Unfortunately the only way to choose a logon session is to join a session > click the view icon on the admin bar > select the session under select login session.
Doing this while another user is on a session will cause both technicians to select the same session.
There is not a good way of doing this so I recommend adding a feature request at the link below to be able to select logon sessions before joining the session and the ability to have multiple technicians remote into different sessions on the same machine without interfering with the other technician
Feature request - product.screenconnect.com