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.

When trying to move away from Group Policies to Configuration times/baselines and in every other scenario as well, add a step in Task Sequence to evaluate and remediate select Configuration items/baselines. Then we can select which one of the Configuration Items/baselines should be applied during OSD so the settings are present when the user logs on for the first time

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 REGSZ /d kbd106.dll & reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "OverrideKeyboardIdentifier" /t REGSZ /d PCAT106KEY & reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "OverrideKeyboardSubtype" /t REGDWORD /d 2 & reg add HKLM\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters /f /v "OverrideKeyboardType" /t REG_DWORD /d 7

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.

When Importing a Task Sequence, I'd like the ability added to Import a Duplicate, but it would NOT overwrite the original, it would create a duplicate with modified name and new package ID.

Situation, I've created v1 of the TS and exported for sharing. Others have taken v1 and modified and started to use.
I then export v2 of same TS and made available, others want to import but it will overwrite. Would like the ability to allow others to import v2 without impacting v1.

It would be great if the created application groups can be added in a task sequence.

Instead of having long lists in a task sequense you could manage default apps in the application groups

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.

Take the OU path from 'Network Settings" and turn it into a variable e.g. _SMSMachineOUpath
I use dynamic variables to determine the OU based on location and device so my Domain OU path has OU=%devicetype%,OU=Location,OU=workstations,DC=Contoso,DC.com
so it would be nice to have the actual value in a variable that I can reference later say in a script to move existing object to the above created OU. I can see the full path in the SMSTS.log, but not in a variable. Also removing the LDAP:\ from the start could be handy in some situations I guess.

Team,

Currently when the non-WDS PXE responder is enabled, all DHCPINFORM messages are logged in the SMSPXE.log. This floods the log with unnecessary information and makes the troubleshoting more difficult as the log gets overwritten very often.

Please perform the change to at least not log these DHCPINFORM messages.

With the new great possibilites using the Administration Service it would be great to have a Built In task sequence variable with the URL to the SMS Provider(s) so we can easily call that in our OSD Powershell scripts during OSD

Sometimes the users just don't know their computer is actually connected LAN at 100 Mbps instead of 1Gbps due to network port issue or network cable issue. It will take almost 5 times longer time to complete the OSD task sequence. It just messes up the things. I hope the network connection speed info is visible in WinPE or give user a warning before kicking off the OSD task sequence.

Pre-caching content for a task sequence is great, but we do not use driver packages for installing drivers in a task sequence. We use normal packages and the download package content step. This is true for in-place upgrades as well. As it works right now, when running an upgrade task sequence, the client downloads all of the packages for drivers, regardless of whether they are needed for that particular model. It would be nice to have a way to specify which package containing drivers gets cached for a particular model.

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.

We often find ourselves duplicating conditions in Task Sequences. The ability to copy/paste/move conditions in TP 1908 is excellent but I would suggest we could go one step further.

To have a conditions library where we could select custom - predefined conditions would be excellent. We should be able to add/edit/delete our own predefined conditions.

I would like a way to monitor the ConfigMgr PXE Responder Service when an error occurs. For instance, when starting an osdeploy and the bootimage fail to load with error 0xC0000001, the smspxe.log simply stops its output, not generating any error. With the WDS-service, this error was easily detected in the eventlog.

The task sequence has a 32MB size limit for all policy. But for some reason they are actually limited to 16MB. But the Product Group is aware of the problem. I know they are working on fixing the 16MB limit.

This will help us troubleshoot and determine when the task sequence has reached this size.

With Bitlocker Network Unlock, a WDS server can automatically unlock your bitlockered device without requiring the user typing the PIN at boot. (https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-how-to-enable-network-unlock).
As we all go forward using the SCCM WDS-less PXE-provider instead of WDS, it would be a good idea, if it supported Bitlocker Network Unlock, too.