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

Published 14 December 2005 05:16 PM by Jeff Widmer

Comments

# Chad Humphries said on 14 December, 2005 05:27 PM
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.
# Jim Hughes said on 14 December, 2005 09:56 PM
You can also add /console after the computer name in the GUI.

SERVER01 /console

At least this works in Remote Desktop Client 5.2...
# Oliver Hine said on 14 December, 2005 09:59 PM
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.
# Aaron Seet (icelava) said on 17 December, 2005 12:02 PM
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.
# chris said on 26 December, 2005 07:37 AM
And if someone want to connect in session mode with windows xp pro?
# Tim F. said on 24 August, 2007 02:48 PM

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.

# Michael A Cooper said on 17 September, 2007 05:32 PM

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,

# Alex said on 06 December, 2007 12:17 AM

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

# Drewskie said on 15 May, 2008 08:03 AM

The new RDP now uses /admin instead of /console

# Rody said on 09 July, 2008 06:35 AM

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

# Ron said on 10 July, 2008 09:34 AM

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?

# Josh said on 11 July, 2008 12:16 AM

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.

# Jaxplanet said on 31 July, 2008 06:23 PM

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?

# Peter Ma said on 06 August, 2008 10:29 PM

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

# Jonathan said on 18 August, 2008 10:29 PM

/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.

# JamesM said on 12 September, 2008 06:41 AM

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.

# Vince said on 29 September, 2008 05:36 PM

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

# Bruce said on 10 October, 2008 10:41 AM

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

# Dave1direct said on 22 January, 2009 08:08 PM

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.

# Bob said on 06 February, 2009 03:30 PM

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.

# Abhishek said on 19 May, 2009 12:54 AM

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

# Matt said on 01 June, 2009 04:50 PM

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!

# COODTEC » Blog Archive » Remote Desktop on Windows Server 2003 said on 26 June, 2009 09:45 PM

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

# Remote desktop to console session on Windows 2003 Server at Stuff.za.net said on 13 August, 2009 02:27 AM

Pingback from  Remote desktop to console session on Windows 2003 Server at Stuff.za.net

# Rick said on 25 August, 2009 02:07 PM

I have tried the /console and /admin switches and both give me an RDP vs. a Console connection on the server. Once I logout, it leaves behind a Disconnected RDP which is causing the issues we are having with a specific appl. The RDP connection target string is %SystemRoot%\system32\mstsc.exe /admin

I am using XP Pro 2002 SP3 on the desktop and Server 2003 R2 SP2 on the target Server.

Thanks for your input.

# RParker said on 04 September, 2009 10:39 AM

> Console connection on the server. Once I logout, it  leaves behind a Disconnected RDP which is causing  the issues we are having with a specific appl.

That's because you are NOT logging out, you are (as the message CLEARLY states - DISCONNECTING).  You need to click shutdown -> LOG OFF.

Not simply click the 'X' to close the session, which leaves the session open.  Using the 'X' ONLY closes the window, but the remote session is STILL live, which is why it shows as DISCONNECTED, you DISCONNECTED from the remote terminal, abandonded it in other words.

# azuan said on 19 October, 2009 07:32 AM

i also want to raise up jamesM and vince, so anyone know whether this is possible? only allow for console login, to prevent accidentally new session.

for example, if someone try to establish new session, windows will send warning like cannot make new session blablabla.

# SCulligan said on 05 November, 2009 07:26 PM

The entry for a saved RDP file is now as follows:

administrative session:i:1

Leave a Comment

(required) 
(required) 
(optional)
(required) 

Search

Go

This Blog

News

    Ads by Lake Quincy Media
    Ads by Lake Quincy Media

Recommended Blogs

Syndication