Re: Task Scheduler
- From: "Pegasus \(MVP\)" <I.can@xxxxxxx>
- Date: Tue, 18 Oct 2005 21:16:42 +1000
This was like pulling a tooth!
Your problem is that your system policy is incorrect. Run
gpedit.msc, then follow this path:
Local Computer Policy / Computer Configuration / Windows Settings /
Security Settings / Local Policy / User Rights. Now enable "Logon as
a batch job".
It's not a good idea to run scheduled jobs under the same
account as the foreground account, because they interfere
with the foreground account. I recommend you use a
different account.
"Sergey Usov" <sergeyusov@xxxxxxxxx> wrote in message
news:OOFqMN90FHA.2876@xxxxxxxxxxxxxxxxxxxxxxx
> The scheduled job is Backup of directory on local drive to another local
> drive.
> The account is "local computer/Administrator".
> The job is scheduled with "Run as local computer/Administrator", password
is
> entered.
> The foreground account is "local computer/Administrator".
> But it runs only once. The second time it gives:
> =========
> 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 failure: the user has not been granted the requested
> logon type at this computer.
> =========
> But, if next day before scheduled time I enter password in "Enter
password"
> next to "Run as" it works OK.
> It's all quite ridiculous.
>
> "Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
> news:utFyO360FHA.2076@xxxxxxxxxxxxxxxxxxxxxxx
> > Once a job is scheduled, it will not ask you for a password.
> > However, if the scheduled job runs under the same account
> > as your current foreground account, and if the job has
> > insufficient access rights to a network resource then it will
> > ask you for a suitable account name / password.
> >
> > In other words: If the scheduled job must access the share
> > \\YourServer\YourShare then you must run it under an
> > account that has appropriate access rights to \\YourServer\YourShare.
> >
> > Rather than talking about your problem theoretically, I suggest
> > you tell us exactly what your scheduled task is attempting to
> > do and at what stage the account/password prompt appears.
> >
> >
> > "Sergey Usov" <sergeyusov@xxxxxxxxx> wrote in message
> > news:entqKd60FHA.464@xxxxxxxxxxxxxxxxxxxxxxx
> >> Is it possible to ask Task Scheduler once to run a job everyday without
> >> confirmation of password?
> >>
> >> "Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
> >> news:uhaMK450FHA.464@xxxxxxxxxxxxxxxxxxxxxxx
> >> >
> >> > "Sergey Usov" <sergeyusov@xxxxxxxxx> wrote in message
> >> > news:u1wW7v50FHA.2880@xxxxxxxxxxxxxxxxxxxxxxx
> >> >> Is anybody using Task Scheduler for everyday runs?
> >> >> Why it asks to enter logon and password everyday for Administrator
> >> > account,
> >> >> otherwise logon failure
> >> >>
> >> >>
> >> >
> >> > You can enter any account name / password when scheduling a task,
> >> > as long as you make sure that the chosen account has sufficient
> >> > access rights to the resources needed by the scheduled task (e.g.
> >> > network shares).
> >> >
> >> > And why do you have to enter an account / password? Simple:
> >> > Because Windows Server is a secure operating system. Without
> >> > an account name / password, you would have no security!
> >> >
> >> >
> >>
> >>
> >
> >
>
>
.
- References:
- Task Scheduler
- From: Sergey Usov
- Re: Task Scheduler
- From: Pegasus \(MVP\)
- Re: Task Scheduler
- From: Sergey Usov
- Re: Task Scheduler
- From: Pegasus \(MVP\)
- Re: Task Scheduler
- From: Sergey Usov
- Task Scheduler
- Prev by Date: Re: Rebuild server.
- Next by Date: Re: Cannot logon to damain
- Previous by thread: Re: Task Scheduler
- Next by thread: Re: W2003 Printserver -> Settings on the client
- Index(es):
Relevant Pages
|
