When deploying a device using Autopilot, the Enrollment Status Page (ESP) is used to prevent access to the desktop until the device provisioning tasks are complete. But ConfigMgr doesn't integrate with the ESP, so there's no way to wait for packages, apps, or task sequences - the user doesn't know when the process is done. Add that integration.

Split this item from a bigger umbrella item.
This is to specify an icon per App Task Sequence in the Software Center.

We have many task sequences, sorted into folders for multiple users, when it comes to archiving them, it's tedious, we'd like to archive multiple task sequences by user (or by folder), this would be great, right now you have to export one task sequence at a time which is tedious.

Currently (v1806 or later) Third Party Software Updates are not being installed during the Install Software Updates step in a Task Sequence.

Ideally third party software updates should be installed just like regular updates during the Task Sequence. A machine should be fully patched (secure and end-user ready) when it leaves the deployment bench.

I would like you to add the keyboard layout setting in the Apply Windows Settings step.
Please add it as shown in the screenshot below.
Currently, keyboard layout settings are manually added to the registry within the Task Sequence.

Command line:
cmd.exe /c reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "LayerDriver JPN" /t REG_SZ /d kbd106.dll & reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "OverrideKeyboardIdentifier" /t REG_SZ /d PCAT_106KEY & reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "OverrideKeyboardSubtype" /t REG_DWORD /d 2 & reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "OverrideKeyboardType" /t REG_DWORD /d 7

I'd like the option to set Variables on the Run Task Sequence Step itself. Often times I need to pass variables into the Task Sequence, which will be different based on which Parent TS is calling the Task Sequence "Module".

Currently I have to have a Set TS Variable Step right before I call the Sub Task Sequence so the Sub TS knows which steps to run, or how to run them.

Add the complete progression status in the progress bar in order to see the current step and remaining steps.

Like in this post http://www.systanddeploy.com/2018/02/add-complete-progression-sta

Please allow additional customization in the Task Sequence High Impact Dialog Box. Enable or Disable the Individual Comment Boxes completely, and allow Hyper Links to launch a web page with more information.

When OS Upgrade and Custom task sequences are running offline (such as following a reboot while on VPN) all task sequence manager status messages are discarded. While this is expected in WindowsPE, it would be beneficial for troubleshooting/reporting if OS Upgrade and Custom task sequences would queue status messages locally just like Executive Manager does with software installation status.

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.

This Cmdlet does not support using a cloud distribution point as the distribution point source (and neither does the GUI).

This means that in order to use this feature we have to have an on-premise DP purely for this purpose.

Regards
Wayne

While Running Task Sequence to deploye custom image for Windows 10 version 1903, task Sequence doesn't show any progress bar in Full OS Mode.

Task Sequence progress bar works fine until WinPE Phase which includes image applying and download of "Setup Windows and configmgr". Right after the reboot when we are expecting to start Full OS phase starting with SCCM Client installation, there is blue screen shown with message "Just a moment..." till the time all the all the steps of task sequence completes successfully.

This doesn't bring a good customer experience.

The new step which lets you run powershell scripts in a task sequence have an open and a browse button. It would be awsome if a button was added which lets us select a configuration items remediation item (script or registry or w/e).

This way we can set up the machine the same say we do after it has its client configured but we dont need to add startup scripts or services to fix this before first logon.

Allow language localization on task sequence User Notifications like we have for applications. currently if you change the default task sequence user notifications, they only show in the language they were entered in, not the users localized language. Same for making the task sequence name, in localized language