J
JOE
Hi,
I thought this might be the proper forum to ask
a "general question" about Microsoft's philosophy as it
applies to sheduling tasks in Windows.
As I look at the SCHEDULED TASKS under CONTROL PANEL,
I only find NORTON tasks. Yet every other task
programmed by Microsoft seems to avoid this tool. For
example, MSAS has its own screen to set its scheduled
runs, and so does Microsoft Automatic UPDATE. There may
be others.
It appears that Microsoft is not using the tool it
designed for WINDOWS, and relegates it only for third
party product sheduling. Does this make sense? I thought
the purpose of SHEDULED TASKS, was to "centralize" timed
task execuion throughout the Windows environment in one
place, where SYSADMIN can easily monitor and modify these
timings. I mean, its a darned nuisance to travel through
the Windows Universe, just to set each application's
schedule, when you want to organize things. It takes a
lot of time, effort, and is error prone. I shouldn't hav
to launch each individual application, when I want to
make several systemwide scheduling changes.
May I suggest that someone at Microsoft look at
perhaps at least "duplicating" these scheduled task
control blocks, inside "SCHEDULED TASKS" under Control
Panel. You can still have a specific window for MSAS
scheduling, if you like, but that information should
also be easily and directly "modifiable" centrally. The
same should be done for WINDOWS AUTOMATIC UPDATE, and
all other similar functions.
Joe
I thought this might be the proper forum to ask
a "general question" about Microsoft's philosophy as it
applies to sheduling tasks in Windows.
As I look at the SCHEDULED TASKS under CONTROL PANEL,
I only find NORTON tasks. Yet every other task
programmed by Microsoft seems to avoid this tool. For
example, MSAS has its own screen to set its scheduled
runs, and so does Microsoft Automatic UPDATE. There may
be others.
It appears that Microsoft is not using the tool it
designed for WINDOWS, and relegates it only for third
party product sheduling. Does this make sense? I thought
the purpose of SHEDULED TASKS, was to "centralize" timed
task execuion throughout the Windows environment in one
place, where SYSADMIN can easily monitor and modify these
timings. I mean, its a darned nuisance to travel through
the Windows Universe, just to set each application's
schedule, when you want to organize things. It takes a
lot of time, effort, and is error prone. I shouldn't hav
to launch each individual application, when I want to
make several systemwide scheduling changes.
May I suggest that someone at Microsoft look at
perhaps at least "duplicating" these scheduled task
control blocks, inside "SCHEDULED TASKS" under Control
Panel. You can still have a specific window for MSAS
scheduling, if you like, but that information should
also be easily and directly "modifiable" centrally. The
same should be done for WINDOWS AUTOMATIC UPDATE, and
all other similar functions.
Joe
