Hi,
we decided to give more flexibilty to our users to defer the execution of a task. So we use "Run options" and activate the option "Allow the user to defer execution of this task".
We choose 12 hours, that users can defer the jobs up to 12 hours. It seems that some of the users choose the complete 12 hours in the pop up window, which is shown after transfering the job to the client’s agent (the "Alert user" task was executed), but at the end of the day, some of them shut down their client, so that the job wasn't started. In the next morning the users start their client and the Symantec Agent executes the first task of the job correctly, but stops the job after this first task with an unknown exception (compare the attached picture "1.jpg").
We could reproduce this behaviour with another client which was offline over night and was started at the next day. Clients which were online again on the same day, but after the defined deferment time had no problem (Example: The choosen time to defer was 5 minutes, after choosing the time we shut down the client immediatly and started it after 10 Minutes. The job was executed correctly).
It looks like that there is a problem, when scheduling the task on one day WITH the possibility to defer for the user and starting this task on the client on the next day. It doesn’t matter if the user has seen the scheduling window and deferred the job or if the client was already offline in the moment we scheduled the job for the client.
Hint: The first task of the job is the execution of a batch-task.
Thanks
Simon