Symantec Management Platform (Notification Server)

With Task Server 6, how are tasks or jobs that were scheduled 'once' or 'run now' handled when the client misses the time to execute, because it was offline, or had no network connection?

The best practices doc 38364, at the end page 31 states that the job will not run or be rescheduled, and the job will expire.

I've tried this with a client, where a power management 'reboot' task was scheduled to run, but I took the client offline before sending the task.  I waited two hours and then brought the client back online.  The client immediately received the task and proceeded to reboot.

I just want a clear explanation of how missed schedules are handled by Task Server client task/jobs.

Thanks.

Software delivery uses a default internal clock of 360 minutes (the max) to kill a running task. This can even be seen when configuring inventory tasks.

The best practices article, as you have pointed out, hints at this but obviously doesn't provide a solution. The Task Server help guide is even more vague (wrong?) in that it says on page 20 (advanced task options) that 30 minutes is the default and max time for a task to run.

So I would think six hours would be the max window, unless you configure it under advanced for less than that (yet that only allows for 30 minutes).

Like I said, interesting...