I know Microsoft thinks the "new" task scheduler is just the cat's meow.
But is anyone having trouble getting it to perform as functionally and
easily as those of previous Windows versions?
For example, to se up a scheduled task requires that the user
(admiknistrator) enter his/her password. But what about an unattended
computer that reboots due to whatever reason and never progresses past
the "welcome" screen so that Task Scheduler will never be triggered?
There are a lot of other funnies too.
Anyone know of third party s/w to replace MS Task Scheduler that will
perform much like previous versions???
Thanks.
No, not having any trouble with it - in fact I much prefer it. Fully
scriptable, ability to link events to tasks etc.
Re your gripes, there's a 'Run whether user is logged on or not' option
on a
task's general tab where you can enter your password, and there's also an
'On startup' trigger.
I appreciate your comments. But perhaps there is something fundamental
I am missing. When setting up a task (simply to run a program on a
schedule) I use two triggers: (1) At startup [in case I have a reboot
when I'm not at the computer] and; (2) The schedule I've allocated for
the task to run (in this case every 10 minutes for 24 hours, then repeat
daily...logs temperature from an external sensor).
When I restart the computer to test the task scheduler, nothing starts
unless I actually log in at startup with my admin password. Otherwise
the "welcome" screen just sits there, no task execution, nothing. What
am I missing here. It seems like MS has made an improvement in the task
scheduler but I can't make it work as advertised.
I'm not a professional IT person but any help will be appreciated.
Thanks.
This could be a number of things.
The task might need to be run elevated (checkbox on the general tab), it
may be running, but failing due to a permissions or dependency on another
service problem, or there may be another problem eg within the code for
the program that is being run that requres you to be logged for it to run
properly.
There's a node in Event Viewer, which provides useful information on
whether tasks ran or not, and might provide error code information too, as
well as the history tab for the task in Task Scheduler.
Applications and Services Logs > Microsoft > Windows > Task Scheduler >
Operational
(you may need to right-click it to enable it)
If you think there's a problem with the way the task is set up, then you
could paste the xml for the task in here (right-click the task > Export >
Open up the xml file in notepad), and I'll see if I can spot anything
obvious. [Change your computer name and user name if you like, but leave
the rest as is]
