Jeff Widmer's Blog

ASP.NET, Window Forms, C#, VB.NET, VB6, ASP 3.0

Remote Desktop to Console Session on Windows Server 2003

When you Remote Desktop to a Windows XP Professional computer, you always connect to the console session.  This is the default for Remote Desktop to Windows XP Professional.  When you remote desktop to a Windows Server 2003 computer, the default is to start a new session.  But you can easily connect to the console session of a Windows Server 2003 computer using the /console switch.  This is nice because at work I run Windows Server 2003 as my operating system.  Then when I go home and Remote Desktop to my work computer, I can get to all of my currently running applications without having to start them up again.

To start Remote Desktop in console mode, run this from the command-line:

mstsc /console

UPDATE (8/15/2008):  Windows Vista remote desktop client does not use the /console switch anymore.  It now uses a different switch (/admin) to get to the console session on the server (thanks Drewskie):

mstsc /admin

Posted: Dec 14 2005, 05:16 PM by Jeff Widmer | with 23 comment(s)

Comments

Chad Humphries said:

You can also edit a saved rdp file and add a new line:

connect to console:i:1

to achieve the same with saved session files.
# December 14, 2005 5:27 PM

Jim Hughes said:

You can also add /console after the computer name in the GUI.

SERVER01 /console

At least this works in Remote Desktop Client 5.2...
# December 14, 2005 9:56 PM

Oliver Hine said:

You could also use one of the many replacement RDP applications. I personally use iShadow Desktop (http://www.ishadow.com/Downloads/Betas/tabid/88/Default.aspx)

This client can do RDP, ICA and VNC connections, and they can be displayed in tabs like vs.net

The attach to console setting is in the advanced connection settings.
# December 14, 2005 9:59 PM

Aaron Seet (icelava) said:

Since i only have RDC 5.1, what i do is save a .rdp for each machine i regularly connect to. Then i create a shortcut like

%SystemRoot%\system32\mstsc.exe "C:\Documents and Settings\aaronse\Desktop\Remote Desktops\home.RDP" /console

So I have both options of connecting to Console or Virtual session.
# December 17, 2005 12:02 PM

chris said:

And if someone want to connect in session mode with windows xp pro?
# December 26, 2005 7:37 AM

Tim F. said:

If you want to permanently connect to console mode, create a shortcut for Remote Desktop and then right-click, choose Properties, choose the shortcut tab and then add the "/console" switch on the end of the Target path.

Ex:  %SystemRoot%\system32\mstsc.exe /console

Hit apply and all your sessions will be console sessions.

# August 24, 2007 2:48 PM

Michael A Cooper said:

What If I want to join a session where someone has connected via RDP to my system? How do I determine which session I want to connect to t owatch what they are doing?

Thanks,

# September 17, 2007 5:32 PM

Alex said:

Check www.ishadow.com/.../MainZoom.htm - iShadow Application Suite

# December 6, 2007 12:17 AM

Drewskie said:

The new RDP now uses /admin instead of /console

# May 15, 2008 8:03 AM

Rody said:

All of this will not work on Windows Server 2003 standard x64

# July 9, 2008 6:35 AM

Ron said:

I have an application that needs to start from the console session.  Once started all users can utilize it much like any service.  Do you know of any tools that would allow me to have that start as a service on boot up?

# July 10, 2008 9:34 AM

Josh said:

Reply to Ron

Ron you can use srvany to launch an application as a service. I do this on my server alot to launch standard exe's.

# July 11, 2008 12:16 AM

Jaxplanet said:

My favorite is to install Windows Server Adminpak and use Remote Desktops.

It has a checkbox option to connect to console.

You can save all your desktops as one config file and move it between computers.

The only problem I have is that I want to disable automatic printer installation and I don't know how. Anyone?

# July 31, 2008 6:23 PM

Peter Ma said:

Thanks Drewskie!!! The option "/admin" works fine. = )

# August 6, 2008 10:29 PM

Jonathan said:

/admin for XP SP3 as well.

to find out more type "mstsc /?" in a command prompt.

for XP SP3 and Vista, using /console would connect as regular connection and NOT console.

# August 18, 2008 10:29 PM

JamesM said:

Is there a way from the server to *only* allow console sessions?  I have an number of developers who constantly don't connect to the console session and start to screw things up.

thanks

J.

# September 12, 2008 6:41 AM

Vince said:

I second JamesM's question. I've been trolling through the Group Policy Object Editor, looking for a way to limit connections only to the console to get a WinXP, or Server 2008 like RDC experience. No luck yet. Anyone know the way?

Thanx...

-Vince

# September 29, 2008 5:36 PM

Bruce said:

It also now appears that the /admin switch must be used for Windows XP Professional where service pack 3 is applied (SP3).

# October 10, 2008 10:41 AM

Dave1direct said:

To shadow another users session in RDP, open the terminal services manager, find out their session # then open the command prompt and type shadow session#. i.e. if their session # is 3 type shadow3.

# January 22, 2009 8:08 PM

Bob said:

Thanks, I spent way too long struggling to figure out why the console session didn't work. Turns out, we just updated to SP3 and I was still using /console instead of /admin.

# February 6, 2009 3:30 PM

Abhishek said:

It can be simply by:

1. Start Menu >  Run

2. mstsc /v: servername* /console

*servername is the server to which you want to connect.

thanks

# May 19, 2009 12:54 AM

Matt said:

Thanks so much. My server's video output crashed or something, and I really needed to connect and save my work and shut things down.

Connecting with the /admin switch was a lifesaver!

# June 1, 2009 4:50 PM

COODTEC » Blog Archive » Remote Desktop on Windows Server 2003 said:

Pingback from  COODTEC  » Blog Archive   » Remote Desktop  on Windows Server 2003

# June 26, 2009 9:45 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)