RE: Remote Desktop Second Console

I'm not sure if the "connect to console" box in Remote Desktops
supports the new /admin switch. Sounds like it doesn't.
If that's the case, you can't use the Remote Desktops snap-in.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?U211cmZtYW4=?= <smurfman@xxxxxxxxxxxxxx> wrote on 06 jun
2008 in microsoft.public.windows.terminal_services:

You are correct, SP3 is what changed things. I recall reading
about the /console and /admin thing... but never gave it
another thought.

The problem I have is this. I created an Admin mmc, and added
Remote Desktops to my console. Then when I want to connect to a
server, I simply add that IP address in there, and the rest is
done.

How will I accomplish the Admin switch to make it take over the
existing session?

Thanks
J



"Vera Noest [MVP]" wrote:

I think that there is a much simpler explanation:
With XP SP3 came rdp client 6.1. In rdp 6.1, the /console
switch is no longer supported (and ignored if used), as it is
now replaced by the /admin switch.

Documented here:

947723 - Changes to remote administration in Windows Server
2008 http://support.microsoft.com/?kbid=947723
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

v-morche@xxxxxxxxxxxxxxxxxxxx (Morgan che(MSFT)) wrote on 06
jun 2008 in microsoft.public.windows.terminal_services:

Hi,

Based on my research, the factor determining if client will
take over the current user session on Terminal server does
not have connection with the version of OS on client. It's
about how can define in Group Policy and the status of
sessions.

Analysis:
========

Generally speaking, only if the previous terminal session
state is "Disconnected" users will be able to reconnect to
the original terminal session; however, if the previous
terminal session state is "Active" or logged off a new
terminal session will be established. In this way, the
current user logging on TS will not be taken over due to the
establishment of new session.

Additionally, by default, windows server 2003 will get a new
session unless we use "Mstsc /v: servername /console" command
to logon TS. I think that is why Windows XP do not take over
the session on TS.

Here I would like to confirm which state of the problematic
terminal session is in Terminal Server Manager. Is it
"Disconnected"?

If not, I suggest that you refer to the following Microsoft
Knowledge Base article to configure the "Keep-Alive
Connections" group policy to let and refresh it by running
the "gpupdate /force":

216783 You cannot completely disconnect a Terminal Server
connection
http://support.microsoft.com/default.aspx?scid=kb;EN-US;216783

< how can I force the Remote Desktop to take over the
existing logon?>

We can configure the "Restrict each user to one session"
option in Windows 2003 terminal server so that each user has
only 1 terminal session on the server:

1. Click Start -> Run, type "tscc.msc" in the text
box, and click OK. 2. Click "Server Settings".
3. Locate the "Restrict each user to one session"
item, and set it to "Yes".
4. Restart the server to test the result.

Meanwhile, if you would like to connect to the console
session please use the following command line to logon
session 0.

mstsc -v: servername /F -console

For more information, please refer to the following Microsoft
Knowledge Base article:

278845 How to Connect to and Shadow the Console Session with
Windows Server 2003 Terminal Services
http://support.microsoft.com/default.aspx?scid=kb;EN-US;278845

Hope this helps.


Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your
issue. =====================================================
This posting is provided "AS IS" with no warranties, and
confers no rights.


--------------------
--->Thread-Topic: Remote Desktop Second Console
--->thread-index: AcjHJlRmgiBW2yGESqGzhMyUTkf0IA==
--->X-WBNR-Posting-Host: 207.46.192.207
--->From: =?Utf-8?B?U211cmZtYW4=?= <smurfman@xxxxxxxxxxxxxx>
--->Subject: Remote Desktop Second Console
--->Date: Thu, 5 Jun 2008 09:08:01 -0700
--->Lines: 24
--->Message-ID:
<A4A1AC48-09C2-45E4-B1AE-4C96E83F56C9@xxxxxxxxxxxxx>
--->MIME-Version: 1.0 --->Content-Type: text/plain;
---> charset="Utf-8"
--->Content-Transfer-Encoding: 7bit
--->X-Newsreader: Microsoft CDO for Windows 2000
--->Content-Class: urn:content-classes:message
--->Importance: normal
--->Priority: normal
--->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
--->Newsgroups: microsoft.public.windows.terminal_services
--->Path: TK2MSFTNGHUB02.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.terminal_services:18187
--->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
--->X-Tomcat-NG: microsoft.public.windows.terminal_services
--->
--->Recently a patch or settings, I am assuming something
with SP3 on XP or --->Remote Desktops patch, has changed the
way I use Remote Desktop to connect to
--->servers.
--->
--->It used to be from my XP Pro machine I could use Remote
Desktop to connect
--->to a server and log in as an administrator. If I was
logging in as the same
--->admin that was logged in, I would simply take over that
session and the --->screen would lock, if I logged off it
logged off the Admin or if I --->disconnected, it would just
leave the server locked. --->
--->NOW - when I connect to a Windows 2003 Server, it seems
that instead of --->taking over the session that is already
logged in, a new / second console is
--->started, and duplicate programs are started, and I can't
see what messages or
--->errors that might have been present on the original
logon. --->
--->HOWEVER - when I use Remote Desktop to connect server to
server, I --->experience the behavior that I am used to.
--->
--->My question is this, what setting is forcing a second
console to start, how
--->can I keep this from happening - or better, how can I
force the Remote --->Desktop to take over the existing logon?
--->
--->Thanks
--->J
--->
.

Relevant Pages

  • RE: Remote Desktops Tool
    ... In remote desktops. ... connecting to the console or a new session, in fact I thought the whole ... We have one customer with an SBS2003 R2 server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Services and Interactive Services
    ... If your Terminal server runs 2003, you can connect to the console ... session with "mstsc /console". ... > see the dialog on remote desktop. ...
    (microsoft.public.win2000.termserv.clients)
  • RE: Remote Desktop annoyance
    ... Connect ot console connects you to Terminal Server Session Zero, ... President - Session Computing Solutions, ...
    (microsoft.public.windows.terminal_services)
  • 2003 Terminal Server Session Application Issue
    ... HRMS runs good from a Windows 2000 terminal server session and the ... application runs good from Windows 2003 server console. ...
    (microsoft.public.windows.terminal_services)
  • Re: Logon Error Message
    ... Is the user who get the error trying to connect to the console ... Only one user at a time can connect to the console session ... >> Vera Noest ... >> MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.win2000.termserv.clients)
Loading