Results 1 to 4 of 4
  1. #1
    Super Moderator BATcher's Avatar
    Join Date
    Feb 2008
    Location
    A cultural area in SW England
    Posts
    3,414
    Thanks
    33
    Thanked 195 Times in 175 Posts
    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

    Time prevents everything happening all at once...

  2. #2
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,180
    Thanks
    47
    Thanked 983 Times in 913 Posts
    I generally dislike WTS, primarily because it is difficult to monitor tasks, but also because it is difficult to backup. It could easily be so much better!
    You can view the tasks and their status, but it doesn't even have the option to add an event log entry on success or failure.
    Backup works if you backup the system state of the server, but you can't backup the tasks and the credentials in a nice easy package.
    Note: this is the case for Windoze up to 2003, 2008 may be better but I'm not confident.

    cheers, Paul

  3. #3
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts
    FYI, the backup process in Server 2008 is a completely different beast that the version with 2003, or the version that came with SBS 2003 which I found to be a significant improvement over standard 2003. So far we've had excellent results with the 2008 version.
    Wendell

  4. #4
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,180
    Thanks
    47
    Thanked 983 Times in 913 Posts
    I checked out TS in 2008 today and it is as I feared, pretty much the same as it was on 2003, with some minor updates and one really annoying bug.

    * There is still no record of task operation that I could find, so you don't know if it is actually running.
    * You can now export tasks easily into XML and the user name is stored, but you still need to remember the password to restore the task - it's better than it was.
    * You can run tasks without providing a password as long as the task runs whilst the user is logged on.
    * TS will happily lock your account out if you get the password wrong the first time you attempt to save the task. It does not seem to be possible to re-enter your password, every time you click OK TS uses the cached incorrect password and then complains that it's wrong. Logging out and in again seems to fix the problem.

    cheers, Paul

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •