This person did not do their homework.
"Scheduled tasks" is buggy, unreliable and lost some of the
functionality that was there with the old "at" scheduler in NT.
For Example, you cannot control it from the command line and if you do any remote management as I'm sure most of us do, it is unusable. Next, if you open/review/modify an existing task, it looses the security context and you must re-enter the username/password, Lastly, Scheduled tasks randomly lose their username/password context information
and simply stop running. This is a reported bug as listed on m$ website but you have to pay for a support call to get "the fix" Huh? How much did I pay for this software?!?
Should I trust my data to this? ... I think not.

Count Ludwig 4/9/2001 9:48:07 PM

The article does not make it clear that it is impossible to schedule tasks on remote machines without quite some effort, unlike using the "at" command, which can under NT4.

Sure you can copy .job files, but they lose their security information when they arrive at the remot machine (though I do see why this should be). This means you must use the GUI tool to set a username and password for the remote job to run.

As someone who has been used to being able to schedule remote "at" jobs on hundreds of machines, this is less than useful.

An equivalent command line tool to "at" to do remote job submission in Windows 2000 would have been a good idea.

Paul Belli 2/7/2001 1:48:03 AM