Scheduled task - minimum security requirements

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I have a simple scheduled task that runs under administrator equivalents
credentials. When I change the scheduled task "Run as" credentials to a user
who is not an administrator, the batch fails to start.

Q1. Is administrator equivalency a requirement for the scheduled task "run
as" security context?

Q2. What are the minimum requirements for the scheduled task "run as"
account? Where are these published?

Environment:
 
NKX said:
Hello,

I have a simple scheduled task that runs under administrator equivalents
credentials. When I change the scheduled task "Run as" credentials to a user
who is not an administrator, the batch fails to start.

Q1. Is administrator equivalency a requirement for the scheduled task "run
as" security context?

Q2. What are the minimum requirements for the scheduled task "run as"
account? Where are these published?

Environment:
Click to expand...

Click Start / run / gpedit.msc
Local Computer Policy / Computer Configuration / Windows Settings /
Security Settings / Local Policy / User Rights / Logon as a batch job.

I think you need to modify your batch file, because it will
delete the wrong files in case the folder d:\data does not
exist. The following would be much safer:

@echo off
del /f /q d:\data\*.txt
 
Thanks for your timely response. I have made that change to the local
security policy and refreshed the machine_policy but it still fails under a
non admin user account. I have checked the effective policy setting to ensure
that a domain policy is not overwiding the local policy to allow the user
login as a batch job.
 
You write that the task fails to start but you did not
report how you reached this conclusion. You must
examine the Task Scheduler report in order to see
what exactly happens. It's accessible under the
Advanced pull-down menu.


NKX said:
Thanks for your timely response. I have made that change to the local
security policy and refreshed the machine_policy but it still fails under a
non admin user account. I have checked the effective policy setting to ensure
that a domain policy is not overwiding the local policy to allow the user
login as a batch job.
Click to expand...
 
The task ends with a non 0 exit code. "Result: The task completed with an
exit code of (1)"
 
The report contradicts your claim. The task ***did***
start but it terminated with an error. Post your batch file
(or whatever it is you scheduled) if you require further
assistance.


NKX said:
The task ends with a non 0 exit code. "Result: The task completed with an
exit code of (1)"
Click to expand...
 
Back
Top