For task sequences that allow code input (command line, PowerShell), apply syntax highlighting to the code

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.

We are much more using efford to .wim file download from wide area, need to change this. Maybe 1 server can lead packets and protocol. So please rescue our from TFTP for wide areas. Also is not secure because its using UDP protocol.

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.

Add the option in Apply Operating System to add a script that can modify the WIM file once it is downloaded (i.e. changes would be local only to the current OS installation).

This would allow you to keep the WIM file as generic as possible while still allowing it to be modified, reducing the number of WIM files required in an environment that may require multiple WIMs per OS.

The Spring 2020 version (20H1) of Windows 10 will supposedly have a "cloud recovery" feature that can download an image from Microsoft to repair a Windows 10 installation. It would be great if we could customize this with ConfigMgr so a repair will grab an image of our choosing from CM without going out to Microsoft.

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.

This would be a great consistency improvement, and would look slick! See attachments for (terrible) example mock up.

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.

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 are seeing a number of unexpected restarts during the "Upgrade Operating System" Windows 10 feature update that causes the task sequence to fail. These restarts are happening during the "setup.exe" phase of the process. Allowing the task sequence to continue would resolve this issue.

The 'Pre-provision BitLocker' step has an option to skip the step when the devices does not have a TPM or when the TPM is not enabled.

I'd like to see that option added to the 'Enable Bitlocker' step. Whether it's enabled by default is another question I guess. However, this is one of the many things that hang up new admins trying to get their first Task Sequence off the ground. Just spent an hour or so trying to get past this step.

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

This would help with troubleshooting TS, if in the actual TS, to the left, it lists by number each step.

When using the Run PowerShell Script task sequence, it would be beneficial to be able to pass task sequence variables in the parameters field, especially when using different credentials where PowerShell no longer has access to Microsoft.SMS.TSEnvironment.

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

Adding compatibility check task/tasks to "Upgrade an operating system from an upgrade package" task sequence with custom error message descripting the compatibility error.

Example: check the attachment file