In the case of [censored] there is a "console 9 character ID" that is assigned to the "machine itself", and if you connect to that then it's as if you are sitting at the console of the server. However, each RDP / session (or user profile) also has its own separate 9 character ID. I think it is assigned per user profile?
With Remote Utilities you connect to the same ID and then simply switch to a desired terminal session on the toolbar
("Terminal user switch" icon).
However, if you want each terminal user to have their specific instance of Remote Utilities agent running (and thus have a dedicated connection entry in tech's address book for each terminal user), then you should use Agent
instead of Host. Users don't have to re-download the Agent for each session though - they can leave it on their computer and run on demand. Here is a blog post
about the differences between Host and Agent.
I want the same functionality in RU - I want to do a support session with them on their desktop. I *don't* want the RDP behavior of taking over a session and kicking the exisitng user off their session.
That shouldn't happen.
I think TV's way of doing this only works for Internet 9 character connections, not for direct IP connections, because the server will (usually) just have one IP for all users?
An IP address belongs to a network interface rather than to a specific application. I'm no expert in virtualization, but I can guess that it's still possible to set up virtual IP addresses on the same subnet (and hence accessible the same way the server can be accessible) for terminal users/sessions. More on the subject
Hope that helps.