ConfigMgr TP 1901 was released yesterday, and among the many new features, there was an improved task sequence error dialog box. Had to be tested. 🙂
First, I added an action to a Task Sequence that I knew would break it – Running the non-existing foo.vbs script.
Then I deployed it to an "old" ConfigMgr 1810 client, and it looked like this:
Next test was to deploy the same sequence to a client in my ConfigMgr TP 1901 environment. Then it looks like this.
YAY! The Error dialog tells me on what step it failed.
/ Johan Arwidmark