Anyone yet discovered a solution to the Vista scheduler problem?

[JethroUK©]

Anyone yet discovered a solution to the Vista scheduler problem - being that
if ever you log out or reboot (and login again), the scheduler 'forgets' the
user privileges & so any/all attempts to resume the schedule fail, fail,
fail, fail, grrrrrrrrrrrrrrrrrr

This was documented when Vista first appeared & reported solution was just
keep resetting the user every time - but it sorta defeats the object of an
otherwise automated scheduled task

I have tried setting the user as 'system' (as per defrag task, etc) but
that doesn't work either

 

[JethroUK©]

Everytime i log out or reboot (even if i login again) Vista forgets my user
privileges so it cant run any scheduled programs

My username is still appears set (but won't work) - i have to reset the very
same user (me) - then it will work fine until the next time i log out

It also always reports a user (my wife) error every time i open it - she has
no tasks set up so i can't see the problem but there could be a connection -
have you got any other users setup under Vista?

 

[JethroUK©]

Every user has tasks, created by windows. What are the exact error
messages and try switching off UAC.

Have tried switching off UAC made no difference

There are no task set up under her actual user name (only system tasks) but
the report actually mentions her specific user name

 

[the wharf rat]

Everytime i log out or reboot (even if i login again) Vista forgets my user
privileges so it cant run any scheduled programs

Beleive it or not it's working as designed. Either stay logged
in or see if you can use the "run as" options. Those don't always work though.

It also always reports a user (my wife) error every time i open it - she has

Well, having been through a very unpleasant divorce I'm tempted
to respond that of course your wife is an error... That would be bitter
and cynical though.

 

[JethroUK©]

Beleive it or not it's working as designed.

Not at all

There is an option "whether logged in or not" which i think is pretty
explicit

It a Vista issue