Remote desktop connection

[Francesco]

i have a PC with Win XP pro, and administer it with the
remote desktop connection trough a LAN.
Is it possible to connect leaving opened the remote PC,
not with the logon screen?

I want to connect and disconnect without to force the
remote user to do a logon after the remote connection.

Bye
Francesco

[Al @Work]

Francesco,

No, that is by design. Reference these KB articles...

http://support.microsoft.com/search/preview.aspx?
scid=kb;en-us;Q282004
http://support.microsoft.com/search/preview.aspx?
scid=kb;en-us;Q280828

Watch the line wrap in the URLs...

Al

>.
>

[Bill Sanderson]

Try this, from
Alex Stephens [MS]
----------------------------------------------------------------------------
------
Yes, there is another way. When you´ve finished with session from the Remote
Desktop client, do not disconnect. Instead, connect that session to the
console with tscon, which is a Windows command-line tool. For example, if
you are connected with the Remote Desktop client to session 0, the following
command, run from a Command Prompt window, will connect your session back to
the console (and disconnect you in so doing):

C:\>tscon 0 /dest:console

If you don´t know what your session ID is, you can find out with qwinsta,
either manually or in a for loop with tscon. For example:

C:\>for /f "tokens=3" %i in ('qwinsta ^| findstr /b ^^^>') do tscon %i
/dest:console

This command runs qwinsta, extracts the session ID from the output, then
connects the corresponding session to the console.

Regards
Alex

--
This posting is provided "AS IS" with no warranties, and confers no rights.
--

"Francesco" <francesc...@cae.it> wrote in message
news:9b8401c20ae0$297c28b0$36ef2ecf@tkmsftngxa12...

[Al @Home]

Bill, you amaze me with your memory of these things...:-)

Thanks...

Al

"Bill Sanderson" <bill_NoSpa...@msn.com> wrote in message
news:eo3calyCCHA.1764@tkmsftngp05...

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.368 / Virus Database: 204 - Release Date: 5/29/2002

[Bill Sanderson]

I need to remember to save that one, rather than searching out the message
and copying it!

What worries me about this one is that I don't understand it. In my usage
of RD, both at home and at a work site on a domain, I connect as the "usual"
desktop user. In both cases, I connect to the session in progress, and when
I hit the X in the upper right corner and disconnect, that session is left
just the way I leave it--if I walk up to the machine and put in the
password, the desktop is right there--if I reconnect via RD, it is just the
way I left it.

So--I'm fuzzy about what the real issue is here. I seem to have worked my
way around the issue that others are seeing, and I need to be able to tell
them how, or what differentiates their situation from mine.

"Al @Home" <A...@Home.net.invalid> wrote in message
news:e5vhlZ0CCHA.1064@tkmsftngp04...

[Alex Stephens [MS]]

I think the issue is that sometimes an administrator would like to connect
remotely to a session for some reason or other, then return it to the
console, where it is used by users who haven愒 been given the account
password (for example, a public PC in a library).

Disconnecting a remote session is the same as locking the machine, in that
it tells the system you扉e finished with the session for the time being, but
would like to use it again later. In this case, the system goes into a
secure mode, requiring a password for access to the session, so users
without the password cannot access it.

To allow access in such cases, it愀 necessary to explicitly connect the
remote session back to the console instead of disconnecting. This avoidd the
locked state, and the need for the user at the console to supply a password.
In normal cases, this should never be necessary, since the user will know
the password.

Regards
Alex Stephens

--
This posting is provided "AS IS" with no warranties, and confers no rights.
--

"Bill Sanderson" <bill_NoSpa...@msn.com> wrote in message

news:OZZUmr0CCHA.2040@tkmsftngp04...

> > > Yes, there is another way. When you扉e finished with session from the

> > Remote
> > > Desktop client, do not disconnect. Instead, connect that session to
the
> > > console with tscon, which is a Windows command-line tool. For example,
> if
> > > you are connected with the Remote Desktop client to session 0, the
> > following
> > > command, run from a Command Prompt window, will connect your session
> back
> > to
> > > the console (and disconnect you in so doing):
> > >
> > > C:\>tscon 0 /dest:console
> > >

> > > If you don愒 know what your session ID is, you can find out with

[Bill Sanderson]

Thanks - that makes excellent sense.

I'm used to rather relaxed small offices, where I tend to know all
passwords, even though I tell folks that not only is this not required, it's
not a good idea!

"Alex Stephens [MS]" <alex...@online.microsoft.com> wrote in message
news:3cfe7cf0$1...@news.microsoft.com...