XP Remote Desktop MSTSC and mstsc/console with parameters

Believe mstsc This command everyone is not strange (XP comes with the Remote Desktop Connection, but also you say), yes, is Remote Desktop. But I do not know whether you have to pay attention to, when the XP run inside the mstsc command and connect to another machine, with the task Manager to see the process inside, you will find a little bare feeling inside, less process pinch. I am also today because of this problem to wonder, because on that machine I still hung a program in the running pinch, but why the process is not, and the taskbar did not see the program is running (why I will notice it today.) That is because before, those programs are start-up, and today reinstall the next program on the machine to try to run, so immediately ran to the computer to see. Hey. It's not running. Then task Manager, alas ... Not so little yes, so I wonder ... Then Baidu ah Google Ah, most of the afternoon, is not. Did I make the wrong order today? No, it's not like this before (I didn't pay attention to these before, so almost'm going Aunt Machine), and then scratching. Well, since is the order, that should have parameters, yes, then go to check this parameter, the results of a check, immediately saw a "mstsc and mstsc/console the difference".

Look after the shame, the original I have been using the so-called Remote Desktop, in fact, is a virtual desktop (another desktop), not the remote host display is the desktop. MSTSC and Mstsc/console two commands connected to the Remote Desktop, in fact, is very different drops. The former MSTSC connection on the remote host, the local host is seen by the remote host desktop is actually a virtual desktop, as previously said, not the remote host display at this time the desktop, but after the simplification of the drop, in addition to the running of some programs, in fact, after the boot manually run program is not displayed, At this point, the remote host does not log off the current user and locks the desktop, and all operations on the remote host (where actions are non-modifiable, such as running a program, the same as the same) do not affect local use (except, of course, the deletion of related files). With the parameter mstsc/console is different, when the local through this command to connect to the remote host, the remote host will immediately log off the current user and lock the desktop, and the relevant operations on the remote host will affect the local use, that is, when the remote host re-login to the user, The connection to it will be disconnected locally.

But they both have one thing in common, which is that the actions and modifications on the host will be recorded and saved (this doesn't mean farting). In fact, what I want to say today is mainly mstsc. Because as long as your terminal connection is not up to the limit, you can use it to connect to the same remote PC at the same time on a single computer (then what's the point?). , not just said, you mstsc remote to run after the program is not actually running on the remote host, then the second mstsc up, on the terminal will not see the first MSTSC run program. For example, if you first mstsc up, landed a QQ123456789, and then you in the second mstsc up, you will not see the QQ program is running, and when you also landed QQ123456789, then, You will be on the first mstsc up on the terminal to see a hint that QQ is landing elsewhere (wondering if it is not, are remote connections on the same host running programs, why so?).

So what do you think of now? Yes, is the debug program, when sometimes need to debug the program on several machines, then you can use this method to test, no need to find the machine everywhere, when sometimes playing games to open more, but the game itself is not allowed to open more time, can also use this method.
Khan, actually said so much, I think there may be half of the people before I have already known, but I think there is still a veteran of the rookie, and my rookie brother (-. ) is only the part of the rookie brothers. So if the above is wrong, please the elder brothers to correct, rookie brothers bag letter.

Stand-alone play tired play LAN, remote change thinking with the following command to solve the problem of the maximum number of connections

Run Mstsc/v:ip/console

You can connect to a 0 session of a remote system.

In fact, this is mainly mstsc parameter understanding, you can learn by MSTSC/?

Remote Desktop Connection

MSTSC [ ] [/v: ] [/console] [/f[ullscreen]]

[/w: /h: ] | /edit "ConnectionFile" | /migrate | /?

--Specifies the name of the connected. rdp file.

/v: --Specifies the terminal server to which you want to connect.

/console--a console session connected to the server.

/F-Launches the client in full-screen mode.

/w: --Specifies the width of the Remote Desktop screen.

/h: --Specifies the brightness of the Remote Desktop screen.

/edit--Opens the specified. rdp file for editing.

/migrate-Migrate The legacy connection files created by the Client Connection Manager to the new. RDP connection file.

/? --Generate this usage message. Run Mstsc/v:ip/console
You can connect to a 0 session of a remote system.
In fact, this is mainly mstsc parameter understanding, you can learn by MSTSC/? Remote Desktop Connection
MSTSC [ ] [/v: ] [/console] [/f[ullscreen]]
[/w: /h: ] | /edit "ConnectionFile" | /migrate | /? --Specifies the name of the connected. rdp file. /v: --Specifies the terminal server to which you want to connect. /console--a console session connected to the server. /F-Launches the client in full-screen mode. /w: --Specifies the width of the Remote Desktop screen. /h: --Specifies the brightness of the Remote Desktop screen. /edit--Opens the specified. rdp file for editing. /migrate-Migrate The legacy connection files created by the Client Connection Manager to the new. RDP connection file. /? --Generate this usage message.