Add a column with the file size next to store path, so admins easily can monitor the amount of space being used during USMT

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

WHY, WHY WHY are there two separate folders for driver creation? Why break out drivers into 2 different parts. Drivers and driver PACKAGES? WHY? WHY WHY WHY? Obtuse. Stupid. Incredibly useless. Adds a layer of unnecessary complexity. Please stop making such inane decisions.

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.

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.

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.

It would be nice to have a button for extra information which shows a list of all the steps in a T.S with a Green tick for success, yellow for skipped, Orange for failed but continued, and Red for failed and ended the TS, along with exit codes.
Having the option to export logs automatically to either a network drive or USB key would make troubleshooting remote deployments so much easier.

Similar to https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/13880781-task-sequence-error-dialog-box-needs-to-show-step,

On SCCM/MDT integration OSD deployment the MDT Deployment Toolkit its downloaded for gathering information among other tasks, but because of multiple reboots during OSD the deployment toolkit is downloaded multiple times which causes delays during OSD, it will be great if we could download and cache the Deployment Toolkit during the OSD build to be re-use to improve deployment overall time. This way the Task Sequence knows the package is local and there is no need to re-download the files.

Add an option to place DPs into maintenance mode while running an OS upgrade task sequence on the upgrade operating system step. Currently we run a powershell script every half hour to place non-responsive DPs into maintenance mode and bring any currently in maintenance mode that come back online out of maintenance mode, but it would be nice to allow the task sequence to do this to clear up the distribution queue.

Add the option to the GUI to enable or disable windows features within an OS install WIM in SCCM rather than relying on DISM. This would allow for significantly easier OS deployment and provide and easy method of verifying the features enabled in a WIM.

I would love to have the option to allow our users to have access to some Task Sequence folders but, not other folders.

I get the option to limit the folders but this prevents them from either being viewed or being copied/modified.

I would like my Task Sequences viewable but not editable. It would be great if users could copy from 'read only' area into their 'test' area and can the create/modify without any risk.

When reimaging a machine it would be most helpful if the machine would retain the name it already has. It greatly annoying that it gets renamed to "Desktop- something or another". Other imaging solutions have this ability (Acronis) without having to do it in some convoluted way; why can't SCCM? Thanks,

Stop resolving environmental variables in Unattend.xml; for example, %SystemDrive% is resolved to “X:” which is of no usage in a RunSynchronousCommand. To clarify, TS Variables are fine as they are.

Add an option to only allow a Task Sequence to be run by a user with local administrative rights.

This will allow a Task Sequence to be advertised to systems but ensure that only support staff who have local admin rights can initiate the Task Sequence, preventing standard users from accidentally re-imaging their computer.

In the past we have used the option to 'run another program first' on a Task Sequence and call a script to evaluate the current users groups/permissions, but it would be really useful if this was a native feature.

Disable “Allow clients to download delta content when available” during the OSD, this is not working and breaks software updates.

If activated Software updates stuck on 0%.

Maybe is anyway a good idea to turn of all these caching options during OSD (P2P, DO, BranchCache).

_See closed Premier Case: #:19378176

Hello

I'm trying to create a 'big' stand alone media..and timeout is not enough.. actually, if i select everything, timeout generate an error ..

could you think a possibilities to extend the timeout for big infrastructure and task like me ?

When viewing computer associations show the devices as online similar to viewing in Devices.

If possible give some more right-click options even if it was just the option to right-click and it ports you to the source and/or destination system in Devices.

Create a TS step to enumerate Appx packages and provisioned packages from the install image and be able to toggle on/off for enterprise deployments. Or provide a list to enable/disable approved that are removed from image during deployment. Annoying to have to use a custom PowerShell script to have to set a list of white-listed/approved apps/features and then uninstall during OSD.

After creating new deploymentshares, and then building a new 2019 deployment server. MDT can't deploy Windows 10 20.04. 6 days spent reading forums, docs and so much more. I have applied the bdd patche as requested but I still get a total failure.
Sysprep simply does not open or run. The system restarts with out running sysprep. There is nothing on the subject to help me.