Logon as a batch job

I've got a new Windows XP Pro machine that is part of a
domain. This computer needs to run several scheduled
tasks. I have set up the tasks and they run just fine
when I click 'Run' from their context menus in the
scheduled task folder.

When they try to run overnight at their scheduled time
they do not start. The status says 'Could not start'. The
log file says:

"The attempt to log on to the account associated with the
task failed, therefore, the task did not run.
The specific error is:
0x80070569: Logon failu the user has not been
granted the requested logon type at this computer.
Verify that the task's Run-as name and password
are valid and try again."

In looking through the docs it appears the account I'm
using for the Run-as (which is a pretty standard domain
account) needs the 'Logon as a batch job' user right.
When I go into security settings (having logged in as the
local administrator on this machine) I can find that user
access right just fine, but the buttons are disabled so
that I can't add or remove any users from that right.

Where am I supposed to change this user access right if I
can't do it from here? Is there something else I should
have done to fix that scheduled task problem?

Thanks for any tips.

Don't set this setting in the local policy. Set it at domain level... (e.g.
domain or OU level)...

Mike

"csh" wrote in message
...
I've got a new Windows XP Pro machine that is part of a
domain. This computer needs to run several scheduled
tasks. I have set up the tasks and they run just fine
when I click 'Run' from their context menus in the
scheduled task folder.

When they try to run overnight at their scheduled time
they do not start. The status says 'Could not start'. The
log file says:

"The attempt to log on to the account associated with the
task failed, therefore, the task did not run.
The specific error is:
0x80070569: Logon failu the user has not been
granted the requested logon type at this computer.
Verify that the task's Run-as name and password
are valid and try again."

In looking through the docs it appears the account I'm
using for the Run-as (which is a pretty standard domain
account) needs the 'Logon as a batch job' user right.
When I go into security settings (having logged in as the
local administrator on this machine) I can find that user
access right just fine, but the buttons are disabled so
that I can't add or remove any users from that right.

Where am I supposed to change this user access right if I
can't do it from here? Is there something else I should
have done to fix that scheduled task problem?

Thanks for any tips.

Looks like that was the problem. I won't know for sure
until it runs tonight but I was finally able to set the
access right.

Thanks for the tip.

csh


-----Original Message-----
Don't set this setting in the local policy. Set it at
domain level... (e.g.
domain or OU level)...

Mike

"csh" wrote in
message
...
I've got a new Windows XP Pro machine that is part of a
domain. This computer needs to run several scheduled
tasks. I have set up the tasks and they run just fine
when I click 'Run' from their context menus in the
scheduled task folder.

When they try to run overnight at their scheduled time
they do not start. The status says 'Could not start'.
The
log file says:

"The attempt to log on to the account associated with
the
task failed, therefore, the task did not run.
The specific error is:
0x80070569: Logon failu the user has not been
granted the requested logon type at this computer.
Verify that the task's Run-as name and password
are valid and try again."

In looking through the docs it appears the account I'm
using for the Run-as (which is a pretty standard domain
account) needs the 'Logon as a batch job' user right.
When I go into security settings (having logged in as
the
local administrator on this machine) I can find that
user
access right just fine, but the buttons are disabled so
that I can't add or remove any users from that right.

Where am I supposed to change this user access right
if I
can't do it from here? Is there something else I should
have done to fix that scheduled task problem?

Thanks for any tips.




.