When creating a new connection in the Remote Desktops MMC snap-in, there is an option called "Connect to console" which is enabled by default. What is the function of this? How does this make the Remote Desktop session behave differently from any other?
| |||
feedback
|
This question covers exactly the same ground as earlier questions on this topic; its answers may be merged with another identical question. See the FAQ for guidance on how to improve it.
|
On Windows Server 2003 the console session is session 0. Connecting to session 0 via the /console switch when using RDP to connect to the server will connect you to the same session as the physical console. It doesn't behave any differently then any other RDP session. The reasons for connecting to session 0 are because processes/services may be running in session 0, to which an administrator might need to connect to to access/manage said processes/services. Session 0 has been deprecated in Windows Server 2008. | |||
|
feedback
|
|
As i understand it the windows console is the physical console of the machine. By this I mean if you log in remotely without /console you can have several sessions over the network and one on a physical monitor plugged into the device. /console make the connection use the one the monitor is using, which will lock the screen of that user until the remote /console session releases it. | |||||
feedback
|
