Scheduler without passwords?

I am the only user of this computer. I do not have passwords (yes, I am
aware of the security risks this involves; my decision).

This morning, I attempted to use task scheduler for the first time on
XP. I got a "you don't have permissions" message; on Googling the error
code (XP's "internal" help was hopeless, even though I have it set to be
allowed to go online), I discover that you can't use Task Scheduler if
you have blank passwords.

Has anyone the solution to this, other than setting a password? I am
aware of - and have downloaded and installed, and it works well (with no
passwords) - System Scheduler from http://www.splinterware.com, but I
find it inconceivable that TS is limited in this way.

(Some of the Microsoft pages mentioned a way of getting round the
limitation, but they seemed to be related to something with a different
name to Task Scheduler.)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL-IS-P--Ch++(p)[email protected]+Sh0!:`)DNAf
** http://www.soft255.demon.co.uk/G6JPG-PC/JPGminPC.htm for ludicrously
outdated thoughts on PCs. **

"Mr. Notlob, there's nothing wrong with you that an expensive operation can't
prolong!" - Monty Python

J. P. Gilliver (John) wrote:

I am the only user of this computer. I do not have passwords (yes, I am
aware of the security risks this involves; my decision).

This morning, I attempted to use task scheduler for the first time on
XP. I got a "you don't have permissions" message; on Googling the error
code (XP's "internal" help was hopeless, even though I have it set to be
allowed to go online), I discover that you can't use Task Scheduler if
you have blank passwords.

Has anyone the solution to this, other than setting a password? I am
aware of - and have downloaded and installed, and it works well (with no
passwords) - System Scheduler from http://www.splinterware.com, but I
find it inconceivable that TS is limited in this way.

(Some of the Microsoft pages mentioned a way of getting round the
limitation, but they seemed to be related to something with a different
name to Task Scheduler.)

Task Scheduler runs an event under the specified Windows account. To do
that, it needs the password for that account. That password cannot be
blank. So if you don't want to login then don't. Use auto-login to
automatically load your Windows account when you boot Windows. You will
still have a username and password for that account but YOU won't have
to bother entering them, and you satisfy the need for Task Scheduler
(and other apps) that demand that the account under which they run a
program will do so with the proper login credentials.

To facilitate auto logging into Windows when you boot it, get
Microsoft's TweakUI powertoy. Or Google on how to do it. Just remember
that ANYONE that walks over to your computer can pretend to be you and
do whatever they want, including "friends" (and friends of friends of
friends that you don't even know but still get invited to your parties)
and the thief that steals your computer.

In message , VanguardLH
writes:
J. P. Gilliver (John) wrote:

I am the only user of this computer. I do not have passwords (yes, I am
aware of the security risks this involves; my decision).
[]
Has anyone the solution to this, other than setting a password? I am
[]
Microsoft's TweakUI powertoy. Or Google on how to do it. Just remember

I intend to install XP's TweakUI (I'm familiar with it from '98).

that ANYONE that walks over to your computer can pretend to be you and
do whatever they want, including "friends" (and friends of friends of
friends that you don't even know but still get invited to your parties)
and the thief that steals your computer.

(I don't have parties.) I put the "I am`aware" line in, in the (futile)
hope of avoiding the (well-intentioned, I'm sure) advice.

So in short, Task Manager can't be made to work without passwords,
though their use can be made invisible (surely negating their effect).
--
J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL-IS-P--Ch++(p)[email protected]+Sh0!:`)DNAf

We need a reversal of the old saying: "DON'T do unto others as you would have
them NOT do unto you." (Paraphrase from "The Moral Maze", 1998-11-21: it was an
attempt - quite good I thought - to get a modern [and non-specific] version.)

J. P. Gilliver (John) wrote:

So in short, Task Manager can't be made to work without passwords,
though their use can be made invisible (surely negating their effect).

Task *Scheduler* (not Task Manager) demands to know the login
credentials for the account under which an event will run. A blank
password is still a password but just how could YOU specify a blank
password? Not entering anything into a field doesn't actually equate to
entering blanks or a null value. It means you didn't enter anything.

http://support.microsoft.com/kb/310715

I believe if you schedule jobs in Task Scheduler to run under the SYSTEM
account that you don't need to add a password. Of course, these jobs
don't run under the privileges of your Windows account but get all the
privileges of the SYSTEM account.

You cannot use the GUI interface provided by the Task Scheduler program
to define jobs that run under the SYSTEM account. You have to use a
command prompt to run the 'at' command. To figure out the command
syntax for the 'at' program, run "at /?" at a command prompt (i.e., open
a command shell to load a console window and enter the command at the
prompt).

http://support.microsoft.com/kb/313565
"Note When you use the at command, the scheduled task is run by using
the credentials of the system account."

In message , VanguardLH
writes:
J. P. Gilliver (John) wrote:

So in short, Task Manager can't be made to work without passwords,
though their use can be made invisible (surely negating their effect).

Task *Scheduler* (not Task Manager) demands to know the login

Oops (-:

credentials for the account under which an event will run. A blank
password is still a password but just how could YOU specify a blank
password? Not entering anything into a field doesn't actually equate to
entering blanks or a null value. It means you didn't enter anything.

I see what you mean; I can see arguments both ways for whether not
entering anything should count as entering a blank one or not.

http://support.microsoft.com/kb/310715

I believe if you schedule jobs in Task Scheduler to run under the SYSTEM
account that you don't need to add a password. Of course, these jobs
[]
You cannot use the GUI interface provided by the Task Scheduler program
to define jobs that run under the SYSTEM account. You have to use a
command prompt to run the 'at' command. To figure out the command
syntax for the 'at' program, run "at /?" at a command prompt (i.e., open
[]
Thanks for that; useful to know it is there!

(Sad to find myself saying this, but I think I find the gooey interface
less bother, so will probably continue to use the splinterware
alternative. I'd say the managing of existing events is almost certainly
easier via GUI.)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL-IS-P--Ch++(p)[email protected]+Sh0!:`)DNAf

We need a reversal of the old saying: "DON'T do unto others as you would have
them NOT do unto you." (Paraphrase from "The Moral Maze", 1998-11-21: it was an
attempt - quite good I thought - to get a modern [and non-specific] version.)