1 |
On Wed, Jun 13, 2018 at 11:41 AM, <thelma@×××××××××××.com> wrote: |
2 |
> On 06/13/2018 10:00 AM, R0b0t1 wrote: |
3 |
>> On Wed, Jun 13, 2018 at 10:18 AM, <thelma@×××××××××××.com> wrote: |
4 |
>>> I run on Gentoo in Virtual Box Windows 7 and trying to connect to |
5 |
>>> Windows 10 |
6 |
>>> |
7 |
>>> X2go - doesn't work on Windows 10 |
8 |
>>> RDS Connection in from Windows 7 to Windows 10 work but not in "shadow". |
9 |
>>> |
10 |
>>> Any suggestion what else to try? |
11 |
>>> |
12 |
>> |
13 |
>> What do you mean by shadow? |
14 |
> |
15 |
> By "shadow" I mean can log-in into the same X-Session as the user is |
16 |
> running. |
17 |
> When I tried to connect from Windows 7 to Windows 10 using RDS I got |
18 |
> connected but the user at Windows 10 was logged out automatically. When |
19 |
> the user on Windows 10 logged IN I got disconnected. |
20 |
> |
21 |
> I use X2go from between Gentoo boxes works very well, even controlling |
22 |
> Windows 7 running in VirtualBox on remote system. |
23 |
> |
24 |
> The problem one of the remote systems is running Windows 10 (stand alone). |
25 |
> |
26 |
|
27 |
There are three ways I could see solving this, in order of ease of use: |
28 |
|
29 |
1) Use RDPWrap.[1] You click some buttons and then connecting via RDP |
30 |
with multiple users will not kick out your previously logged in |
31 |
session.[2] To make things easier to manage I'd recommend creating a |
32 |
separate account to run your VMs so that you can leave it on in the |
33 |
background. However, there is a setting in the RDPWrap configuration |
34 |
tool to allow multilogon with one user which you can try. |
35 |
|
36 |
2) Use X2Go. Use the "suspend session" and "reconnect to session" |
37 |
features. To use this you need to connect via X2Go to create a session |
38 |
and then disconnect while leaving it active. You can later reconnect |
39 |
at any time. This can be a little strange when accessing the session |
40 |
locally, as you need to log in and then reconnect to the session on |
41 |
the same computer. |
42 |
|
43 |
3) Use X11 forwarding. This is likely to do what you have requested |
44 |
but requires some minimal application support. If you launch a |
45 |
forwarded application it will exit once it is closed on your desktop. |
46 |
However, any daemonized programs you are running will stay active, and |
47 |
the application you launch with Xming could be e.g. a managment |
48 |
interface to that server. |
49 |
|
50 |
4) Use VNC. This is probably the worst option but will do *exactly* |
51 |
what you have requested. It will fight the user for the mouse if they |
52 |
were sitting in front of the computer. |
53 |
|
54 |
Can you comment on your evaluation of the suitability of some of the |
55 |
other options? |
56 |
|
57 |
Cheers, |
58 |
R0b0t1 |
59 |
|
60 |
|
61 |
[1]: Most users do not consider RDPWrap to be against Microsoft's |
62 |
terms of use. I would feel comfortable using it in a corporate setting |
63 |
(there is in fact a company that sells a product nearly identical to |
64 |
RDPWrap). An in-depth discussion can be seen at |
65 |
https://github.com/stascorp/rdpwrap/issues/26. |
66 |
|
67 |
Perhaps the most limiting interpretation of the license that is still |
68 |
reasonable allows you, the licensed user, to connect as many times as |
69 |
you want to a single licensed installation: |
70 |
|
71 |
Section 2.d(ⅴ): “Remote access. No more than once every 90 days, you |
72 |
may designate a single user who physically uses the licensed device as |
73 |
the licensed user. The licensed user may access the licensed device |
74 |
from another device using remote access technologies.” |
75 |
|
76 |
And in fact this is what I expected a Windows 8.1 Pro license to grant |
77 |
me the ability to do out of the box, yet it does not without minor |
78 |
modification. |
79 |
|
80 |
|
81 |
Note the Windows license has some patently ridiculous things in it and |
82 |
may not be valid. Taken at face value you are likely already violating |
83 |
it. For example: |
84 |
|
85 |
"Section 2.c: “[…] this license does not give you any right to, and |
86 |
you may not:” and Section 2.c(ⅳ): “work around any technical |
87 |
restrictions or limitations in the software;” |
88 |
|
89 |
Ergo, "[...] using the file search utility FileLocator to work around |
90 |
the restrictions Windows puts in place to limit your ability to find |
91 |
files on the system is strictly speaking a violation of the Windows |
92 |
license as written." |
93 |
|
94 |
|
95 |
[2]: Depending on the settings you pass to RDPWrap connecting as your |
96 |
user remotely while you are logged in locally will forcefully close |
97 |
the local view to the sesion. This is probably what you want. |