The essential need to run executable content from package before drive partitioning step (or any other case of unavailability of writable partiotion). "Data Access" package feature seems not working in OSD TS.

Currently you can't create offline media for OS upgrades. I'd like to see an option added where you can create offline media (that you don't need to boot from) that can upgrade an OS. At the moment, you can create standalone bootable media, copy the TS and change every source location/install to a run command.

Kind of hybrid between prestage and standalone. Not everyone connects to 'work' via fast always active links. VPN users over slow links are not currently catered for.

I would like to add setting of LayeredDriver (106/109 key, etc.) during OSD (OS deployment).
These settings are "very important topics" for OSD guys in Japan and Korea.
Without this setting, the keyboard will become an English keyboard.

LayeredDriver [Microsoft Docs]
https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-international-core-winpe-layereddriver

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.

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.

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,

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.

By default you can pause a Task Sequence by adding a step in the TS that will display a msgbox.

It would be cool to be able to pause a TS when you want and as many times you want.

It is possible by changing the ztiutility.vbs file and add the below process:
- Create a new TS variable TSPause
- If this variable is configured to True a msgbox is diplayed

See a post I did about this:
http://www.systanddeploy.com/2020/02/pause-task-sequence-when-you-want-with.html

Display the DP the content is coming from in the Progress UI after the % Complete.

"Downloading install.wim (64% complete) from DP: DPOINT01"

It will be more productive if we have a build in task to add to task sequence to perform the following:
1- Windows 10 Background Settings.
2- Windows 10 Lock-screen.
3- Add custom fonts
4- Pin to Taskbar.

As of now we can achieve the above using script, but it will be grateful to achieve it by task sequence.

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.

Currently 1E PXE lite client agent is used to manage the PXE Boot image for remote locations instead of downloading Boot Image from SCCM DP.
Can you bring this feature in Endpoint Configuration Manager which saves huge cost for the company.

there should be an option for disable/enable all conditions. For testing or debug, without deleting conditions, we can disable them and then re-enable.

When building unknown devices, the RDR and UDR do not merge, leaving an Unknown device record and a 'stale' correctly named record that is not managed by ConfigMgr. MS have confirmed that this is a well documented known issue and advised me to post here, so it can get some attention from the product team. Please advise

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.

The new Model field on drivers is useful, but needs to be extended to other content types, like Packages & Applications, where Model specific items need to be installed (e.g. specific HP SoftPaqs, or video drivers that need to run from .EXE etc).

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.

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,

SMSTSDisableStatusRetry is great but in my testing there still seems to be times in which status messages are retried multiple times. The big one is whenever you run a "run powershell script" step in bypass mode. Please make this variable supress all status message retries and speed up our disconnected task sequences!

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.