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)Ar@T0H+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.)