Video Screencast Help

Jobs and Tasks shouldn't expire if the computer is offline

Created: 14 Oct 2011 | 11 comments
noodleNT's picture
8 Agree
0 Disagree
+8 8 Votes
Login to vote

In DS 6.9 scheduled tasks would stay scheduled untill the computer came online. NS7.X expires the tasks after a scheduled time the task was scheduled. This causes issues with offline computers never getting the task. So you have to watch it every day and there is no way to re-run the task on just the failed machines.

Comments 11 CommentsJump to latest comment

MinAung's picture

There is a way to increse the End Task Time out. The default value is from 5 to 2160 minutes. You need select your Job/Task and click on Advance > Task option. Click on the Check Box “End Task After” and key in the value that you want.

I hope this help.

0
Login to vote
Frank_RE's picture

Hello, we have the same Problem wit the End Task Time out. To set the Value in the Job to round 18 Day's works, but we need Jobs to run also after 18 Days.

To uncheck the Option "End Task After" dose not work. The Server terminate the job after a default Timeout from 600 Minutes.

Is there no way to set this default Timeout to an higher value ?

0
Login to vote
Alex Bizjajev's picture

Hi Frank,

May you specify the version of the product - is it 7.1.SP2 or 7.5?

Thank you,

Alex.

0
Login to vote
Frank_RE's picture

Hi Alex,

we use in Production 7.1 SP2 and in Testenviroment 7.5. In both it`s the same.

0
Login to vote
noodleNT's picture

Really this is a design flaw. If a task is scheduled on an offline computer the task will still show in a "Running" state. My opinion, this shouldn't happen. The computer should show "pending" until it comes online. Extending the timeout is a poor work around as you still want tasks to fail quickly if their was some sort of problem when the job was running.

0
Login to vote
Alex Bizjajev's picture

It seems like problem with the tasks time-out has been fixed in 7.1MP1 FP2, a kind of workaround has been described in KB http://www.symantec.com/business/support/index?pag... .

But as the problem re-occurs on a 7.5 I'm not sre this is a same issue.

0
Login to vote
Frank_RE's picture

Yes, Your right !

I agree and so it was in the Altiris Deployment Server 6.X. OK, no Timeout if ther was an Error..

How about a Fix Symantec ? Or is it all done ?

0
Login to vote
Frank_RE's picture

I do not Think that the workaround is usefull. This only fixes one Job and set the Time to an higher value.

We have more then 1000 Jobs !

Ist there no Switch (reg?) to set the Default Timeout (if no Check Box “End Task After” is set).

By the Way we can set the Timeout for one Job to max 18 Day`s.

0
Login to vote
Alex Bizjajev's picture

Hi Frank,

In 7.5 it should be possible to set maximum time-out for the client job to 2628000 minutes, i.e. 1825 days.

job-time-out.png

Time-out has been increased per 7.1SP2 customer's escalation and the same fix should exist in 7.1.SP2 PF2.

If you have problem with setting such time-out to the gratest value than 18 days then this is a bug - please escalate the issue to the support.

Unfortunatelly, I'm not aware about the possibility to change global time-out value using some registry key.

Thank you,

Alex.

0
Login to vote
Frank_RE's picture

Hi Alex,

I have changed in version 7.1 the timeout and got an error message with the maximum value 2160th When I veringerte the value to "2628000", he wurder accepted. Thus we have a solution. In version 7.5 comes with the same approach, the message with the Error value "2.628 million". So at least the ad was angepsst in 7.5.

It is a pity that there is no fix for the actual error. Hook out would have been better and more logical. OK, we wait for a fix in the next version.

I hope the Symantec Support get such errors with and passes them on to the developers.

Regards, Frank

PS. Finally, sorry for my bad school English.

0
Login to vote
Alex Bizjajev's picture

Hi Frank,

No problem at all and I'm sorry for the issues with our soft.

I have logged usability defect for the appropriate team to make the jobs and tasks time-out controllable in one single location.

Thank you,

Alex.

+1
Login to vote