Today I plan to collaborate with colleagues in the field to set up a Windows 2012 R2 server. Originally, I thought this was a very simple thing. I went up mstsc and he went up mstsc. Then I right-clicked his account in the user of the task manager, and the remote control would do. I used to do this in 2008 R2. Unexpectedly, under 2012R2, this remote control is gone
Baidu took a look at it ,,,,,, not to mention it, to spit out weakness, artificial fool just happy.
The English website searched for some time and finally solved the problem: add a bunch of parameters when starting mstsc.
Specifically, first let the colleague in the field log in normally, then enter the task manager, click the detailed information, and go to the "user" page. Right-click on the title bar of the "User" table and check "ID". Then let him tell me the value of this ID. Let's say it is 2.
At this time, I then enter the command line:
mstsc / v IP address: port / shadow: 2 / prompt / control
2 of them is his login ID. The port can be omitted with the preceding colon, unless the default 3389 is changed. / prompt means to prompt for the login account, / control means that you can control the desktop after logging in.
After the command line is started, log in first, and then the other party will prompt "Who is who is requesting to control your session", requiring the other party's consent. Then you can have fun together.
The advantage of this command line method is that there is no need to change any configuration of the server, such as modifying group policies so that the same account can log in multiple times, adding RD roles and functions, etc.
It should be noted that today's practice found that only the same account is useful, and each account will be rejected. I don't know if this is normal.
