Defrag scheduling/password issue

  • Thread starter Thread starter Help with scheduling issue
  • Start date Start date
H

Help with scheduling issue

I have no difficulty establishing a schedule task to defrag computer that
uses XP-Pro, SP3. However, the setup procedure demands I enter a password
and fails because I don't. I don't enter a password because I do not use a
Windows password and therefore have no password to give it. Ergo, the task
never runs. Is this a Catch-22 in Windows, or am I missing something?
 
The scheduler will not run unless you have at least one account that has a
password.
So create a new account and give it a password or password protect your
account.

JS
http://www.pagestart.com


"Help with scheduling issue" <Help with scheduling
(e-mail address removed)> wrote in message
news:[email protected]...
 
Turns out it IS a Catch-22.

JS said:
The scheduler will not run unless you have at least one account that has a
password.
So create a new account and give it a password or password protect your
account.

JS
http://www.pagestart.com


"Help with scheduling issue" <Help with scheduling
(e-mail address removed)> wrote in message
 
"Help with scheduling issue" <Help with scheduling
(e-mail address removed)> wrote in message
I have no difficulty establishing a schedule task to defrag computer that
uses XP-Pro, SP3. However, the setup procedure demands I enter a password
and fails because I don't. I don't enter a password because I do not use
a
Windows password and therefore have no password to give it. Ergo, the
task
never runs. Is this a Catch-22 in Windows, or am I missing something?

It's the default behaviour for the Windows Task Scheduler, and it's there
for security reasons.

You *can* disable it, but this is a bad idea, again for security reasons.

It's much better to just add a password to your account, then use tweakUI or
"control userpasswords2" to set Autologon.

http://www.internetfixes.com/xp_automatic_logon/

HTH
-pk
 
"Help with scheduling issue"
Turns out it IS a Catch-22.

No, it's not a catch-22, it's just a not-very-well documented security
feature.

Most of the clearest documentation on it comes from 3rd party
knowledgebases, in the form of answers to "my scheduled backup or virus scan
didn't run".

HTH
-pk
 
Back
Top