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