Re: Remote Desktop to XP Pro Problems

Connecting to the console is not the default, but client OSes (like WinXP) don't allow more than a single logon per user to my knowledge. Being the "console" shouldn't matter much one way or another (Vista and Longhorn reserve the console session, session 0, for services; no one actually logs in to it).

Disconnect is the correct option; logoff will definitely kill any running programs. I'm going to check around and see if anyone has heard of any issues in this arena and get back to you.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"JimR" <JimR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:E118CD7B-9A7A-43F4-95F4-F6DE2A9F46CA@xxxxxxxxxxxxxxxx
Thanks for the info.
On number 1, I do not know what you are refering to when you say the
"windows security" icon.
For number 2, we do not have a GP forcing logoff. The odd thing is that when
the user disconnects, the normal window pops up saying that their programs
will continue to run but in fact the opposite happens. Is the default for RDP
to be logged in to the "console"? This is the larger of the 2 problems by far
becuase the programs they run can take hours to complete their work. Is the
behavior of RDP sessions set in the Terminal Services portion of GP? Is it
possible that this is being affected by the way they are disconnecting? They
should choose "disconnect" as opposed to "logoff", correct? I assume this is
right or they wouldn't receive the message about their programs continuing to
run. I'm stumped but we really need to figure this out.
Would appreciate any additional ideas you might have.

Jim

"Josh Rosenberg [MSFT]" wrote:

An additional note on problem number 1. Assuming you haven't disabled it,
the "Window Security" icon should appear in the Start Menu while running
under Remote Desktop. It should be able to do the shutdown/restart you
want.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"Josh Rosenberg [MSFT]" <joshrose@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:9F67A3A0-C190-48D2-A15E-11EDD3CCDFFE@xxxxxxxxxxxxxxxx
> For problem number 1, you could simply provide a shortcut that executes
> the proper shutdown command. There are numerous other ways to shutdown > a
> machine that don't require it (Alt-F4 while the desktop or task bar has
> focus, selecting it from the Task Manager menus, etc.), but > distributing a
> shortcut is simplest.
>
> For problem number 2, group policy can restrict users to a single > session,
> so any attempt to login with a specific user name always targets the > same
> session. To my knowledge this is the default for WinXP, but I've not
> tried it in a while. If the session is actually disappearing, is there > a
> chance you have an "Idle Logoff" GP set up? Again, by default a user
> logged on at the console should not be logged off automatically, but > your
> GP might be forcing it.
>
> -- > Josh Rosenberg [MSFT]
> SDE - Terminal Services
>
>
> "JimR" <JimR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C8EA87B6-1B7E-48DD-B61E-E25A19354A76@xxxxxxxxxxxxxxxx
>> We are using Remote Desktop to access XP Pro desktops. We are having 2
>> issues.
>> 1st - The "shutdown/restart" button is not available. The users need >> the
>> ability to occasionaly reboot these machines. I know I can use the
>> "shutdown
>> -r" option via cmd but regular users need simple solutions.
>> 2nd - When the users disconnect, their programs stop running and
>> shutdown.
>> The user will connect to the XP box via remote desktop while here in >> the
>> office, kick off a program, then bring their laptop home, reconnect >> and
>> the
>> program they ran isn't running any longer.
>> Isn't there some way to have these remote XP boxes act the same as a
>> Win2k3
>> Server would act when you remote into it? I read something about a
>> "/console"
>> switch but this does not seem to change anything.
>> I've searched MS for answers but have been unsuccessful. Sure would
>> appreciate some help.
>> Thanks,
>> Jim
>



.

Loading