AdamGrossTX / asquaredozen

0 stars 0 forks source link

Building a Better Task Sequence-A Square Dozen | A. Gross Blog #14

Open utterances-bot opened 2 years ago

utterances-bot commented 2 years ago

Building a Better Task Sequence-A Square Dozen | A. Gross Blog

A.Gross Blog | Adam Gross Enterprise Mobility MVP

https://www.asquaredozen.com/2018/11/29/building-a-better-task-sequence/

gr8greet commented 2 years ago

Hello Adam, Thanks for the quick and super useful TS as always!. But one weird issue found out at my workplace and in my test LAB while testing this TS. Issue is that in the Task Sequence Error prompt the variable %FailedStepName% doesn't get replaced by the failed step name but it does in the Installation Progress prompt. I can't see the option to paste the screenshot here.

MrZepto commented 2 years ago

Same issue here...

AdamGrossTX commented 1 year ago

Try checking the variable names on the failed step vs the script for output. I think I made a typo in there somewhere but haven’t touched this in a long while.

Also, I have a better version of this plus a few other posts that may be cleaner.

https://www.asquaredozen.com/2018/12/14/building-an-even-better-task-sequence/

https://www.asquaredozen.com/2019/04/30/building-a-smarter-task-sequence/

With the newer Powershell steps available now I no longer use the run commandline steps but moved to a variablized Powershell step to make this all cleaner.

yafp commented 8 months ago

@MrZepto @gr8greet have you been able to find the issue here? I am stuck with the same problem as you mentioned.

MrZepto commented 8 months ago

Nope

MiketheWils commented 7 months ago

It appears that MS introduced single quotes into the error messages since 2018. In PS this writes the exact text. I'm assuming Endpoint mgr is using something related. I've been able to duplicate, however, the information in the step is correct. Just not the step name in the message pop-up. I don't think there is a way around this behavior. MS needs to remove the single quotes.