Now that Task Scheduler 2.0 in WS2008 has been made rather more complicated than it was in WS2003 and before, I wonder whether anyone has come across any discussion of ‘best practices’ in the setting up of scheduled tasks to do the things you did in WS2003, say?
On an extremely brief acquaintance, it would seem to be sensible to set up a new folder immediately below the Task Scheduler Library, at the same level as “Event Viewer Tasks” and “Microsoft”, and put administrator- and server-specific tasks in there, to keep them away from anything that Microsoft has created. Subfolders would be useful in much the same way as subdirectories are for files, to associate similar tasks, if there are enough of them.
I note that you can’t readily move folders or tasks. Create the new folder in the right place/delete it from the wrong place seems to be the only possibility. I’ve been able to export a scheduled task to an XML file, and import it into the correct folder, as an inefficient move method.
Is it still a good idea to set up a “service account” which runs as administrator, and which doesn’t have/need an Exchange mailbox?
Would anyone with experience of Task Scheduling in WS2008 care to comment and elaborate, please? Thanks!
BATcher
Plethora means a lot to me.
