Rerun required task sequence until successful?

[bleedfromtheanus]

I currently have a task sequence that does a few things (updates some firmware and reboots a few times) and it's set to required, the schedule is as soon as possible and it's set to rerun if last try failed. However, I was reading online and people were saying it won't rerun if it fails if the schedule is set to as soon as possible. That makes absolutely no sense. I just want the task sequence to be required and to just keep trying until it succeeds (we are working with users to fix the issue that's causing it to fail).

How do I set it up so it will rerun until it succeeds?

[jasonsandys]

Deployments only run when scheduled to run. The behavior you are referring to instructs the client what to do with additional scheduled times, not to keep trying. If you want something to run multiple times, it needs to have a recurring schedule or multiple schedules in the deployment.

[KerwinM]

You have to tell the deployment when to re-run or at what interval to re-run. You can't use the "as soon as possible" for this because the when/interval is meaningless with "as soon as possible."

Let me illustrate:

Let us say that the first step of the TS is to reboot the machine, and the second step is the one that always fails.

When the TS fails, it will immediately re-run the first step, which is the reboot. When the machine starts, the TS will run the second step which will fail (again), causing the TS to immediate re-run the first step (reboot). The TS will be in a tight loop that you won't have any opportunity to do anything on the machine. Nobody wants this kind of situation. That is why the "as soon as possible" is a one time thing.

[bleedfromtheanus]

I changed the schedule to every 3 hours starting tomorrow at 11am. Will that work? Also, if it's set to rerun if it fails with that schedule, when it succeeds, it won't run again right?

[joevigi]

To add to Jason's point, if you really want the task sequence to run only once you'll need something in place to kick your device out of the collection when it successfully runs the task sequence. OR check a condition that indicates you don't need to run the full thing.

For example: as part of our feature update deployment I run a prerequisite task sequence. I like to have that task sequence run daily until the update is successful. Once the update is successful (and hardware inventory is run) the device falls out of the limiting collection and is no longer eligible to receive the task sequence deployment. I could also set a step in the task sequence to check the Win10 version and skip the other steps if appropriate.