Re: scheduled jobs not logging on

From: Dave (noone_at_nowhere.com)
Date: 08/31/04


Date: Tue, 31 Aug 2004 10:00:29 -0400

go back in to each task and re-enter the password for the account it is
supposed to run as. have seen a machine here forget the scheduled task
passwords also, apparently randomly. entering the passwords again seems to
fix it.

"JoeElla" <jebright@gcwda.com> wrote in message
news:O5LOoG2jEHA.3428@TK2MSFTNGP11.phx.gbl...
> I have windows2000 service pack 4. I have about 7 jobs set to run from
> scheduled tasks. These have worked well up until about three weeks ago.
> Suddenly they run only sporadically. maybe one will run a day, and not
the
> same one. The only error message that I get is "Could not log on".
PLEASE
> HELP.
>
>



Relevant Pages

  • Re: Restart and Logon with Scheduled task
    ... Accounts: Limit local account use of blank passwords to console logon only. ... Run Scheduled Task without a Password ...
    (microsoft.public.windowsxp.general)
  • RE: Scheduled Tasks
    ... if your accounts require passwords,you may have to ... >I have set up a scheduled task to run Disk Cleanup as I ... >unlike W98 Disk Cleanup starts but will not run automatically. ...
    (microsoft.public.windowsxp.general)
  • Re: at HH:MM /interactive cmd /k
    ... (create a new account in 'User and ... Passwords'). ... It might also be the WindowPosition and or WindowSize are off ... | whats happening when my scheduled task is running? ...
    (microsoft.public.win2000.general)
  • Re: Account lockouts
    ... for reusable passwords and the AAA infrastructures that rely upon them? ... In that context, account lockout policy -- duration, threshold, lockout ... > cracking attacks. ...
    (microsoft.public.security)
  • Re: Deleting Admin Account
    ... administrative level account to change the Type of the Admin account ... created to a limited account (or create yourself a third account - non-admin ... The built-in administrator cannot be changed from the administrative level, ... You should password protect (with different passwords would be best) each ...
    (microsoft.public.windowsxp.setup_deployment)