Re: Terminal services and Scheduled tasks
- From: "Jeff Pitsch" <jeff@xxxxxxxxxxxxxxxxx>
- Date: Mon, 20 Mar 2006 16:15:57 -0500
I'm not sure I understand. When a server boots, typically it is not set to
logon automatically. Session 0 is simply logging in as if you were standing
in front of the physical server. as well, logging in to the console
automatically is not done through scheduled tasks but by some simple
regedits. Also, when you log onto the console session, if it is not the
same credentials, you are logging off the user that was on the console to
begin with.
Jeff Pitsch
Microsoft MVP - Terminal Services
http://www.sbcgatekeeper.com
Your Terminal Services Security Website
"SerGioGio" <nospam> wrote in message
news:uImSfW9SGHA.4340@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
On a WsK3 server, I have a program setup in scheduled tasks to start "when
my computer starts".
The program does start successfully "when my computer starts" in console
session (session 0) but when I remote connect to the box (/console switch
of mstsc), I cannot see the window of the program, although I am in
session 0!
Why is that so? Is there any way to schedule an application to start "when
my computer starts" and still be able to see the application's GUI?
Thanks in advance,
SerGioGioGio
.
- Follow-Ups:
- Re: Terminal services and Scheduled tasks
- From: SerGioGio
- Re: Terminal services and Scheduled tasks
- References:
- Terminal services and Scheduled tasks
- From: SerGioGio
- Terminal services and Scheduled tasks
- Prev by Date: Re: Installing MSOffice Service Packs on a Terminal server
- Next by Date: Re: User event tracking
- Previous by thread: Terminal services and Scheduled tasks
- Next by thread: Re: Terminal services and Scheduled tasks
- Index(es):
Relevant Pages
|