Deployment Solution

 View Only

Task jobs restarting after they seem to have finished

  • 1.  Task jobs restarting after they seem to have finished

    Posted Jan 06, 2012 10:33 AM

    Hallo everyone

    I have a bit of a strange problem.
    I would like to start out by saying how it's setup, and then explain the problem.

    We are using DS 7.1 (latest release, can't remember the exact version, but the NS is fully updated as of last friday, which is 30-12-2011).
    We have off site PXE servers (which also are task and package servers), and we are going to have a distribution center which are going to be handling the installation of 10.000 clients.
    As of today we have 2 kinds of machines, one is a domain pc and one is a non-domain machine, those 2 machines have their seperate images for the installation, and seperate installation jobs.

    As of today, the way we control what job we initiate we do it by 1 job which handles the name giving of the computer, and if it has name 1, this vbscript exits with error code 1, and if it has name 2, it exits with error code 2.

    If we start lets say 45 machines we have problems with about 11% of them (which is about 5 computers) and how we see the problem, is the jobs on the 5 machines runs to end, and the job decides, oh wait, we haven't run this job and starts the deployment job all over (which is not acceptable).

    Has anyone seen problems which kind of looks like this one?

    I would like to also say, the log files doesn't seem to be at much help here, because the solution just seem to think, i haven't startet the job and i need to do this, and then in the logfiles the only entry we can see is that it has startet the job.

    Kind Regards
    Morten Leth