Display the Step No. in the Task Sequence Editor so it can be easier to find where in the TS an issue is occurring. This could be handy because you could have multiple steps of the same name (especially gather & User Toolkit)

After creating stand alone media from a task sequence, all packages in the task sequence are not encrypted. All files in applications, packages and also os image can be exported easily. The all media in the stand-alone media should be encrypted with pre-given password (determined when standalone media created) . So, the all files will be protected.

If you are doing BIOS updates as part of a Task Sequence you are sometimes faced with "unexpected reboots" because the BIOS update program restarts the computer if you want or not (e.g. Lenovo ThinkStation BIOS updates).
Those reboots will cause the Task Sequence to fail.
It would be very helpful for those scenarios to be able to prepare a task for such reboot events and to ignore the errors in order to continue the Task Sequence after the reboot.
Maybe a modified "Restart Computer" task which prepares a Task Sequence reboot but doesn't execute it could be an approach.

Make it possible to password protect the F8 command prompt during OSD.

the F8 support is very usefull for troubleshhoting but it is alos a security issue. Having two bootmedias (one with and one without) isn't a workaround since you will have to reboot to get the F8 support and the problem may not occur during the second atempt.

Allowing us to password protect the prompt gives a secure function that doesn't require a reboot when you have to troubleshoot.

During an OSD deployment we install several applications that return a reboot exit code.

Each time they install they reboot, rebooting takes a minutes or two to restart the task sequence engine so each application is adding 2-3 minutes to the build time.

I would like to ignore these reboot exit codes because I know I will be rebooting at the end. We would prefer to not have a separate application for OSD and for Software Center.

Having version control for Task Sequences would be invaluable.

If we could link a GitHub account we could easily monitor Task Sequence changes either in Github or SCCM. The ability to roll versions with Administrator approval (similar to publishing scripts) would be ideal.

Expanding on this idea more, highlighting additions/edits/deletes within the Task Sequence dialog would be the icing on the cake.

Provide an option to RESUME an already running OSD task sequence deployment that failed in a specific area versus having to start the deployment all over again. In the event of a failure, this would allow for us to resolve the issue right away and then allow the admin to RESUME the OSD task sequence deployment from the exact point of where it failed (not have to start everything over again).

When auto-launching a PowerShell script inside of a customized version of WinPE, the script will fail if an Import-module function is required in the script. a workaround is to open PowerShell, manually import the module before running the script and it will work. It appears that PowerShell is not fully initializing if you call a script as a command line parameter of Powershell.exe...

Compare the contents of two task sequences and report on the differences. Ignore minor items unique to each Task Sequence like dates and ID codes .

For MBAM clients I want to use preprovisioned bitlocker volumes.
A requirement is to use the AES256 encryption mode.The pre provision bitlocker step defaults to aes128, and cannot be changed in the step itself.
I now have a extra step before the preprovision bitlocker step with this command:
cmd /c reg.exe add HKLM\SOFTWARE\Policies\Microsoft\FVE /v EncryptionMethod /t REG_DWORD /d 4 /f

Thanks to this website:
https://blog.alschneiter.com/2017/05/03/change-bitlocker-drive-encryption-to-xts-aes-256-during-osd-with-configmgr/

Not only applications or packages/programs run in a TS would be nice to select a special deploymenttype to run. In packages with programs is it possible why not with applications and his deploymenttype.

I would like the ability to load up a couple of Task Sequences, and have the ability to merge any changes between the two TS's.

This would assist when importing TS over from a TEST or DEV env or working on test TS in the same environment. Ideally have the option to approve /deny each of the merges before submitting.

Once merged, version the change to a later increment so neither of the two TS's are saved over?

There is a buisiness need to be able to select a different bootimage as the one linked to a task sequence. This can be used for administrative tasks of a client such as booting MDOP DaRT over the network. Implement the ability to define which bootimages can be selected at a TFTP boot. (Of cause, OSD is only possible with the image linked to the task sequence)

I know we can use the DISM command to set the input locale but from my point of view it should exist a field in the Boot Image properties where you could specify the layout you want.

Please allow Task Sequence specific passwords. Currently the only built in option to password protect a task sequence is to password protect a PXE point.

I'd love an option to run a Task Sequence in simulation mode (potentially on a Virtual Machine) that can check for any "logic" issues in the Task Sequence. As an example, I just made a change to an MDT Integrated Build & Capture TS to just be a WORKGROUP machine, rather than domain joined. I made the necessary SMSMP= change to the ConfigMgr client install for application installs to work, but I forgot to change the capture path to a FQDN - therefore it got the whole way through and failed. A quick simulation would have saved me 45 minutes.