Windows Task Scheduler (a.k.a Task Scheduler) and SQL Server 2000/2005
After the problems on the SQL Server 2000 cluster with the new hotfix installer, a case was opened with Microsoft Support engineer allocated to us (see article prior to this).
Well, after some more looking, SQL Server 2005 will use Windows Task Scheduler for setup on Clusters too.
OK, but Microsoft recommends that you disable Task Scheduler as a security precaution. Great.
According to the SQL Development team, the use of Task Scheduler is here to stay. In some respect I see where they are coming from as they can then use the "Run As" on the remote host to launch the process under the correct account.
Currently, if things fail, the task is left on the remote machine, but the directory the task refers to is deleted.
We have now opened a DCR (Change request) that Microsoft either documents this feature and process very well, including updating their security lockdown documentation, or make the hotfix installer/Setup clever enough to start the task scheduler on the remote hosts, run the processes required and shut it down again.