Task Sequence Error Dialog Box Needs to Show Step Name
The error dialog box for the task sequence shows the error code, but does not show you what step threw the error.
- Show the step name on the default error dialog box.
- The modal dialog box for errors goes directly over the progress dialog box, so you can’t see the step from there without using the mouse.
- You may not have mouse support, especially when you are RDPing into a box with a VMware or Hyper-V console… which means this is REALLY frustrating
Nash Pherson (MVP)
shared this idea
AdminBob Mac Neill
(Software Engineer, Microsoft Endpoint Configuration Manager)
responded
Thanks for all your suggestions and feedback, updating status to completed.
SCCM 1902 fast Ring released today
Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Update-1902-for-Configuration-Manager-current-branch-is-now/ba-p/376516
Docs: https://docs.microsoft.com/sccm/core/plan-design/changes/whats-new-in-version-1902
9 comments
-
Someone
commented
We implemented a script to return the error code by e-mail, they've since added the SMSTSLastActionName variable, so we can now send the step and return code by e-mail.
https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/20037565-smstslastactionname -
Michael
commented
The same as 'Gibson99'. Every time the techs call me to say "it's not working, I have error 4005". I prefer they just shut u*, always the same story
-
AdamGrossTX
commented
This as well as adding a TS variable to capture the Name of the last step that failed. Most people trap the error then do post-error cleanup steps. This makes it necessary to dig through the logs or reports to find what step actually failed. Making it easier to handle errors in general would be fantastic.
-
Levi Stevens
commented
We basically had to write a PowerShell script to parse the SMSTS.LOG and display a meaningful messages.
-
Levi Stevens
commented
It should also show any messages with LOG TYPE OF 3 for that step.
-
Nash Pherson (MVP)
commented
You have my permission to use any and all extraordinary measures needed to get an intern to ensure this change is ready before the next release. Kidnap interns from other teams. Lock interns in their cubes over night. Force feed interns energy drinks. Feel free to tell security that "Nash said it was ok!".
-
Gibson99
commented
THIS!!! A THOUSAND TIMES THIS!!! 3 votes is not enough for this. I can't tell you how many times my techs email/call me and say "it failed" and if they actually give me an error code, it's usually 80004005 which is about as useful as ye olde 1603 from msiexec - completely worthless. it doesn't matter how many times i tell the techs to move the error message or hit alt-tab and tell me WHICH step it failed on, and extending the auto-reboot time didn't help either (except for my own testing). having the error message NOT be system modal or having it moved up/down so that it doesn't cover up the progressUI window would be ideal if you can't just include the actual task sequence step name in the error dialog box itself.
-
Nash Pherson (MVP)
commented
Additionally, you could just make it so the error dialog box isn't modal which would mean we could ALT+tab to the step name.
-
Nash Pherson (MVP)
commented
The other two from the #MMSMOA #HackAThon discussion are: