Whether you reached the 32 action limit in your task X or simply want to organize some actions into different tasks, the secret to getting them to run one after the other is to have task X+1 set with an custom event trigger that scans specific event logs and looks for event 102 Task Completed from a specific task (the previous task in sequence, or task X in this case). Splitting up tasks and running them tasks sequentially split task X into multiple task, and set each subsequent task to run sequentially after the previous task completes.If your task X has 32 actions, then you must either. ![]() So I will copy it here, with updated steps that are easier to follow along. Or needs to figure out how to implement event-based triggering.Īfter searching exhaustively, I found a blog post that figured this out quite some time ago. I still left the original answer below as it might help someone who wants to work exclusively with Task Scheduler. To run silently (without CMD console window), you can use nircmd or silentCMD script. In addition to having unlimited actions, I can add comments for each action which I couldn't do with task scheduler actions. I still don't know how to print the ERRORLEVEL codes. I just echo my own custom logs after each command along with timestamp so that I can follow the progress. Then just run that CMD file in Task Scheduler as a single action. I decided to create CMD script and just stick all my sequential commands there.
0 Comments
Leave a Reply. |