authorpa

I'm trying to connect from a Vista based system to Windows Server 2003 via
Remote Desktop. When I connect using the Vista system it pulls up my own
instance of the account that I'm trying to log into. What I am wanting to do
is basically have Account A logged into the server and from the Vista system,
be able to remote in and not have it log in as Account A(2) but log in as
Account A. I want to be able to control the already logged in account
remotely. Perhaps I'm missing what needs to be done here. Any information
on this would be greatly appreciated

vera noest [mvp]

You'll have to connect to the conaole of the server:

mstsc /console
__________________________________________________ _______
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?QXV0aG9yUGE=?= <AuthorPa@discussions.microsoft.com>

authorpa

I also attempted that to no avail. It connected but gave me the same thing.
I tried connecting to the cnosole as well as shadowing. I mean, I've seen it
done previously on other servers where all they did was RDP from the machine
into the server and could access what they were using at that second. Of
course that was XP/2k3 instead of Vista/2k3.

Is there anything in particular I need to change, install, update, etc to
get this working?

vera noest [mvp]

Have you tried shadow 0 from the second session?

278845 - How to Connect to and Shadow the Console Session with
Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=278845

If that doesn't work either, I'd suspect a problem with the 6.0 rdp
client, although I haven't seen read anything about this problem
elsewhere.
Or are you running the 6.1 beta version? Then you need to use
/admin instead of /console, as documented here:

Changes to Remote Administration in Windows Server 2008
http://blogs.msdn.com/ts/archive/200...ges-to-remote-
administration-in-windows-server-2008.aspx

You can probably get the behaviour you want by configuering the
server to allow only a single session per user, but maybe that is
not what you want?
__________________________________________________ _______
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?QXV0aG9yUGE=?= <AuthorPa@discussions.microsoft.com>

authorpa

I have tried the shadow 0 as well and get the same results. I am not running
the 6.1 beta so that won't be the issue. I also tried setting it to single
session per user and that ended up dropping the server off the local network
but after changing the setting back it picked up the network again. Does the
server need to be a DC for this to function correctly?