I have a windows 2003 enterprise R2 server running SP2 and trying to
get 2 scripts to run as scheduled tasks on a nightly basis.
What seems to happen is they run once after I set the password for
them. Than the next night they will not run stating "could not
start" . If I go in and set the password again I can run them
manually and they will run once more than they give me the same error
the next night.
The account that it is running under doesn't seem to matter what I
use, I created a local account in the admin group, a domain account
and gave it admin privledges to the box and even used the domain
administrator account which all produce the same result.
Has anyone seen this before?

Tim

Hello Tim,

Give the account the security right "logon as a batch job" in your GPO.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I have a windows 2003 enterprise R2 server running SP2 and trying to
> get 2 scripts to run as scheduled tasks on a nightly basis.
> What seems to happen is they run once after I set the password for
> them. Than the next night they will not run stating "could not
> start" . If I go in and set the password again I can run them
> manually and they will run once more than they give me the same error
> the next night.
> The account that it is running under doesn't seem to matter what I
> use, I created a local account in the admin group, a domain account
> and gave it admin privledges to the box and even used the domain
> administrator account which all produce the same result.
> Has anyone seen this before?
> Tim
>

On Jun 14, 11:32 am, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
> Hello Tim,
>
> Give the account the security right "logon as a batch job" in your GPO.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > I have a windows 2003 enterprise R2 server running SP2 and trying to
> > get 2 scripts to run as scheduled tasks on a nightly basis.
> > What seems to happen is they run once after I set the password for
> > them. Than the next night they will not run stating "could not
> > start" . If I go in and set the password again I can run them
> > manually and they will run once more than they give me the same error
> > the next night.
> > The account that it is running under doesn't seem to matter what I
> > use, I created a local account in the admin group, a domain account
> > and gave it admin privledges to the box and even used the domain
> > administrator account which all produce the same result.
> > Has anyone seen this before?
> > Tim

Is there any other way to do it besides changing the GPO?

Hello Tim,

Open Administrative tools, local security policy and configure the right
there.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> On Jun 14, 11:32 am, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
>
>> Hello Tim,
>>
>> Give the account the security right "logon as a batch job" in your
>> GPO.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
>>> I have a windows 2003 enterprise R2 server running SP2 and trying
>>> to
>>> get 2 scripts to run as scheduled tasks on a nightly basis.
>>> What seems to happen is they run once after I set the password for
>>> them. Than the next night they will not run stating "could not
>>> start" . If I go in and set the password again I can run them
>>> manually and they will run once more than they give me the same
>>> error
>>> the next night.
>>> The account that it is running under doesn't seem to matter what I
>>> use, I created a local account in the admin group, a domain account
>>> and gave it admin privledges to the box and even used the domain
>>> administrator account which all produce the same result.
>>> Has anyone seen this before?
>>> Tim
> Is there any other way to do it besides changing the GPO?
>

On Jun 14, 12:48 pm, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
> Hello Tim,
>
> Open Administrative tools, local security policy and configure the right
> there.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > On Jun 14, 11:32 am, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
>
> >> Hello Tim,
>
> >> Give the account the security right "logon as a batch job" in your
> >> GPO.
>
> >> Best regards
>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> I have a windows 2003 enterprise R2 server running SP2 and trying
> >>> to
> >>> get 2 scripts to run as scheduled tasks on a nightly basis.
> >>> What seems to happen is they run once after I set the password for
> >>> them. Than the next night they will not run stating "could not
> >>> start" . If I go in and set the password again I can run them
> >>> manually and they will run once more than they give me the same
> >>> error
> >>> the next night.
> >>> The account that it is running under doesn't seem to matter what I
> >>> use, I created a local account in the admin group, a domain account
> >>> and gave it admin privledges to the box and even used the domain
> >>> administrator account which all produce the same result.
> >>> Has anyone seen this before?
> >>> Tim
> > Is there any other way to do it besides changing the GPO?

It looks like it needs to be done with a GPO as this is locked by
Group policy and not editable.