On Wed, Jun 13, 2018 at 11:41 AM, <the...@sys-concept.com> wrote:
> On 06/13/2018 10:00 AM, R0b0t1 wrote:
>> On Wed, Jun 13, 2018 at 10:18 AM, <the...@sys-concept.com> wrote:
>>> I run on Gentoo in Virtual Box Windows 7 and trying to connect to
>>> Windows 10
>>>
>>> X2go - doesn't work on Windows 10
>>> RDS Connection in from Windows 7 to Windows 10 work but not in "shadow".
>>>
>>> Any suggestion what else to try?
>>>
>>
>> What do you mean by shadow?
>
> By "shadow" I mean can log-in into the same X-Session as the user is
> running.
> When I tried to connect from Windows 7 to Windows 10 using RDS I got
> connected but the user at Windows 10 was logged out automatically. When
> the user on Windows 10 logged IN I got disconnected.
>
> I use X2go from between Gentoo boxes works very well, even controlling
> Windows 7 running in VirtualBox on remote system.
>
> The problem one of the remote systems is running Windows 10 (stand alone).
>
There are three ways I could see solving this, in order of ease of use:
1) Use RDPWrap.[1] You click some buttons and then connecting via RDP
with multiple users will not kick out your previously logged in
session.[2] To make things easier to manage I'd recommend creating a
separate account to run your VMs so that you can leave it on in the
background. However, there is a setting in the RDPWrap configuration
tool to allow multilogon with one user which you can try.
2) Use X2Go. Use the "suspend session" and "reconnect to session"
features. To use this you need to connect via X2Go to create a session
and then disconnect while leaving it active. You can later reconnect
at any time. This can be a little strange when accessing the session
locally, as you need to log in and then reconnect to the session on
the same computer.
3) Use X11 forwarding. This is likely to do what you have requested
but requires some minimal application support. If you launch a
forwarded application it will exit once it is closed on your desktop.
However, any daemonized programs you are running will stay active, and
the application you launch with Xming could be e.g. a managment
interface to that server.
4) Use VNC. This is probably the worst option but will do *exactly*
what you have requested. It will fight the user for the mouse if they
were sitting in front of the computer.
Can you comment on your evaluation of the suitability of some of the
other options?
Cheers,
R0b0t1
[1]: Most users do not consider RDPWrap to be against Microsoft's
terms of use. I would feel comfortable using it in a corporate setting
(there is in fact a company that sells a product nearly identical to
RDPWrap). An in-depth discussion can be seen at
https://github.com/stascorp/rdpwrap/issues/26.
Perhaps the most limiting interpretation of the license that is still
reasonable allows you, the licensed user, to connect as many times as
you want to a single licensed installation:
Section 2.d(ⅴ): “Remote access. No more than once every 90 days, you
may designate a single user who physically uses the licensed device as
the licensed user. The licensed user may access the licensed device
from another device using remote access technologies.”
And in fact this is what I expected a Windows 8.1 Pro license to grant
me the ability to do out of the box, yet it does not without minor
modification.
Note the Windows license has some patently ridiculous things in it and
may not be valid. Taken at face value you are likely already violating
it. For example:
"Section 2.c: “[…] this license does not give you any right to, and
you may not:” and Section 2.c(ⅳ): “work around any technical
restrictions or limitations in the software;”
Ergo, "[...] using the file search utility FileLocator to work around
the restrictions Windows puts in place to limit your ability to find
files on the system is strictly speaking a violation of the Windows
license as written."
[2]: Depending on the settings you pass to RDPWrap connecting as your
user remotely while you are logged in locally will forcefully close
the local view to the sesion. This is probably what you want.
