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.

A lot of folks are building WPF apps and frontends that are used at the start of OSD. The most recent PE has stopped supporting this all together. I'm not sure if this is the correct user voice, but the ability to whip up an app to run in PE makes OSD a lot more flexible. It'd be excellent to have it back and to have it be a bit more robust.

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.

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.

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)

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...

For task sequence step conditions (in the options tab), it would be SO GREAT if we could move the conditions around just like we can with the actual task sequence steps (drag and drop, move up or down, cut/paste, etc.). It can be a pain to remove a bunch of conditions and add them back when they are not in the right order.

Modify the Download Package Content step to include a dynamic option similar to the Install Package step (see attached mock up). This will allow the ability to selectively download content that is not a direct task sequence reference. When deploying the task sequence, the direct references (common to every system) can be downloaded ahead of time and then the system specific items can be downloaded selectively at TS run time. OSDDownloadContent.exe already performs a dynamic content location request, which is super useful when needing to pre-cache or download driver packages, BIOS packages and other items that are machine specific.

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).

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.

Add Battery, Power state check to Task Sequence "Check Readiness"

Would be nice to add an extra option there to check the power state, this is very important for when making a task sequence available to the user.

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.

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.

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.