I'm having an issue on a number of computers running a task sequence. Many of them are failing with exit code 1152. I've got the task sequence set to run every 4 hours until the computer is removed from the collection. I'm in the process of sifting through SMSTS.log files to see what went wrong. One my first system, something happened that I didn't think was possible.
My task sequence performs 4 steps. The first two run correctly. On this particular system (and it may be more or all of them), the third step started at 12:03:34 AM 06-04-2013 and then the log is nothing but "Waiting for job status notification..." until 10:58:05 AM 06-06-2013. It looks like the only reason it stopped then was that the system was shutdown.
How is this possible? The step in question has a maximum allowed runtime of 30 minutes. Why is my TS waiting so long?
I'm assuming that my 1152 exit codes are the result of trying to re-launch a task sequence after 4 hours when the previous attempt is hunt?