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.

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.

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.

User State Migration: Please add an option to choose that a OS deployment on the target Computer will be only enabled when a capture on the source Computer was already done and the Migrated Data is on the Migration Point. Or add a possibility to query for the state Status in a dynamic Collection Membership rule. At the moment the target Computer can start there OS Deployment task sequence, even the migration data is not at the State Migration Point.

Following on from the excellent view only option added to task sequences - https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/20361052-task-sequence-view-only-option - can we have the ability to copy a task sequence step from this view? We can already copy text from e.g. Run Command Line but we can't copy task sequence steps themselves or view conditions on steps in a way that allows copying text from them so we still need to open the task sequence in Edit mode to do this.

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

We have had situations where the PXE Reponder service errors and stops listening to PXE requests WITHOUT the service stopping.
For example, if the service starts and the machine doesnt yet have an ip address.

Errors reported:
PXE: No valid IP addresses.
PXE::StartPXEServer failed; 0x80070490

BUT the service keeps running!

Suggest that the service should stop in this case so that other monitoring tools can detect and remediate the service failing.

The MDAC component of WinPE currently contains the deprecated SQLOLEDB provider. This will not allow a connection to a SQL server from WinPE during OSD using a script or existing MDT automation if the SQL server has TLS 1.0 disabled.

Please update the WinPE MDAC component to include the updated MSOLEDBSQL driver, which supports connections using newer versions of TLS.

We would like the following capabilities added to the task sequence copy/paste conditions feature: (1) If pasting into a step that has no conditions, the right-click content menu should simply say Paste. Paste Under, Paste Before, and Paste After only make sense if the step has other conditions. (2) Add ability to copy/paste more than one condition at a time. (3) Add ability to copy-paste conditions between different task sequences.

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.

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.