I'm responsible for a dozen or so Windows 2003 Servers. I need to be able to
remote into them to see/change what is happening on the console(s). The
technology is built in to Windows 2003 and Windows XP Pro but how to use it
is not obvious.

Remote Assistance

I can use this to connect to the existing session on the server, but only if
I am invited to do so. This is not possible for an unattended server.

Remote Desktop

I can connect without being invited, however, I don't get connected to the
existing session. I get a brand new session which doesn't allow me to see
what is happening on the current session on the server.

Remote Desktop with Shadowing

While this might seem to be the solution, I have to run a session within a
session. The shadowing only allows me to connect to another remote session.
If I run the server apps from a remote session so that I can watch it from
another remote, I can no longer see what is happening if I am physically at
the server, also, the operation of the server then depends on the continued
operation of the PC that is running the remote session.

There must be a way to set up Remote Assistance similar to Remote Desktop
where I specify that certain people, or members of certain groups can
connect to and control the existing session. Does anyone know how?

Before anyone suggests PC anywhere, I've noticed that PC anywhere, as well
as being significantly slower than Remote Desktop, causes a substantial
performance hit while connected.

Hi Jim,

Have you tried this?

Start - Run - mstsc /console.

Enter the credentials of the console session and it will connect to the
console session.

Thanks,
Nico Tomacelli
Microsoft Corp.
US - Windows Core:SOLID

This posting is provided "AS IS" with no warranties, and
confers no rights.
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader
so that others may learn and benefit from your issue.
=====================================================

"Jim de Graff" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm responsible for a dozen or so Windows 2003 Servers. I need to be able
> to
> remote into them to see/change what is happening on the console(s). The
> technology is built in to Windows 2003 and Windows XP Pro but how to use
> it
> is not obvious.
>
> Remote Assistance
>
> I can use this to connect to the existing session on the server, but only
> if
> I am invited to do so. This is not possible for an unattended server.
>
> Remote Desktop
>
> I can connect without being invited, however, I don't get connected to the
> existing session. I get a brand new session which doesn't allow me to see
> what is happening on the current session on the server.
>
> Remote Desktop with Shadowing
>
> While this might seem to be the solution, I have to run a session within a
> session. The shadowing only allows me to connect to another remote
> session.
> If I run the server apps from a remote session so that I can watch it from
> another remote, I can no longer see what is happening if I am physically
> at
> the server, also, the operation of the server then depends on the
> continued
> operation of the PC that is running the remote session.
>
> There must be a way to set up Remote Assistance similar to Remote Desktop
> where I specify that certain people, or members of certain groups can
> connect to and control the existing session. Does anyone know how?
>
> Before anyone suggests PC anywhere, I've noticed that PC anywhere, as well
> as being significantly slower than Remote Desktop, causes a substantial
> performance hit while connected.
>
>
>

We came across this independently about 30 minutes ago. If I may, I have a
follow up question.

If I put all of my parameters in an rdp file I can create a remote (new)
session and have it log me in automatically. However, I can't specify the
"/console" parameter in the rdp file. If I create a shortcut to mstsc and
add in the location of the rdp file and the parameter /console, everything
works, EXCEPT I have to enter the password which is already stored in the
rdp file. Is there any way to add the /console option to the rdp file?

Hi Jim,

Just to be sure we are running the right command, you are running the
following command line?

mstsc stored.rdp /console

If that is correct, it should work. Tell me a little more about your
configuration.
Did you install Terminal Services Licesning on the machine?

Thanks,
Nico Tomacelli
Microsoft Corp.
US - Windows Core:SOLID

This posting is provided "AS IS" with no warranties, and
confers no rights.
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader
so that others may learn and benefit from your issue.
=====================================================

"Jim de Graff" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We came across this independently about 30 minutes ago. If I may, I have a
> follow up question.
>
> If I put all of my parameters in an rdp file I can create a remote (new)
> session and have it log me in automatically. However, I can't specify the
> "/console" parameter in the rdp file. If I create a shortcut to mstsc and
> add in the location of the rdp file and the parameter /console, everything
> works, EXCEPT I have to enter the password which is already stored in the
> rdp file. Is there any way to add the /console option to the rdp file?
>
>

Nope.

The simplest solution would seem to be to be able to specify /console as a
parameter in the rdp file. But how?

"Larry" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Was there ever any resolution to this? I'm seeing the exact same
behavior.
> Thanks.