Scheduled jobs and terminal server

[Guest roger.orr@gmail.com]

When using scheduled tasks under Windows Server 2003 a job will run in

the context of a terminal services session for the specified user, if

available, and run in session 0 if not.

 

However, this means that if the terminal services user logs out while

the job is running then the job is aborted.

 

Is there any way to supress this behaviour and prevent scheduled jobs

running in terminal services sessions (this was the behaviour on

Windows 2000) ?

 

Regards,

Roger.

[Guest Pegasus \(MVP\)]

Re: Scheduled jobs and terminal server

 

 

<roger.orr@gmail.com> wrote in message

news:380fad97-3820-4b6f-bd48-a76a2a64dd3c@60g2000hsy.googlegroups.com...

> When using scheduled tasks under Windows Server 2003 a job will run in

> the context of a terminal services session for the specified user, if

> available, and run in session 0 if not.

>

> However, this means that if the terminal services user logs out while

> the job is running then the job is aborted.

>

> Is there any way to supress this behaviour and prevent scheduled jobs

> running in terminal services sessions (this was the behaviour on

> Windows 2000) ?

>

> Regards,

> Roger.

 

The usual method is to use a dedicated account for scheduled

jobs so that they become independent of any console or

terminal session.

[Guest roger.orr@gmail.com]

Re: Scheduled jobs and terminal server

 

On 11 Mar, 11:09, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:

> The usual method is to use a dedicated account for scheduled

> jobs so that they become independent of any console or

> terminal session.

 

Thanks for the reply.

I think we'll do something similar -- create new accounts to use

only for terminal services sessions and leave the jobs, as we want

to retain the actual accounts used for the jobs.

 

Roger.